On Fri, 2005-05-06 at 10:04 -0400, James Laska wrote:
On Thu, 2005-05-05 at 16:45 -0700, Karsten Wade wrote:
> Karsten: Assign task of making docs use common files in ./ instead of
> ../, in order to work for separate modules per document.
I can see the benefits of going both paths (centralized vs decentralized
configs). Is there a lot of demand for local xsl customization in the
fedora-docs/* documents?
Actually, I don't think there would be that much demand, because it
would be a hindrance to consistency. Karsten, there should be a pretty
easy way to get modules to automatically "include" a checkout of the
common stuff. In the CVSROOT/modules file, simply insert this near the
top of the list. (The list itself is a little hinky, and could probably
use some trimming, since it has a bunch of entries that don't match
existing stuff in the repository.)
base common css scripts xsl
Then, for any directories containing docs (i.e. modules), do:
module module &base
The name "module" would be the name of the directory used for the
module, i.e. "translation-guide," "jargon-buster," etc. The other
four
modules will come down automatically along with the requested module.
Look at the Extras CVSROOT/modules for examples -- there are plenty of
them! :-)
The nice thing about this scenario is that the CVS maintainer will
always be on top of what's added into CVS, since that person will be
adding a module definition into CVSROOT/modules for the new document.
There's no need to change the way we're doing business, existing
Makefiles all stay the same, and the use of "../common/*" doesn't
change.
--
Paul W. Frields, RHCE
http://paul.frields.org/
gpg fingerprint: 3DA6 A0AC 6D58 FEC4 0233 5906 ACDB C937 BD11 3717
Fedora Documentation Project:
http://fedora.redhat.com/projects/docs/