On Fri, 2023-09-01 at 14:31 +0200, Jean Abou Samra wrote: > Hi, > > Per the release procedure > https://lilypond.org/doc/v2.25/Documentation/contributor/release-checklist , > GitLab releases for LilyPond contain both binaries + doc tarballs and source > tarballs generate by "make dist", while the old download site > lilypond.org/download, which used to host all of these, now only has source > tarballs. > > https://gitlab.com/lilypond/lilypond/-/issues/6648 is the result of someone > being confused by not finding doc tarballs next to source tarballs on > lilypond.org/download, as it was in the past. > > I couldn't find the reason for this in the archives. What's the purpose of > serving the source tarballs from two different places?
IIRC it was alluded to when I proposed uploading only the binaries (and the documentation) to GitLab: the source archive is used to build for various distributions (Linux, Homebrew, MacPorts). They all had (and still have) the "old" link in their setups, so it was (and still is) easier to keep uploading them there. Plus they are relatively small and don't require that much resources, so I think the benefit of providing the sources from the official website outweighs the extra step. As for the issue, I consider that somewhat of an outlier: Most users will follow the links on the website, and everything will work for them. A small fraction tries to find the binaries where they used to be (and I'm surprised there are still questions about the installer scripts...), but I find it highly unlikely that those people check the directory with the sources, so not uploading them doesn't really change anything for those users, does it? Jonas
signature.asc
Description: This is a digitally signed message part
