one question we should rethink is whether to have docs in their own
modperl-2.0-docs cvs tree on all in a modperl-2.0/docs subdirectory.
i'm pretty sure cvs allows access control so certain people can write to
docs/ but not ../
the other reason for the split is if we want to release docs more often
than the rest of the distribution. if docs/ is self contained similar to
Apache-Test (with its own Makefile.PL, MANIFEST, etc.), one can cd docs/
and 'make dist' for a seperate docs package. when the modperl-2.0 package
is built from the top-level it will automatically include the docs thanks
to MakeMaker subdir recursion. but, it docs live in
modperl-2.0/../modperl-2.0-docs, we need todo special Makefile.PL magic to
pick up that directory, which i think will be somewhat messy.
the other question is should docs for modules live inlined in the .pm's or
be in docs/pod/lib/Apache/FooModule.pod ? i would think the latter so the
pdf and other doc magic stas plans can be applied to the module docs.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
