lilypond-devel
[Top][All Lists]
Advanced

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

Distribution updates and documentation woes


From: Jan Nieuwenhuizen
Subject: Distribution updates and documentation woes
Date: Thu, 15 Jan 2009 16:43:01 +0100

Hi,

After 2.12 I decided to do my small round checking of distributions 
again (should we add something like this to release tasks?).  

Fedora already has 2.12 (yay!), while Debian and Ubuntu already had 2.12
wishlist bugs filed (great!), but none of the major distributions
manages to provide proper images in the Info docs.  Time for action!

Debian
    http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=511676  2.12
    http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=511773  no images in Info 
docs

Ubuntu
    https://bugs.launchpad.net/ubuntu/+source/lilypond/+bug/312544  2.12
    https://bugs.launchpad.net/ubuntu/+source/lilypond/+bug/317067  no images 
in Info docs

openSUSE
    https://bugzilla.novell.com/show_bug.cgi?id=466437  2.12, docs as unbuilt 
texinfo sources
    [but also: GPL 2 or later, extremely terse description, stale list of 
Authors,
     non-optimized build, etc.]

Fedora

Fedora is a special case, it uses our prebuilt documentation ball, so
no simple patch can be provided.  I think we need to fix this, other
distributions may also go this way of using our pre-built doco.  How
to fix images in Info docs for Fedora?

  - distribute lilypond-info-man.tar.bz2 alongside documentation ball?
  - roll info (and man?) docs into documentation ball
     + How?  docbal currently is rooted at ./Documentation,
       info would need to be moved to/unpacked at ../../info .
  - suggest make web, make web-install + adding of symlink

See
    
http://ftp.nluug.nl/pub/os/Linux/distr/fedora/linux/development/source/SRPMS/lilypond-doc-2.12.1-1.fc11.src.rpm

IWBN if a fedora user would file the wishlist/bug once we settle on a fix.


LilyPond.org

And last but not least: what about our own documentation builds?  Info
docs are missing here altogether!  Should we include info docs and
re-root the documentation ball to look like

   share/doc/lilypond/Documentation/*
   share/info/dir
   share/info/*

and/or provide a shar archive to extract the documentation into
a proper place?

Jan.

-- 
Jan Nieuwenhuizen <address@hidden> | GNU LilyPond - The music typesetter
http://www.xs4all.nl/~jantien       | http://www.lilypond.org





reply via email to

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