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 ge...@apache.org on 2004/11/19 17:27:30 UTC
svn commit: r105829 - perl/modperl/docs/trunk/src/docs/2.0/user/install
Author: geoff
Date: Fri Nov 19 08:27:29 2004
New Revision: 105829
Modified:
perl/modperl/docs/trunk/src/docs/2.0/user/install/install.pod
Log:
start the svn migration documentation
Modified: perl/modperl/docs/trunk/src/docs/2.0/user/install/install.pod
==============================================================================
--- perl/modperl/docs/trunk/src/docs/2.0/user/install/install.pod (original)
+++ perl/modperl/docs/trunk/src/docs/2.0/user/install/install.pod Fri Nov 19 08:27:29 2004
@@ -128,7 +128,7 @@
=head2 Getting Bleeding Edge CVS Sources
-If you really know what you are doing you can use the cvs versions of
+If you really know what you are doing you can use the cvs/svn versions of
the components. Chances are that you don't want to them on a
production site. You have been warned!
@@ -158,35 +158,33 @@
=item Apache
-To download the cvs version of httpd-2.0 and bring it to the same
+NOTE: as of November 17, 2004 httpd has moved to subversion.
+
+To download the svn version of httpd-2.0 and bring it to the same
state of the distribution package, execute the following commands:
- % cvs -d :pserver:anoncvs@cvs.apache.org:/home/cvspublic login
+For httpd 2.0 (the stable Apache 2.0 branch)
-The password is "anoncvs". Now extract the C<APACHE_2_0_BRANCH> branch
-of httpd-2.0.xx. If you don't use this branch you will get
-httpd-2.1.xx which at this moment is not supported. Similarly you need
-C<APR_0_9_BRANCH> and C<APU_0_9_BRANCH> cvs branches for apr and
-apr-util projects, respectively.
-
- % cvs -d :pserver:anoncvs@cvs.apache.org:/home/cvspublic co \
- -r APACHE_2_0_BRANCH -d httpd-2.0 httpd-2.0
- % cd httpd-2.0/srclib
- % cvs -d :pserver:anoncvs@cvs.apache.org:/home/cvspublic co \
- -r APR_0_9_BRANCH -d apr apr
- % cvs -d :pserver:anoncvs@cvs.apache.org:/home/cvspublic co \
- -r APU_0_9_BRANCH -d apr-util apr-util
- % cvs -d :pserver:anoncvs@cvs.apache.org:/home/cvspublic co \
- -r APU_0_9_BRANCH -d apr-iconv apr-iconv
- % cd ..
- % ./buildconf
+ $ svn checkout http://svn.apache.org/repos/asf/httpd/httpd/branches/2.0.x/ httpd-2.0
+ $ cd httpd-2.0/srclib
+ $ svn checkout http://svn.apache.org/repos/asf/apr/apr/branches/APR_0_9_BRANCH/ apr
+ $ svn checkout http://svn.apache.org/repos/asf/apr/apr-util/branches/APU_0_9_BRANCH/ apr-util
+ $ cd ..
+ $ ./buildconf
Once extracted, whenever you want to sync with the latest httpd-2.0
version and rebuild, run:
- % cd httpd-2.0
- % cvs up -dP
- % make distclean && ./buildconf
+ $ cd httpd-2.0
+ $ svn update
+ $ make distclean && ./buildconf
+
+For httpd 2.1 (the development Apache 2.0 branch) use this instead
+
+ $ svn checkout https://svn.apache.org/repos/asf/httpd/httpd/trunk/ httpd-2.1
+ $ cd srclib
+ $ svn checkout http://svn.apache.org/repos/asf/apr/apr/trunk/ apr
+ $ svn checkout http://svn.apache.org/repos/asf/apr/apr-util/trunk/ apr-util
=back
@@ -285,18 +283,28 @@
or an equivalent command.
-=item CVS Bleeding-Edge Version
+=item SVN Bleeding-Edge Version
+
+NOTE: as of November 17, 2004 mod_perl 2.0 has moved to subversion.
-To download the cvs version of modperl-2.0 execute the following
+To download the svn version of mod_perl-2.0 execute the following
commands:
- % cvs -d :pserver:anoncvs@cvs.apache.org:/home/cvspublic login
+ $ svn checkout http://svn.apache.org/repos/asf/perl/modperl/trunk/ mod_perl-2.0
+
+Current mod_perl developers with commit access will need to use https instead:
+
+ $ svn checkout https://svn.apache.org/repos/asf/perl/modperl/trunk/ mod_perl-2.0
-The password is "anoncvs".
+META: missing Apache-Test information
- % cvs -d :pserver:anoncvs@cvs.apache.org:/home/cvspublic co modperl-2.0
+In order to commit for the first time you will need to update your
+password. To do that, log in to svn.apache.org and run the command "svnpasswd":
-You can also try the latest CVS snapshot:
+ $ ssh svn.apache.org
+ $ svnpasswd
+
+You can also try the latest cvs snapshot:
http://cvs.apache.org/snapshots/modperl-2.0/
---------------------------------------------------------------------
To unsubscribe, e-mail: docs-cvs-unsubscribe@perl.apache.org
For additional commands, e-mail: docs-cvs-help@perl.apache.org
Re: svn commit: r105829 - perl/modperl/docs/trunk/src/docs/2.0/user/install
Posted by Geoffrey Young <ge...@modperlcookbook.org>.
>> +In order to commit for the first time you will need to update your
>> +password. To do that, log in to svn.apache.org and run the command
>> "svnpasswd":
>
>
> Eh? ssh keys don't work with svn?
svnpasswd is in the documents everywhere, from geronimo to
http://www.apache.org/dev/version-control.html. my ssh key allowed me to
log in to svn.apache.org without a password, but was insufficient to allow
me to commit anything.
IIRC there is no way around svnpasswd - if you could commit you might have
done it before?
--Geoff
---------------------------------------------------------------------
To unsubscribe, e-mail: docs-dev-unsubscribe@perl.apache.org
For additional commands, e-mail: docs-dev-help@perl.apache.org
Re: svn commit: r105829 -
perl/modperl/docs/trunk/src/docs/2.0/user/install
Posted by Frank Wiles <fr...@wiles.org>.
On Fri, 19 Nov 2004 14:29:43 -0800
"Philippe M. Chiasson" <go...@ectoplasm.org> wrote:
> Bingo! Right on. I was talking to infra folks and they are looking
> into the future and administering
> 1000+ unix users with shell accounts is much much more complex than if
>
> these 1000 accounts are
> all confined within the realm of a htaccess file ;-)
Yeah, but these days with PAM and other nifty utilities you can get
rid of the actual accounts, store them in a SQL database, etc. and
mitigate the headache a ton.
But I can understand their reluctance as I believe the SVN docs
specifically say that svn+https is the only method they really focus
on.
---------------------------------
Frank Wiles <fr...@wiles.org>
http://www.wiles.org
---------------------------------
---------------------------------------------------------------------
To unsubscribe, e-mail: docs-dev-unsubscribe@perl.apache.org
For additional commands, e-mail: docs-dev-help@perl.apache.org
Re: svn commit: r105829 - perl/modperl/docs/trunk/src/docs/2.0/user/install
Posted by "Philippe M. Chiasson" <go...@ectoplasm.org>.
Frank Wiles wrote:
>On Fri, 19 Nov 2004 17:09:45 -0500
>Stas Bekman <st...@stason.org> wrote:
>
>
>
>>Philippe M. Chiasson wrote:
>>[...]
>>
>>
>>>Yeah, it sucks++ and it's a major issue I have with https+svn. But
>>>it's only going to get worste
>>>once we move over to ssl client certificate authentication ... The
>>>only thing needed is the same
>>>thing as ssh-agent, but for ssl keys.
>>>
>>>
>>Why is it worse?
>> I'm surprised they want to use https+svn since I've found ssh+svn to
>> be much faster and less resource intensive on the box.
>>
>>
That's indeed the case.
>> I'm sure however that the administration of https+svn is probably
>> less than ssh+svn since it doesn't require Unix users, keys, etc.
>>
>>
Bingo! Right on. I was talking to infra folks and they are looking into
the future and administering
1000+ unix users with shell accounts is much much more complex than if
these 1000 accounts are
all confined within the realm of a htaccess file ;-)
Re: svn commit: r105829 -
perl/modperl/docs/trunk/src/docs/2.0/user/install
Posted by Frank Wiles <fr...@wiles.org>.
On Fri, 19 Nov 2004 17:09:45 -0500
Stas Bekman <st...@stason.org> wrote:
> Philippe M. Chiasson wrote:
> [...]
> >>>> Eh? ssh keys don't work with svn?
> >>>
> >>> Nope, svn works over https instead. SVN does support an
> >ssh-tunneled >> mode, but the
> >>> people on infrastructure@apache.org prefer https access over it.
> >It >> will only ask for your
> >>> password once (caching it in your ~/.svn/ dir a bit like cvs
> >pserver >> used to do)
> >>
> >> Hmm, the password is stored in clear text :( that sucks.
> >
> > Yeah, it sucks++ and it's a major issue I have with https+svn. But
> > it's only going to get worste
> > once we move over to ssl client certificate authentication ... The
> > only thing needed is the same
> > thing as ssh-agent, but for ssl keys.
>
> Why is it worse?
I'm surprised they want to use https+svn since I've found ssh+svn to
be much faster and less resource intensive on the box.
I'm sure however that the administration of https+svn is probably
less than ssh+svn since it doesn't require Unix users, keys, etc.
---------------------------------
Frank Wiles <fr...@wiles.org>
http://www.wiles.org
---------------------------------
---------------------------------------------------------------------
To unsubscribe, e-mail: docs-dev-unsubscribe@perl.apache.org
For additional commands, e-mail: docs-dev-help@perl.apache.org
Re: svn commit: r105829 - perl/modperl/docs/trunk/src/docs/2.0/user/install
Posted by "Philippe M. Chiasson" <go...@ectoplasm.org>.
Stas Bekman wrote:
> Philippe M. Chiasson wrote:
>
>> Stas Bekman wrote:
>>
>>> Philippe M. Chiasson wrote:
>>> [...]
>>>
>>>> Yeah, it sucks++ and it's a major issue I have with https+svn. But
>>>> it's only going to get worste
>>>> once we move over to ssl client certificate authentication ... The
>>>> only thing needed is the same
>>>> thing as ssh-agent, but for ssl keys.
>>>
>>> Why is it worse?
>>
>> Because then you'd _really_ need to type password every time you
>> update/checkin, etc.
>
> But you said that ssh-agent like thing resolves it. Are you saying
> that there is no such thing?
No such thing indeed. All in all, these things are in the hands of the
infrastructure folks at apache.org
and we'll have to wait and see what they setup in the future.
Gozer.
Re: svn commit: r105829 - perl/modperl/docs/trunk/src/docs/2.0/user/install
Posted by Stas Bekman <st...@stason.org>.
Philippe M. Chiasson wrote:
> Stas Bekman wrote:
>
>> Philippe M. Chiasson wrote:
>> [...]
>>
>>>
>>> Yeah, it sucks++ and it's a major issue I have with https+svn. But
>>> it's only going to get worste
>>> once we move over to ssl client certificate authentication ... The
>>> only thing needed is the same
>>> thing as ssh-agent, but for ssl keys.
>>
>>
>>
>> Why is it worse?
>
>
> Because then you'd _really_ need to type password every time you
> update/checkin, etc.
But you said that ssh-agent like thing resolves it. Are you saying that
there is no such thing?
--
__________________________________________________________________
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: r105829 - perl/modperl/docs/trunk/src/docs/2.0/user/install
Posted by Stas Bekman <st...@stason.org>.
Philippe M. Chiasson wrote:
[...]
>>>> Eh? ssh keys don't work with svn?
>>>
>>> Nope, svn works over https instead. SVN does support an ssh-tunneled
>>> mode, but the
>>> people on infrastructure@apache.org prefer https access over it. It
>>> will only ask for your
>>> password once (caching it in your ~/.svn/ dir a bit like cvs pserver
>>> used to do)
>>
>> Hmm, the password is stored in clear text :( that sucks.
>
> Yeah, it sucks++ and it's a major issue I have with https+svn. But it's
> only going to get worste
> once we move over to ssl client certificate authentication ... The only
> thing needed is the same
> thing as ssh-agent, but for ssl keys.
Why is it worse?
> In the meantime, you can also tell svn _never_ to store passwords and
> type it every time. That's
> what I do.
No, thank you.
--
__________________________________________________________________
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: r105829 - perl/modperl/docs/trunk/src/docs/2.0/user/install
Posted by Stas Bekman <st...@stason.org>.
Philippe M. Chiasson wrote:
> Stas Bekman wrote:
>
>> geoff@apache.org wrote:
>>
>>> - % cvs -d :pserver:anoncvs@cvs.apache.org:/home/cvspublic co
>>> modperl-2.0
>>> +In order to commit for the first time you will need to update your
>>> +password. To do that, log in to svn.apache.org and run the command
>>> "svnpasswd":
>>
>>
>>
>> Eh? ssh keys don't work with svn?
>
>
> Nope, svn works over https instead. SVN does support an ssh-tunneled
> mode, but the
> people on infrastructure@apache.org prefer https access over it. It will
> only ask for your
> password once (caching it in your ~/.svn/ dir a bit like cvs pserver
> used to do)
Hmm, the password is stored in clear text :( that sucks.
Thanks Philippe!
--
__________________________________________________________________
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: r105829 - perl/modperl/docs/trunk/src/docs/2.0/user/install
Posted by Stas Bekman <st...@stason.org>.
geoff@apache.org wrote:
> Author: geoff
> Date: Fri Nov 19 08:27:29 2004
> New Revision: 105829
>
> Modified:
> perl/modperl/docs/trunk/src/docs/2.0/user/install/install.pod
[...]
> - % cvs -d :pserver:anoncvs@cvs.apache.org:/home/cvspublic co modperl-2.0
> +In order to commit for the first time you will need to update your
> +password. To do that, log in to svn.apache.org and run the command "svnpasswd":
Eh? ssh keys don't work with svn?
--
__________________________________________________________________
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