> On 17 Mar 2022, at 23:18, Hans Åberg <haber...@telia.com> wrote: > > >> On 17 Mar 2022, at 23:06, Hans Aikema <hans.aik...@aikebah.net> wrote: >> >> Hans Aikema, direct vanuit de iCloud >> >>>> Op 17 mrt. 2022 om 22:31 heeft Hans Åberg <haber...@telia.com> het >>>> volgende geschreven: >>> >>> >>>> On 17 Mar 2022, at 22:26, Jean Abou Samra <j...@abou-samra.fr> wrote: >>>> >>>>> The latest development version works, and I gather it does not differ >>>>> much from the "stable" version fairly recent updates (the old development >>>>> version become new stable). >>>> >>>> Not sure what you're referring to here? The latest stable release, which >>>> is quite recent, is 2.22.2, which is from the 2.22 series. It has only >>>> received bug fixes compared to the previously available stable release, >>>> 2.22.1. It does not receive the current development changes. If you want >>>> to help as a beta tester for the development release, 2.23.6, or just >>>> enjoy its new features, you are of course welcome to do so, but it is what >>>> it is: an unstable release. It does differ significantly from 2.22.2. >>> >>> The versions before did not change for a long time, and I always used the >>> development version as needing the features, and I have had not problems >>> with that. >> >> The observed (in)stability depends on the use-case. For lilypond-devel I >> currently run into https://gitlab.com/lilypond/lilypond/-/issues/6203 >> as I use Lilypond (among others) to create create images with transparent >> background for powerpoint slides. A use-case that works fine with the stable >> release, but is broken in the current development release (and expected to >> be working again once 2.23.7 is released according to the issue status) >> >> I also prefer to run development releases alongside stable, but any music I >> try to write for stable (unless there is something I neer for it that only >> works in the development version). Development I only run from time >> to time to see that nothing I use is breaking on it. > > In the past I used support for irregular meters and microtonality with > support slowly coming along in the development version, but that has now > moved to the stable version. Unfortunately, one cannot install both the > development version and the stable one side by side in the standard MacPorts, > I think, because they have the same name, unless one makes a separate > installation of MacPorts in a different location than /opt/local/, which is > also possible.
You cannot have both active indeed, but you can install them both (one active, one inactive). The recipe to end up with stable, but have current development version at hand for activation: sudo port install lilypond-devel sudo port deactivate lilypond-devel sudo port install lilypond then when you want to try develop: sudo port deactivate lilypond sudo port activate lilypond-devel and the other way around to switch back to stable: sudo port deactivate lilypond-devel sudo port activate lilypond only the active one will be upgraded with a sudo port upgrade outdated (over time you can even have multiple historical versions side by side at hand for activation by specifying the explicit version)
