lilypond-devel
[Top][All Lists]
Advanced

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

Re: Building info with images in 2.13.44


From: Dave Plater
Subject: Re: Building info with images in 2.13.44
Date: Thu, 30 Dec 2010 00:02:28 +0200
User-agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.1.16) Gecko/20101125 SUSE/3.0.11 Thunderbird/3.0.11

On 12/29/2010 11:29 PM, Graham Percival wrote:
> On Wed, Dec 29, 2010 at 12:40:57PM +0200, Dave Plater wrote:
>   
>> On 12/28/2010 10:11 PM, Graham Percival wrote:
>>     
>>> On Tue, Dec 28, 2010 at 05:12:56PM +0200, Dave Plater wrote:
>>>   
>>>       
>>>> "lilypond/html/input/lsr" and
>>>> "lilypond/html/Documentation/user"
>>>>         
>>>   
>>> Yes; those directories were removed 1-2 years ago.  I recommend
>>> that you start by building the docs normally/natively (make doc)
>>> and then looking at the directory structure in
>>> out-www/offline-root/ .  I would imagine that the current dir
>>> structure of the info stuff will closely (or exactly) mirror the
>>> current out-www/ dir structure.
>>>   
>>>       
>> Does that mean that I can disable the macro and let the script compress
>> all the info files and no links to the docdir are needed?
>>     
> Sorry, I have no clue what this means.
>
> Cheers,
> - Graham
>
>   
Examining the 2.13.44.1 doc tarball info directory, there is one link
"lilypond" so I still need the macro to override the part of rpmbuild
that compresses any file or link in the info or man directories because
otherwise the link "lilypond" would become lilypond.gz and the
"html/Documents" directory it links to will become ""html/Documents.gz".
The macro enables me to create the link after rpmbuild has gz compressed
all the contents of the info and man directories thereby ensuring that
the link and target aren't affected.
Hope this clarifies my previous ramblings a bit.
Dave P.



reply via email to

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