On Sun, 29 Dec 2002, Stas Bekman wrote:
> [EMAIL PROTECTED] wrote:
>
> Hi Randy,
>
> I wasn't closely following the win32 docs commits, but I've noticed a
> few things from this commit that I wanted to comment on.
>
> The idea behind perl.apache.org/docs/ is to have a consistent
> documentation, with minimum duplication across different docs.
>
> So rather than duplicating all the relevant docs for win32 I suggest to
> try hard to have only win32 specific material under win32/ and
> crossreference to the main docs where possible. In the long run this
> will keep the docs more maintainable. I hope that this is doable without
> ruining the win32 user's learning/referencing experience. What do you
> think? Comment below.
Hi Stas,
Thanks for the comments ... I agree with this intent -
some comments below ....
>
> > -Obtain the mod_perl sources from CPAN:
> > -
> > - http://www.cpan.org/authors/id/D/DO/DOUGM/mod_perl-1.xx.tar.gz
> > -
> > +Obtain the mod_perl sources (F<mod_perl-1.xx.tar.gz>) from CPAN
> > +under L<http://www.cpan.org/authors/id/D/DO/DOUGM/>.
> > When unpacked, using Winzip or similar tools, a subdirectory
> > F<mod_perl-1.xx> will be created.
>
> I'd rather point to http://perl.apache.org/download/, where the latest
> version is automatically linked to.
I think I'd prefer F<mod_perl-1.0-current.tar.gz> from
L<http://perl.apache.org/dist/> - the page
http://perl.apache.org/download/ contains an
"Installation" link which takes one out of the
section describing how to build mod_perl on Windows.
>
> > @@ -210,6 +203,20 @@
> > Apache and mod_perl header files, which can then be accessed
> > through the Apache::src module.
> >
> > +If this build fails, you may want to try the sources obtained
> > +from cvs (you may also want to use the Apache cvs sources).
> > +To do this, first obtain a Win32 cvs client from, for example,
> > +L<http://www.cvshome.org/>. The cvs sources may be obtained as
> > +
> > + C:\src> cvs -d :pserver:[EMAIL PROTECTED]:/home/cvspublic login
> > + C:\src> cvs -d :pserver:[EMAIL PROTECTED]:/home/cvspublic co apache-1.3
> > + C:\src> cvs -d :pserver:[EMAIL PROTECTED]:/home/cvspublic co modperl
> > +
> > +The build then proceeds as above. Be aware, though,
> > +that as well as providing bug fixes, there may be new features being
> > +added and tested in the cvs versions, so at any given time there are
> > +no guarantees that these packages will build and test successfully.
> > +
> > =head1 Binaries
>
> Any reason to duplicate docs? We already have this documented at:
> http://perl.apache.org/download/source.html#Development_Source_Distribution
OK - I'll change that to link to the cvs-specific anchor ... One
reason I put the cvs stuff there is that, as before,
http://perl.apache.org/download/source.html contains
"Installation" links that takes one outside of the realm of
building mod_perl on Win32.
>
> > discussion of Apache-2 and modperl-2.
>
> Can we please have consistently Apache 2.0 and mod_perl 2.0? Notice that
> Apache 2.1 is not the same as Apache 2.0, so Apache-2 is definitely not
> a good choice.
OK ... One thing I was worried about was introducing a
"mod_perl 2.0" when that doesn't officially exist yet, and
people then getting confused when browsing CPAN and
finding mod_perl-1.99_xx instead. Or, at
http://perl.apache.org/dist/, thinking mod_perl-2.0-current
is (at present) different from mod_perl-1.99_xx. But I'll
put a note in the relevant place to that effect.
>
> > Having built and installed Apache 2.0, next obtain the mod_perl 2.0
> > -sources from http://www.cpan.org/authors/id/D/DO/DOUGM/. After
> > +sources (F<mod_perl-1.99_xx>)
> > +from L<http://www.cpan.org/authors/id/D/DO/DOUGM/>. After
> > unpacking, run the command
>
> Same here, better point to perl.apache.org/download/
and as above, I think I'd prefer F<mod_perl-2.0-current.tar.gz>
from L<http://perl.apache.org/dist/>, with a note about
mod_perl-2.0 being in development.
>
> > C:\modperl_src> perl Makefile.PL MP_AP_PREFIX=\Path\to\Apache2
> > @@ -106,7 +107,7 @@
> > official releases, you may want to try the sources obtained
> > from cvs (it is a good idea to also use the cvs httpd-2.0 sources).
> > To do this, first obtain a Win32 cvs client from, for example,
> > -http://www.cvshome.org/. The cvs sources may be obtained as
> > +L<http://www.cvshome.org/>. The cvs sources may be obtained as
> >
> > C:\src> cvs -d :pserver:[EMAIL PROTECTED]:/home/cvspublic login
> > C:\src> cvs -d :pserver:[EMAIL PROTECTED]:/home/cvspublic co httpd-2.0
> > @@ -127,8 +128,8 @@
>
> similar as for 1.3, a pointer to /download/ would be better.
and as above ...
>
> If things change, we need to adjust only one place and all the docs
> already point to the latest info.
I'll look at making the above changes ... I can certainly see the
wisdom in not duplicating things, but that I think has to be
partly balanced against the "danger" of taking Win32 users to
pages that have Unix-specific links.
--
best regards,
randy
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
