On Tue, Nov 06, 2007 at 12:05:47PM -0800, [EMAIL PROTECTED] wrote: > Juan Manuel Palacios <[EMAIL PROTECTED]> writes: > > Content organization put aside, we have to figure a way to tie "make > >man" in the doc-new dir with our make system in trunk/base, so that > > 1) > >the regular "./configure && make && make install" dance (called > >either when installing from source of while selfupdating) gets a set > >of shiny new pages.... > > 2) > >or are you thinking of regen'ing them manually > >in trunk/doc-new and copying them over to trunk/base/doc/ when you > >think it's OK to "cut a release" for them? > > I would think option 1 would be best, unless there is a consensus > otherwise. I'm cc'ing doc team on this. I'd prefer "live" docs with head > as now. I haven't thought about what Makefile changes would be necessary, > and since the other doc team members are better programmers, I probably > wouldn't be the one to do it anyway. > > Mark
Hi, I also think 1) is the best way. But there is one problem: To make sure everybody gets the documentation when checking out a copy from svn we either have to move the documentation in the base/doc directory or use svn:externals so it gets downloaded. And as not everybody has a docbook installation on their computer the man pages should be generated before each release and included in the source tarballs. But we have to be "careful" no one modifies the man pages as they are then automatically generated and so any change will be overwritten. Maybe the easiest way is copy the man pages manually before each release. We could add a target to the Makefile of the documentation to move the generated man pages to a given directory, which could be useful for developers to simplify the update process for them. What do you think is the best way to achieve this? Thanks, Simon -- + privacy is necessary + using http://gnupg.org + public key id: 0x6115F804EFB33229
pgpNV5V8ipD85.pgp
Description: PGP signature
_______________________________________________ macports-dev mailing list [email protected] http://lists.macosforge.org/mailman/listinfo/macports-dev
