At 15:02 24.04.2002, Stas Bekman wrote: >Per Einar Ellefsen wrote: > >>All the other Apache:: core modules docs have been integrated into the >>site and changed style there too. Should these be re-submitted into the core? > >What we can do is to go the modperl-2.0 way for modperl-1.0, i.e. strip >the pm files from pod and let the modperl-docs/src/docs/1.0 be checked out >into the modperl tree.
Would this make them usable by just doing 'perldoc Apache::*' ? I think that's needed, becausae it's the first place anyone looks. >The drawback (or the benefit :) is the size of this directory, mostly >added by the size of the guide: > >du -s src/docs/1.0/* >184 src/docs/1.0/api >16 src/docs/1.0/CVS >172 src/docs/1.0/faqs >1460 src/docs/1.0/guide >56 src/docs/1.0/win32 > >which compressed becomes 531k, bringing the dist tar.gz from 380k to about >800k (twice more). That's bad. Too big probably. >The biggest benefit is that we will have all the docs in one place and >they will be searchable/browsable on the site, without needed to sync with >the core every time there is a change. What we can do instead: DocSet supports .pm files. So we could get docs/1.0/api aliased in some way to all the modperl-1 modules, so that when you check out you get the Perl Module files. The problem is that these are very spread out in the mod_perl source tree, so it'll be hard to extract them correctly. -- Per Einar Ellefsen [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
