On Thu, 2024-01-04 at 22:33 +0100, David Kastrup wrote: > CX <[email protected]> writes: > > > Is it possible to build a specific stable lillypond version with sources > > retrieved by git clone instead of a source tarball download? > > If it is possible how can you do this (because I can not find the > > documentation to do it)? > > The README in the repository references > <http://lilypond.org/doc/v2.25/Documentation/contributor/compiling> > > Have you checked it? > > In particular, setting it up from a clone appears to be described in > <http://lilypond.org/doc/v2.25/Documentation/contributor/configuring-make>
To add to this, the source tarballs each correspond to a specific commit in the repository. The exact hash is documented in the RELEASE- COMMIT file in the tarball, and also published as a git tag in the repository. Since around two years the tags follow the naming scheme v2.x.y, for example v2.24.3 for the latest stable release. Before that the format was release/2.x.y-1, ie release/2.22.2-1 for the last release of the 2.22 series. In addition to that, there are the stable/2.x *branches*, which at least at the time of writing correspond to the latest release from the respective series. But keep in mind they may be ahead with additional fixes while a release is prepared. Hope this helps, Jonas
signature.asc
Description: This is a digitally signed message part
