On Thu, Apr 22, 2021 at 2:24 PM Bart Kummel <[email protected]> wrote:
> Jean, > > The first thing I do is checking the website, in this case lilypond.org. > There is a section about reporting a bug. It says to check the bug list and > if your bug isn't there, report it. That's what I did. It didn't say > "search through years of mail archives". And, let's be honest, it is HARD > to come to conclusions from a mail archive, especially when you weren't > part of the discussion. > > That discussion aside, it seems the Homebrew formula found here > https://github.com/nwhetsell/homebrew-lilypond does work. It's fairly > simple, but takes a while to run. > > My suggestion would be to update the MacOS download page, and add Homebrew > and Macports as preferred installation methods. I'd be happy to help > updating that page, if someone can tell me where to start. > Macports should *not* be the preferred method of installing LilyPond on Mac OS; I believe most Mac users these days stay far away from it (I know I do). I like Homebrew for some things, but I've generally found it awkward for installing things like LilyPond, which is why I created the downloadable .app bundles. Is there a problem with the .app bundles? Why are we having this discussion right now? I think I'm missing some context. BTW, we'll need to change the Mac OS download page anyway; Bintray, where the current Mac downloads are hosted, is going away at the end of the month, and I need to figure out a good place to put them. Meanwhile, I've heard from someone who has some ideas about putting the Mac build pipeline on GitHub Actions, which apparently now has Mac build hardware available. I like the idea if we can make it work. > > Best regards, > Bart > Best, -- Marnen Laibow-Koser [email protected] http://www.marnen.org _______________________________________________ bug-lilypond mailing list [email protected] https://lists.gnu.org/mailman/listinfo/bug-lilypond
