Re: Issue 2338 in lilypond: OS X LilyPad not working

[lilypond]

Comment #13 on issue 2338 by address@hidden: OS X LilyPad not working
http://code.google.com/p/lilypond/issues/detail?id=2338

Regarding comment #11:

> David -- I know exactly what needs to be done.  I'm not doing it because  
> I don't want to be doing it.

Believe it or not: I have no beef with that.  I have no interest in  
providing CP/M support for LilyPond either though I probably would be the  
best qualified person among those reading these lists.

I have no sympathy for the "you should be doing it because you are better  
at it than me" stance.  It is not just that it is a lot of work to do for  
somebody else, it is also that it is _totally_ _inefficient_ work since  
those whom it would concern are not even stepping up for _timely_ and  
_reliable_ feedback.  This farce has been going on for _months_.

We have to adapt our decisions and planning to our resources.  And I have  
not seen anything to suggest that our resources permit declaring OSX a  
supported platform, one where a failure in components will be considered  
release-critical.

You have made the last OSX release cycle "because David is such a nice  
guy", as bad a reason as any I can imagine.  And lo-and-behold, it was in  
vain since it appears you integrated a tarball that was basically unchecked  
in an important component.  And caused another extended delay with no end  
in sight.

Even if you were willing to do this song-and-dance routine again and again,  
I would feel _totally_ silly asking for it.  And I am not "such a nice guy"  
that I would take over such a futile task and stop working on things that  
actually lead to results.

I don't see any way around stopping to guarantee LilyPad (and likely other  
components) to work as delivered under MacOSX.  We can point to the  
respective web sites, and to our source code.  And then it is up to the OSX  
users how they deal with that.