[EMAIL PROTECTED] writes: > On Thu, 19 Feb 2004, Han-Wen Nienhuys wrote: > > > [EMAIL PROTECTED] writes: > > > I'm now using Lilypond. I just installed 2.1.25, and noticed a couple of > > > small things: > > > > > > 1. The lilypond-documentation Fedora Linux RPM installs docs in > > > /usr/share/doc/lilypond. Strictly it should be in > > > /usr/share/doc/lilypond-documentation-2.1.25 (i.e. with the same name as > > > the RPM and with the version number). > > > > This is intentional: we can refer to the docs as being in > > /usr/share/doc/lilypond regardless of version and platform. > > I don't think that's a good enough excuse for breaking the naming rules, > and I think there are better ways of achieving the same results. I haven't > even seen any instructions on where to find the docs, but if I did want to > look for them I'd look at man lilypond. This helpfully tells me that I can > look at info lilypond for the full docs: no need to worry about paths. It > could be made even more useful by having a note in the man page and info > docs that there are also HTML and PDF versions; the paths to them can > easily be inserted at build time.
That's actually slightly hairy, since proper documentation paths are distribution dependendent. > If you wanted to make it really useful you could integrate the HTML and > PDF docs with the other documentation readers like scrollkeeper (I don't > know anything about this; I'm quite happy to use man, info and rpm -ql to > find my documentation). Great idea, it could've mine! In fact, it was. I added OMF files to the -documentation RPM a year ago, and couldn't work out how to get Yelp or kde-help to display them. Then I gave up. > Finally, a tip you may want to include in the FAQ or Wiki: I started (The whole point of a wiki is that you add it yourself.) -- Han-Wen Nienhuys | [EMAIL PROTECTED] | http://www.xs4all.nl/~hanwen _______________________________________________ Bug-lilypond mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/bug-lilypond
