On Mar 1, 2012, at 3:12 PM, lilyp...@googlecode.com wrote: > > Comment #28 on issue 2338 by colingh...@gmail.com: OS X LilyPad not working > http://code.google.com/p/lilypond/issues/detail?id=2338 > > Right. I'll contact Christian and ask him to tar up his dev directory then. > > Otherwise, is my outline of the work involved to get to a patch correct? >
Yup - the idea is that we want grahms fork of LilyPad to produce a reliable LilyPad from scratch. I think it's worth it to do this to get 2.16 out. Afterwards, we should do some brainstorming about better ways to package manage. For example, brew has a lilypond OS X port of the stable version and jEdit can be used. If these become the "Mac OS X" instructions on the webpage, people will actually get a better UI than if they download what we bundle. It then becomes necessary that developer resources be spent on maintaining these packages, but it seems like this is a better (and more decentralized) use of our time than maintaining a GUI text editor. Cheers, MS _______________________________________________ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
