[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Moving CVS repository

From: Joi Ellis
Subject: Re: Moving CVS repository
Date: Thu, 2 May 2002 15:38:27 -0500 (CDT)

On Thu, 2 May 2002, Greg A. Woods wrote:

> [ On Thursday, May 2, 2002 at 13:39:06 (-0400), Eric Siegerman wrote: ]
> > Subject: Re: Moving CVS repository
> >
> > On Wed, May 01, 2002 at 01:42:44PM -0500, Joi Ellis wrote:
> > >   find . -type f -name 'Root' | \
> > >      xargs perl -pi.bak -e 's/localhost/some.hostname/'
> > > [...]
> > > I prefer using perl rather than a 'cp' because some of our modules
> > > are nested and I don't trust the Root file to be identical all
> > > through the tree.  Maybe they are, maybe they aren't.
> > 
> > Agreed.
> If I'm not mistaken the CVS/Root file _MUST_ be identical throughout an
> entire module's working directory, regardless of whether module aliases
> are used or not.  A given working directory _MUST_ always come from the
> same repository.
> (Of course idiot users could maybe manually check out one module from
> another repository into the same working directory, but they lose and
> that's just too bad for them, IMNSHO!  :-)

Yes, that is true. 

However, this isn't what I said.  I said users often nest modules.  This is
particularly common in Java applications.  There is at least one IDE that
leads its users into building such bastard workspaces.  I see this come
up a lot on the JBuilder newsgroups because JBuilder doesn't support
nested modules well (if at all) but users are trying to coerce JBuilder
into adjusting itself to an existing nested workspace.

Module A:

Module B:

     dir B1
     dir B2

In this sort of nested workspace, one can't simply cp a Root file from
the top of the workspace into all of the subdirectories because B's
Root is different.

Joi Ellis                    Software Engineer
Aravox Technologies          address@hidden, address@hidden

No matter what we think of Linux versus FreeBSD, etc., the one thing I
really like about Linux is that it has Microsoft worried.  Anything
that kicks a monopoly in the pants has got to be good for something.
           - Chris Johnson

reply via email to

[Prev in Thread] Current Thread [Next in Thread]