Re: [opensuse-contrib] lilypond

[Dave Plater]

On 01/04/2010 05:11 PM, Jan Nieuwenhuizen wrote:
> Op maandag 04-01-2010 om 15:33 uur [tijdzone +0200], schreef Dave
> Plater:
>
> Hi Dave,
>
> Thanks for mailing us about this!
>
>   
>> I'm the current maintainer of lilypond in openSUSE:Contrib and am in the 
>> process of updating to version 2.12.3.I'm currently having a
>> bit of a problem with the info files and info is an area that is new to me 
>> as far as packaging and creating are concerned.
>> 1) The man page for lilypond-invoke-editor points to the info page which 
>> gives a copy of the man page and there is no
>> lilypond-invoke-editor.info to be found. Have I done something wrong or is 
>> this a bug as there is no info page in the documentation package
>> or built with the package at all?
>>     
> There is no lilypond-invoke-editor.info -- I think you found a bug 
> (sort of), this is a general remark for [GNU] help2man man pages.
>
> Is there a reason not to build the documentation?  It would be good
> to know for lilypond developers as well as openSUSE users that
> everything they see in the manual actually can be and was
> created on SUSE.
>
> Another /big/ advantage of building the documentation is that you/we
> can say to openSUSE users to do
>
>   zypper source-install -d lilypond-documentation
>
> and they be ready to build lilypond themselves.
>   
I'm assuming that the documentation tarball which is 98 meg in size
contains the same documentation as gets built and downloaded from the
web by the other method. In which case the documentation rpm will still
be the same size and the source rpm will be smaller but when building
you will end up downloading a lot more than the doc tarball. Am I right
in my assumption?
>   
>> 2) I would like to be able to make a package with the info images available 
>> but ATM can't get this right. Everything packaged under the
>> info directory gets compressed and has a .gz extension even where the two 
>> links link to. I'm not sure if this is the problem. ATM I delete
>> the two links, lilypond, lilypond-snippets and the files 
>> lilypond-snippets.info-images-dir-dep and lilypond.info-images-dir-dep which 
>> I
>> assume are related to this.
>>     
> Yes, that's related.  The openSUSE extended info install check blindly
> gzips everything it finds, including the target of symlinks that do
> not exist.
>
> The symlinks will help emacs find the images, there need be two
>
>    usr/share/info/lilypond --> ../../doc/lilypond/html/Documentation/user
>    usr/share/info/lilypond-snippets --> ../../doc/lilypond/input/lsr
>
> or somesuch.  I think we used to print a helpful/warning message
> when installing the documentation -- esp. for distributions when
> they install not in /usr but for packaging reasons - but that seems
> to be gone now [John, Graham?]
>
> Have you seen/read this section in the rpm that you (or at least 
> is now) commented out?
>
> This is/was to work around this gzipping thing
>
>     # brp-compress ignorantly compress the symlink (or directory) for Info 
> images.
>     #      ERROR: link target doesn't exist (neither in build root nor in 
> installed system):
>     #      /usr/share/info/lilypond-snippets.gz -> 
> /usr/doc/packages/lilypond/html/input/lsr/.gz
>     #%define __os_install_post \
>     #    %{suse_check} \
>     #    /usr/lib/rpm/brp-compress \
>     #    (cd %{buildroot}/usr/share/info; \
>     #      rm -f lilypond.gz; \
>     #      ln -sf ../doc/packages/lilypond/html/Documentation/user lilypond; \
>     #      rm -f lilypond-snippets.gz; \
>     #      ln -sf ../doc/packages/lilypond/html/input/lsr lilypond-snippets) \
>     #    /usr/lib/rpm/brp-symlink
>   
This makes sense, I had already tried restoring the links almost the
same way as you have done, the documentation tarball now uses the path
/usr/share/docs/lilypond and I moved everything to
/usr/share/docs/packages/lilypond and had to recreate the links, I don't
know the brp-compress and brp-symlink tricks though, what do they do? I
will uncomment this section and play with it now I know what its for, it
was already commented out when I took over.
>   
>> 3) install_info complains about lilypond-learning.info and 
>> lilypond-programming.info not having DIR headers, I examined the other info
>> files and made patches (usr/ is where I unpack the documentation) :-
>>     
> Hmm, I don't think you need to install-info these files, all
> necessary headers should be available in lilypond.info,
> lilypond-internals.info and music-glossary.info
>
> eg, this
>
>   
>> --- usr/share/info/lilypond-learning.info       2009-12-15
>> 22:08:29.000000000 +0200
>> +++ usr/share/info/lilypond-learning.info       2010-01-03
>> 19:28:30.762962562 +0200
>> @@ -1,3 +1,9 @@
>> +INFO-DIR-SECTION GNU LilyPond -- the music typesetter
>> +
>> +START-INFO-DIR-ENTRY
>> +* LilyPond Learning Manual: (lilypond-learning).      Start here.
>> +END-INFO-DIR-ENTRY
>> +
>>     
> is in lilypond.tely [and thus lilypond.info] as:
>
>     * LilyPond Learning Manual: (lilypond-learning).  Start here.
>     * LilyPond Internals Reference: (lilypond-internals).  Definitions for 
> tweaking.
>     * LilyPond Application Usage: (lilypond-program). Installing and running 
> applications.
>
> Greetings,
> Jan.
>   
The lilypond-learning and programming infos look cleaner at the top with
the INFO-DIR-SECTION but they still work without it and those two infos
weren't in the previous documentation at least not in the spec file..
Regards and happy new year
Dave P