I have been voluntarily maintaining a Chocolatey package for ActivePerl for some time now (Chocolatey is a community based software manager for Windows, to some extend comparable to Homebrew for MacOS). The ActivePerl Chocolatey package is quite popular e.g. the v5.28 has been installed over 40k times.
A Chocolatey package is not a real package in the classical way. In practice a “package” is just a PowerShell script that downloads the actual software package from the software vendors site and then installs it. The package maintainer (that is: me) provides the required metadata such as installer download url, installer checksum, installer arguments etc.
Previously creating a Chocolatey recipe for the ActivePerl was a breeze. However, starting from v5.28, the download content for the community edition is not permanent anymore. That is, the community edition seems to be a weekly-build and the content checksum changes weekly. The Chocolatey packaging rules expect a hard-coded checksum for each version in the recipe. This makes it very problematic to maintain the Chocolatey install script.
Theoretically, I could release a new Chocolatey version on weekly basis. However, because there would always be a delay between the actual weekly release and the Chocolatey package update (including the moderation delay), the installer would break time to time (i.e. when the last weeks build is not available anymore but the Chocolatey package has not been updated yet). Another option would be to mirror the weekly releases but this is in my understanding not permitted by the license.
Now, I wonder if it would be possible for ActiveState to have a some semi-permanent download url for the weekly releases? E.g. so that the weekly builds would have distinguishable file-name and the old weekly release would be available for download for some time. Or maybe you have some other ideas, how to make this work?