At 16:18 12.05.2002, Stas Bekman wrote:
Well, I think we just do as I said there. Replace "Win32" with "Operating System specific details", put those files into that directory, and leave it at that. Right now, we're not doing anything special with the Win32 docs, and I don't think anything more is needed.
so you simply suggest to move 1.0/win32 to 1.0/docs/guide/win32?
No, I'm saying to move 1.0/win32 to 1.0/os/win32, and leave the 1.0/os/ directory ready for other OSes.
So if someone grabs the PDF of the guide, he doesn't get the OS specific parts. On the other hand if we put them all in the guide, then the PDF will be bloated with stuff not interesting to all. But still it's better to have more than less, don't you think? I know a bunch of people who simply print out the guide's PDF, bind it and give to their employees to read.
I'm in favor of having OS specific details in their own documents. This will allow to have separate maintainers do their best without stepping on each other toes.
But would like to hear other opinions whether to have these OS-specific chapters in the guide or in parallel to it?
__________________________________________________________________
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]
