You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@avalon.apache.org by "Farr, Aaron" <Aa...@am.sony.com> on 2004/03/17 18:57:12 UTC
Switch to Subversion Promptly (WAS: RE: Mortician at Work)
> -----Original Message-----
> From: Noel J. Bergman [mailto:noel@devtech.com]
>
> I believe that due to the way in which Avalon wants to re-organize and
> re-factor the code, it is absolutely imperative that we switch to
> Subversion
> promptly. Otherwise we will shortly have a code base where the active
> code
> has been completely disassociated from its development history.
>
> I don't believe that I can possibly get across how totally unacceptable I
> find the current situation.
If subversion solves this problem, then I'm +1 for the switch.
Noel,
What all would be involved in moving to svn? I think in the end we would
like to just have:
avalon
avalon-components
avalon-sandbox
avalon-site
Would we need to temporarily move excalibur into svn and then into
avalon-components, or could we keep excalibur in CVS and then move from
there directly into avalon-components (in svn) while still preserving
revision history? (I hope I'm being clear)
J. Aaron Farr
SONY ELECTRONICS
DDP-CIM
(724) 696-7653
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@avalon.apache.org
For additional commands, e-mail: dev-help@avalon.apache.org
RE: Switch to Subversion Promptly (WAS: RE: Mortician at Work)
Posted by Alex Karasulu <ao...@bellsouth.net>.
Wooops I think we responded at the same time to this on Aaron...
+1 for me too on a subversion switch now on this thread this time.
Alex
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@avalon.apache.org
For additional commands, e-mail: dev-help@avalon.apache.org
RE: Switch to Subversion Promptly (WAS: RE: Mortician at Work)
Posted by "Noel J. Bergman" <no...@devtech.com>.
> There's also TortoiseSVN (Windows) and RapidSVN (Windows/Linux),
> for us who need a GUI to hug...
And Subclipse and IDEA integration. The http://scm.tigris.org site lists
the tools.
--- Noel
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@avalon.apache.org
For additional commands, e-mail: dev-help@avalon.apache.org
RE: Switch to Subversion Promptly (WAS: RE: Mortician at Work)
Posted by Leo Sutic <le...@inspireinfrastructure.com>.
There's also TortoiseSVN (Windows) and RapidSVN (Windows/Linux),
for us who need a GUI to hug...
/LS
> From: Noel J. Bergman [mailto:noel@devtech.com]
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@avalon.apache.org
For additional commands, e-mail: dev-help@avalon.apache.org
RE: Switch to Subversion Promptly (WAS: RE: Mortician at Work)
Posted by "Noel J. Bergman" <no...@devtech.com>.
> Seriously, I'm +1 even if I have to work. Using CVS was a
> pain when I reorganized excalibur-logger.
FWIW, I run Subversion on a relatively old RH 6.2 (linux 2.2 kernel) box.
It does not have all of the necessary parts installed, nor do I feel like
updating it just for Subversion, to be a Subversion server. Who cares? I
just need a client. So I downloaded the source tarball, and did:
tar zxvf subversion-1.0.1.tar.gz
cd subversion-1.0.1
./configure --with-ssl --enable-all-static
make
The --with-ssl is important, since otherwise you will not have SSL support.
I added the --enable-all-static because I wanted one statically linked
client, even it it is 5MB. No fuss, no muss, no dependencies. If you want
to do the same thing, add --without-berkeley-db to ensure that it won't
build the server.
--- Noel
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@avalon.apache.org
For additional commands, e-mail: dev-help@avalon.apache.org
RE: Switch to Subversion Promptly (WAS: RE: Mortician at Work)
Posted by Leo Sutic <le...@inspireinfrastructure.com>.
> From: Noel J. Bergman [mailto:noel@devtech.com]
>
> > What all would be involved in moving to svn?
>
> Request to infrastructure, who would do the CVS to SVN
> conversion. One of the things we might want to resolve at
> that time would be repairing (if
> possible) some of the disassociations we have already done.
> But the experts don't include me. :-) They do, however,
> include Greg, Justin, Sander and Fitz.
Clear improvement && no work for me involved -> +2 from me.
(Lazy consensus with emphasis on lazy.)
Seriously, I'm +1 even if I have to work. Using CVS was a
pain when I reorganized excalibur-logger.
/LS
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@avalon.apache.org
For additional commands, e-mail: dev-help@avalon.apache.org
RE: Switch to Subversion Promptly (WAS: RE: Mortician at Work)
Posted by "Noel J. Bergman" <no...@devtech.com>.
> If subversion solves this problem, then I'm +1 for the switch.
It does. You have to copy and rename the files using Subversion, so that it
can track the operation.
> What all would be involved in moving to svn?
Request to infrastructure, who would do the CVS to SVN conversion. One of
the things we might want to resolve at that time would be repairing (if
possible) some of the disassociations we have already done. But the experts
don't include me. :-) They do, however, include Greg, Justin, Sander and
Fitz.
[As a side note, since it does not exist in the current code, I was
commenting last night that I thought it would be very cool if a future
enhancement to cvs2svn used a variation of Eric Raymond's shred-based
comparator to help detect and repair disassociations.]
> I think in the end we would like to just have:
> avalon
> avalon-components
> avalon-sandbox
> avalon-site
Actually, that would be:
http://svn.apache.org/repos/asf/avalon/
http://svn.apache.org/repos/asf/avalon/components
http://svn.apache.org/repos/asf/avalon/sandbox
http://svn.apache.org/repos/asf/avalon/site
But you can reorganize it however you want, once the content is present.
> Would we need to temporarily move excalibur into svn and then into
> avalon-components, or could we keep excalibur in CVS and then move
> from there directly into avalon-components (in svn) while still
> preserving revision history?
Think of Subversion as a versioned file system with a DAV interface. One of
its lovely properties is that when you tell this file system to copy a file,
the file's history is preserved. So if we have:
http://svn.apache.org/repos/asf/avalon/excalibur
and we want to move any or all of it, we just tell Subversion to do that,
and it does it without losing track of any historical information. In fact,
when you move it, I can still check out an old version from the old
location. The entire virtual file system has history, including moves and
copies.
--- Noel
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@avalon.apache.org
For additional commands, e-mail: dev-help@avalon.apache.org