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.
>
>   
>> 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
>
>   
snip

> Greetings,
> Jan.
>   
Disregard what I said about building the documentation although it seems
to take a long time. The "make web" target no longer exists, I'm trying
it out with "make doc", there is a "make WEB_TARGETS=" but I don't think
thats what "make web" was. What would happen if I extracted the
documentation tarball into `out-www' ?
Regards
Dave P