Hi, Yesterday I tried to clone the macports-ports repo and played around with the LilyPond Portfile. Howerver, I haven't really got how to work with the repo, particularly every port command I ran seemed to be using another macports location, not my local repository.
I will try again tomorrow or sometime this week. Would also be interested in learning if someone has managed to work with the repo. Best On Mon, Feb 9, 2026, 10:27 PM Werner LEMBERG <[email protected]> wrote: > > Thanks to all who responded to my request. I've asked first for help > on the LilyPond mailing lists, hoping that there are some people who > have both experience with LilyPond and programming... > > >> However, I currently don't have access to that Mac, and due to the > >> age of this computer the development cycles are glacially slow. > >> > >> Is there anyone using MacPorts who could work on this file and > >> submit updates? > > > > I have zero experience with MacPorts maintenance/development, but I > > do own a Mac Studio M4 that should be able to run at a non-glacial > > speed > > Nice! > > > Generic IT/development skills are present, but on the dev side > > mostly limited to Java development > > > > Would that work? Or would I need deeper Guile/C skills to work on > > this? > > Thanks for your offer! In general, no need for Guile/C skills, I > think. It's rather to fumble around with a Macports Portfile, which > is written in (easy) Tcl, and which has to be updated to replace the > 'guile-2.2' package with 'guile-3.0'. Both LilyPond and guile 3.0 > themselves build cleanly on the macOS, AFAIK. > > The documentation at > > https://guide.macports.org/#development > > is quite good IMHO, and there are zillions of other Portfiles to look > at in the 'macports-ports' git repository. > > > The efforts up to now for keeping the stable version available and > > up-to-date (as well as occasionally the -devel variant if there > > happened to be something interesting for me to try out in the > > unstable releases) have been higly appreciated as I do use MacPorts > > as an end-user to get several tools among which lilypond provisioned > > and updated on my system. > > Well, if you currently use 'lilypond-devel' via MacPorts, you get a > two-years-old version... > > > Werner > >
