You are viewing a plain text version of this content. The canonical link for it is here.
Posted to docs-cvs@perl.apache.org by go...@apache.org on 2004/11/19 23:17:10 UTC
svn commit: r105889 - perl/modperl/docs/trunk/src/download
Author: gozer
Date: Fri Nov 19 14:17:09 2004
New Revision: 105889
Modified:
perl/modperl/docs/trunk/src/download/docs.pod
Log:
Update docs download section to SVN
Modified: perl/modperl/docs/trunk/src/download/docs.pod
==============================================================================
--- perl/modperl/docs/trunk/src/download/docs.pod (original)
+++ perl/modperl/docs/trunk/src/download/docs.pod Fri Nov 19 14:17:09 2004
@@ -14,24 +14,22 @@
=head1 Download
-The mod_perl documentation lives in the C<cvs.apache.org> CVS
+The mod_perl documentation lives in the C<svn.apache.org> Subversion
server. To get it, you will need to checkout a copy. Assuming you have
-CVS installed, run the following commands from the directory you want
-to place the I<modperl-docs> directory in:
+Subversion installed, run the following command from the directory you
+want to place the I<modperl-docs> directory in:
- % cvs -d:pserver:anoncvs@cvs.apache.org:/home/cvspublic login
- (use the password "anoncvs")
- % cvs -d:pserver:anoncvs@cvs.apache.org:/home/cvspublic co modperl-docs
+ % svn co http://svn.apache.org/repos/asf/perl/modperl/docs/trunk modpe
You will now find a directory called I<modperl-docs> in the current
working directory which contains all the sources needed to build the
-site. See the L<CVS Howto|contribute::cvs_howto> for more information.
+site. See the L<Subversion Howto|contribute::svn_howto> for more information.
-Another way to download the sources, if you don't want to use CVS, is
-to get the snapshots available from
+Another way to download the sources, if you don't want to use Subversion,
+is to get the snapshots available from
http://cvs.apache.org/snapshots/modperl-docs/ . However, it will be a
major drag for you to keep these up to date, so you are better advised
-to use the CVS access.
+to use the Subversion access.
=head1 Build
@@ -41,7 +39,7 @@
=head2 Prerequisites
-DocSet: while it is included with the CVS distribution, please
+DocSet: while it is included with the Subversion distribution, please
download it from CPAN and install the latest version. It will install
the tool C<html2ps>, which is needed to build the PDF version, and
also a number of Perl modules (it will tell you the Perl modules
@@ -88,11 +86,11 @@
so you might want to follow the L<docs-cvs mailing
list|maillist::docs-cvs> to see when changes are made.
-Once you see a change is made, you need to update your CVS working
-copy, and re-build the site (although it will only rebuilt modified
-files).
+Once you see a change is made, you need to update your Subversion
+working copy, and re-build the site (although it will only rebuild
+modified files).
- % cvs up
+ % svn up
% bin/build
Rebuilding the PDF version is just as easy, just run:
@@ -109,8 +107,8 @@
=head1 Submitting documentation patches
We warmly welcome any updates to the documentation. To send us a
-documentation patch, please update your CVS tree, and then, depending
-on the patch:
+documentation patch, please update your Subversion tree, and then,
+depending on the patch:
=over
@@ -122,10 +120,10 @@
=item *
If you only add a paragraph/modify a line, please make sure you have
-the I<latest> CVS version, and then issue:
+the I<latest> Subversion version, and then issue:
% cd modperl-docs
- % cvs diff -u > patch
+ % svn diff -u > patch
And send the I<patch> file to the maintainer or the L<documentation
mailing list|maillist::docs-dev>, preferably inlined in your e-mail
@@ -136,7 +134,7 @@
do:
% cd modperl-docs
- % cvs diff -u src/docs/2.0/api/Apache/RequestUtil.pod > patch
+ % svn diff -u src/docs/2.0/api/Apache/RequestUtil.pod > patch
This approach will get the diff of only that file.
@@ -220,7 +218,7 @@
$flags .= 'd' if $name =~ /pdf/;
$flags = $flags ? "-$flags" : "";
- system("cvs up -dP >/dev/null 2>&1");
+ system("svn up >/dev/null 2>&1");
system("bin/build $flags");
---------------------------------------------------------------------
To unsubscribe, e-mail: docs-cvs-unsubscribe@perl.apache.org
For additional commands, e-mail: docs-cvs-help@perl.apache.org
Re: svn commit: r105889 - perl/modperl/docs/trunk/src/download
Posted by "Philippe M. Chiasson" <go...@ectoplasm.org>.
Stas Bekman wrote:
> Philippe M. Chiasson wrote:
>
>> Stas Bekman wrote:
>>
>>> gozer@apache.org wrote:
>>>
>>>> - % cvs -d:pserver:anoncvs@cvs.apache.org:/home/cvspublic login
>>>> - (use the password "anoncvs")
>>>> - % cvs -d:pserver:anoncvs@cvs.apache.org:/home/cvspublic co
>>>> modperl-docs
>>>> + % svn co http://svn.apache.org/repos/asf/perl/modperl/docs/trunk
>>>> modpe
>>>
>>>
>>>
>>>
>>> I thought we were first trying to figure out what's the best way to
>>> go (on the dev list). I'd prefer to see https:// here. So let's
>>> agree on things first, before we change those back and forse. Thanks.
>>
>>
>>
>> Nah, in this case, telling users to checkout modperl thru http will
>> be just fine. They will simply get the docs/ and Apache-Test/
>> externals out as https without even needing to know/notice. So no
>> harm in recommending http for read-only for at least the
>> modperl repository itself.
>
>
> Developers (especially the new ones) will get burned by this. I
> suggest we use https:// everywhere.
Well, if by developers you mean the people with rw access to the
repository, I don't think it'a a big deal to tell
them to use https instead of http, just like developers right now with
cvs need to switch from anoncvs to ssh tunneled
cvs. Or am I getting this wrong ? In either case, the simple thing is:
Read-only access, pick one of http/https, same difference
Read-write access, pick https.
Personally, if people think this might be confusing, I have no strong
objections to recommending https across the board.
Re: svn commit: r105889 - perl/modperl/docs/trunk/src/download
Posted by Stas Bekman <st...@stason.org>.
Philippe M. Chiasson wrote:
> Stas Bekman wrote:
>
>> gozer@apache.org wrote:
>>
>>> - % cvs -d:pserver:anoncvs@cvs.apache.org:/home/cvspublic login
>>> - (use the password "anoncvs")
>>> - % cvs -d:pserver:anoncvs@cvs.apache.org:/home/cvspublic co
>>> modperl-docs
>>> + % svn co http://svn.apache.org/repos/asf/perl/modperl/docs/trunk
>>> modpe
>>
>>
>>
>> I thought we were first trying to figure out what's the best way to go
>> (on the dev list). I'd prefer to see https:// here. So let's agree on
>> things first, before we change those back and forse. Thanks.
>
>
> Nah, in this case, telling users to checkout modperl thru http will be
> just fine. They will simply get the docs/ and Apache-Test/
> externals out as https without even needing to know/notice. So no harm
> in recommending http for read-only for at least the
> modperl repository itself.
Developers (especially the new ones) will get burned by this. I suggest we
use https:// everywhere.
--
__________________________________________________________________
Stas Bekman JAm_pH ------> Just Another mod_perl Hacker
http://stason.org/ mod_perl Guide ---> http://perl.apache.org
mailto:stas@stason.org http://use.perl.org http://apacheweek.com
http://modperlbook.org http://apache.org http://ticketmaster.com
---------------------------------------------------------------------
To unsubscribe, e-mail: docs-dev-unsubscribe@perl.apache.org
For additional commands, e-mail: docs-dev-help@perl.apache.org
Re: svn commit: r105889 - perl/modperl/docs/trunk/src/download
Posted by "Philippe M. Chiasson" <go...@ectoplasm.org>.
Stas Bekman wrote:
> gozer@apache.org wrote:
>
>> - % cvs -d:pserver:anoncvs@cvs.apache.org:/home/cvspublic login
>> - (use the password "anoncvs")
>> - % cvs -d:pserver:anoncvs@cvs.apache.org:/home/cvspublic co
>> modperl-docs
>> + % svn co http://svn.apache.org/repos/asf/perl/modperl/docs/trunk
>> modpe
>
>
> I thought we were first trying to figure out what's the best way to go
> (on the dev list). I'd prefer to see https:// here. So let's agree on
> things first, before we change those back and forse. Thanks.
Nah, in this case, telling users to checkout modperl thru http will be
just fine. They will simply get the docs/ and Apache-Test/
externals out as https without even needing to know/notice. So no harm
in recommending http for read-only for at least the
modperl repository itself.
Re: svn commit: r105889 - perl/modperl/docs/trunk/src/download
Posted by Stas Bekman <st...@stason.org>.
gozer@apache.org wrote:
> - % cvs -d:pserver:anoncvs@cvs.apache.org:/home/cvspublic login
> - (use the password "anoncvs")
> - % cvs -d:pserver:anoncvs@cvs.apache.org:/home/cvspublic co modperl-docs
> + % svn co http://svn.apache.org/repos/asf/perl/modperl/docs/trunk modpe
I thought we were first trying to figure out what's the best way to go (on
the dev list). I'd prefer to see https:// here. So let's agree on things
first, before we change those back and forse. Thanks.
--
__________________________________________________________________
Stas Bekman JAm_pH ------> Just Another mod_perl Hacker
http://stason.org/ mod_perl Guide ---> http://perl.apache.org
mailto:stas@stason.org http://use.perl.org http://apacheweek.com
http://modperlbook.org http://apache.org http://ticketmaster.com
---------------------------------------------------------------------
To unsubscribe, e-mail: docs-dev-unsubscribe@perl.apache.org
For additional commands, e-mail: docs-dev-help@perl.apache.org