[Top][All Lists]

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

Re: pending LilyPond removal from debian release ?

From: Anthony Fok
Subject: Re: pending LilyPond removal from debian release ?
Date: Tue, 22 Jun 2004 11:38:45 +0800
User-agent: Mutt/1.5.6+20040523i

On Mon, Jun 21, 2004 at 10:10:32PM +0200, Jan Nieuwenhuizen wrote:
> What about the removal report and the gs bug, I assume that this
> >   * gs-gpl 8.01 (and gs-afpl 8.14) dies when building LilyPond docs.
> >     (Known -sDEVICE=bbox bug in gs 8.01 and newer, see gs-gpl Bug#250290.)
> >     Added Build-Conflict-Indep: gs-gpl (>= 8.01) | gs-afpl (Closes: 
> > Bug#250622)
> takes care of that?

Yes, I think so.  I tried out gs 7.07 (gs-esp), gs-gpl 8.01 and gs-afpl
8.14.  It turns out that only 7.07 still works.  The newer versions fail
because -sDEVICE=bbox causes gs just segfaults.

> > if possible, please remove these files from the upstream source
> > tree:
> >
> >     debian/lilypond1.7*.dirs
> >     debian/lilypond.dirs
> >     debian/postinst
> >     debian/prerm
> >     debian/postrm
> Done.  Will debian users be able to build the package without these
> files, or will you send a patch?  [I assume so, just tried 2.2.3 CVS
> with the files removed but got another silly error
> mv debian/lilypond/usr/share/lilypond/2.2.3/dvips/ \
>    debian/lilypond/etc/texmf/dvips/
> mv: cannot move `debian/lilypond/usr/share/lilypond/2.2.3/dvips/' 
> to `debian/lilypond/etc/texmf/dvips/': Unknown file or directory
> make: *** [binary-arch] Error 1
> debuild: fatal error at line 763:
> but I am assuming this is already fixed somewhere so I'm leaving it for now]

Oh, sorry, I should have been more clear.  What I meant is "please
remove these files from the upstream source tree after applying the
lilypond_2.2.2-2.diff.gz patch."  :-)

Since is architecture-independent and goes with all the font
data, I decided to put it with the fonts in the new "lilypond-data" package.
After that, the two lines should become:

        mv debian/lilypond-data/usr/share/lilypond/2.2.3/dvips/ \

Comes from these two lines in debian/rules:

        mv $(r_data)/usr/share/lilypond/$(VERSION)/dvips/ \

r_data = "root of data package" = debian/lilypond-data
(Hoho, I got some strange variable names in there.

> > Many thanks!  :-)
> Thank you!
> Jan.

Thank you!  :-)  It's my duty.

Actually, I have an ulterior motive for finally updating lilypond too
because I will hopefully be finding some time to actually use it again
soon.  I joined a local Catholic parish here in Beijing in recent months
and joined the parish youth choir (about 16-20 people?), and seeing the
overall lack of resource in liturgical and sacred music scores, I
thought LilyPond could really help here.  :-)

As you may know, most music scores here in China use the "numerical
notation" (or simple notation), e.g.:

C  2/4

  | 5   3 4  |  5   3 4  |  5  5 6  |  5  -  |  3  -  |
        ---         ---        ---

Sometimes with the 5-line staff underneath, sometimes without.  So yes,
I was glad to see that Joshua Koo asking a similar question on
lilypond-user, and is thinking how to go about that... whether numerical
notation could be typeset today with LilyPond, or with scheme extension,
or need to write C++ code.  Hmm...  Any help or pointers would be great.

Many thanks,


reply via email to

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