Re: Cannot open LilyPond

[David Kastrup]

Hanno <address@hidden> writes:

> David Kastrup <dak <at> gnu.org> writes:
>
>> If you compare the release dates for LilyPond 2.14.2 and MacOSX 10.7.3,
>> it should be obvious that a bug report does not make much sense before
>> actually cross-checking with the latest unstable release reflecting more
>> recent developments.
>> 
>
> Wait a minute - if I go to a web page and I see there is a download for Mac OS
> X, I can assume that it's working as long as there is no hint that it might 
> not.
> So, 
> it would really make sense to add a hint on the Mac download page that the 
> last
> stable version might not work with Lion.
>
> By the way - it would be really nice if you'd just answer by "The last stable
> version does not work with Mac OS 10.7.3. We did not have the man power to
> develop a newer one yet. So please use the unstable version or wait for a new
> stable release." 
>
> Maybe you wanted to be funny, but it sounded more like a hidden accusation. As
> described, I do not think that I NEED to check an unstable version if there is
> no hint of it on the page.
>
> The unstable version starts correctly by the way. 

You don't understand apparently that LilyPond is run by volunteers and
not by your underlings.

I don't use MacOSX at all, so I would have _no_ _clue_ _whatsoever_ what
runs and what runs not with what error symptoms.

The expected turnaround time for bug reports is several days.  You would
have needed this about three times.  I was just helping in reducing that
time for you, and all you have for that is sneers and disdain.

Do you think you will improve the support volunteers not even involved
with MacOSX will deliver for MacOSX in that manner?

Most people processing and even _fixing_ your problem have nothing to do
with MacOSX.  By treating them like human trash, regardless of whether
you personally consider them as such, you don't really improve what they
will be willing to do for your sake.

-- 
David Kastrup