[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [opensuse-contrib] lilypond
From: |
Jan Nieuwenhuizen |
Subject: |
Re: [opensuse-contrib] lilypond |
Date: |
Mon, 04 Jan 2010 19:54:17 +0100 |
Op maandag 04-01-2010 om 19:09 uur [tijdzone +0200], schreef 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,
> > 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.
Nothing gets downloaded when you build the documentation
by doing "make web".
The pre-built documentation ball is available primarily for users that
do not want to, or do not succeed in building the docs. It contains
what gets built by doing "make web; make web-install"
> 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?
I don't see much difference in the source rpm's size. Either way it
contains just all of lilypond. When downloading the prebuilt doc ball,
you download ~98MB more; stuff that you otherwise all build locally.
> 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.
Ah. Then you probably also did not comment-out "make web" and added
downloading the documentation tarball. Best to revert that, I think.
I did not invent the brp-symlink and brp-compress; although I can take
a guess as to what they do [hint: man symlink, man compress]. This
magic was just copied from the original __os_install_post macro
in the rpm lib; with added rm and ln fixings.
> 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..
Interesting.
Jan.
--
Jan Nieuwenhuizen <address@hidden> | GNU LilyPond - The music typesetter
AvatarĀ®: http://AvatarAcademy.nl | http://lilypond.org
- [opensuse-contrib] lilypond, Dave Plater, 2010/01/04
- Re: [opensuse-contrib] lilypond, Jan Nieuwenhuizen, 2010/01/04
- Re: [opensuse-contrib] lilypond, Dave Plater, 2010/01/04
- Re: [opensuse-contrib] lilypond,
Jan Nieuwenhuizen <=
- Re: [opensuse-contrib] lilypond, Jan Nieuwenhuizen, 2010/01/04
- Re: [opensuse-contrib] lilypond, Dave Plater, 2010/01/04
- Message not available
- Message not available
- Message not available
- Re: [opensuse-contrib] lilypond, Jan Nieuwenhuizen, 2010/01/05
- Re: [opensuse-contrib] lilypond, Dave Plater, 2010/01/05
- Interrupted builds: gs should remove broken output? [Re: [opensuse-contrib] lilypond], Jan Nieuwenhuizen, 2010/01/05
- Re: Interrupted builds: gs should remove broken output? [Re: [opensuse-contrib] lilypond], Dave Plater, 2010/01/06
Re: [opensuse-contrib] lilypond, Dave Plater, 2010/01/04