lilypond-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Avoid Python!


From: Jan Nieuwenhuizen
Subject: Re: Avoid Python!
Date: Sun, 22 Jan 2006 11:55:45 +0100
User-agent: Gnus/5.110004 (No Gnus v0.4) Emacs/22.0.50 (gnu/linux)

Werner LEMBERG writes:

> A very critical point of view w.r.t. Python is here:
>
>   http://plan99.net/autopackage/Linux_Problems
>
> I wasn't aware of this problem at all...

I do not consider this to be a problem at all, this is a fact of life.
IMNSHO, the autopackage developers could do with a cluebat.  Don't
worry, we will not be using autopackage much longer; we have already
dropped autopackage for 2.7.x.

The autopackage developers are fast to point out that the wole world
and their dog are broken, eg. every linux distribution is broken in
several ways, the FHS is broken, etc.

Yet, they do not really seem to listen to the other side's arguments,
or care about other's brokenness, but rather assume everyone is
clueless and work around it all and `fix' it in the great autopackage
structure.  Somehow the whole world does not want to be helped, but
wants to ship broken software.

When I suggested to file bugs with Red Hat and Debian instead of
whining, this post is what happened

    https://www.redhat.com/archives/fedora-devel-list/2005-October/msg00261.html

(Nothing was posted to Debian, because Debian never fixes any bugs
anyway).  Especially notice this

    Here are a few I noticed a while back - apologies if these have
    changed in rawhide or if I am misremembering

Han-Wen and I could not convince them that /usr is off-limits for
third party software.  When they would not take patches from Han-Wen
for cross compilation, we decided to drop autopackage.  As soon as
2.6.x is available in GUB binaries, we'll send the autopackage
developers an official goodbye notice.

Jan.

-- 
Jan Nieuwenhuizen <address@hidden> | GNU LilyPond - The music typesetter
http://www.xs4all.nl/~jantien       | http://www.lilypond.org




reply via email to

[Prev in Thread] Current Thread [Next in Thread]