At 06:35 12.05.2002, Stas Bekman wrote:
Per Einar Ellefsen wrote:
Haven't found any problems yet, but I have one suggestion: instead of having a Win32 section under 1.xx, let's make it an "OS-specific instructions" section, so we could put MacOS/Cygwin/foo instructions there. If I ever get mod_perl 1.x to work on Cygwin, I'll try and write up some stuff, and I think we have enough working installations for MacOS X to get some help for that too.
Yes, we weren't sure how to do that the best. On one side it's nice to have everything in one doc to minimize dups. But if each OS specific part grows big a separate doc makes more sense. I think win32 docs are big. That's said we could move them out of win32/ and put under guide/, e.g. install_win32.pod, config_win32.pod, etc.
We have the same issue with 2.0 stuff, but here is easier: we have 2.0/install/install.pod (for generic stuff), platform specific stuff can go into 2.0/install/win32.pod, etc. What do you think?
Hmm, I think that for 1.x we only need an os-specific section. Then we just make "groups" inside that instead of even more different docsets. We won't have too much information, but it'll be too much to stick into the "User's guide" (which is more than big enough already).
I don't understand you, Per Einar. You say that we make the section (not separate docs), but then you say it'll be too big (which is exactly my concern). Look at the win32, the docs are relatively big, no?
__________________________________________________________________ Stas Bekman JAm_pH ------> Just Another mod_perl Hacker http://stason.org/ mod_perl Guide ---> http://perl.apache.org mailto:[EMAIL PROTECTED] http://use.perl.org http://apacheweek.com http://modperlbook.org http://apache.org http://ticketmaster.com
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
