On Wed, 28 Mar 2001, Doug MacEachern wrote:

> i like the idea, the pdf output i've seen from your modules is really
> slick!  before moving forward, i think we should consider creating a
> modperl-2.0-docs repository, similar to what httpd does, splitting up its
> docs and code.  the mod_perl-2.0 dist can include the docs (or subset of),
> but a seperate repository makes it easier to maintain:
>
> - different release schedules (example: docs might be released more often
> than code)
>
> - different groups of people working on docs and code
>
> and if it turns out to be a bad idea, we can always merge the docs
> repository with the code and kill the -docs repository

+1

> the only requirements i personally have for the new system are:
>
> - we can still write docs in plain old pod :)
>
> - .pod's are installed so pod2man, perldoc and friends still work for
>   mod_perl docs as expected

which means, standard pod, which is how it works. My package provides some
other extended syntax, which I've developed for the book, but nobody has
to use it. Pod::HtmlPsPdf handles the plain pod just fine.


_____________________________________________________________________
Stas Bekman              JAm_pH     --   Just Another mod_perl Hacker
http://stason.org/       mod_perl Guide  http://perl.apache.org/guide
mailto:stas@stason.org   http://apachetoday.com http://logilune.com/
http://singlesheaven.com http://perl.apache.org http://perlmonth.com/



---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@perl.apache.org
For additional commands, e-mail: dev-help@perl.apache.org