apr-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Greg Stein <gst...@lyra.org>
Subject Re: [lists@rowe-clan.net: Re: CVS rename?]
Date Mon, 14 May 2001 21:10:11 GMT
On Mon, May 14, 2001 at 04:04:09PM +0200, Luke Kenneth Casson Leighton wrote:
> > > It is safe to move a file. That is all we're talking about.
> > 
> > Safe?  Well certainly inconsiderate.
> > 
> no, it's not safe to move a file.
> what happens if you wish to compile an older version?

Please re-read my initial statement:

We haven't done a release yet and we don't need the history of the files in
their old locations. Just go into /home/cvs/... on dev.apache.org and 'mv'
the files.

Special precautions are only needed if we want to preserve history (in the
old location) and/or we have tagged the files under their old names.          

> try this:
> cvs co ... -D '2 days ago'
> oh, whoops, why doesn't it compile?  i don't understand, the Makefile
> says there's a file there, but where is the file?

Fuck it. We don't need it.

> it's actually better to move directories around than it is to
> move individual files, but only if the directory and its
> subdirectories are self-contained and not referenced via any
> other Makefiles, scripts, includes, libs etc.

No. This isn't possible at all. The CVS client will see files disappear from
the repository and simply unhook them in the working copy. No harm, no foul.
But if you move a *directory*, then everything gets fucked. The client can't
recover. The user has to manually edit CVS/Entries to deal with the change.

Directory moves are *never* good.

File moves are fine, IFF you don't care about the history of that file.

> and yes, if someone starts moving directories, you're better
> off doing a total re-checkout.

It is edit CVS/Entries or a new checkout. But if you have changes, then you
have one option, and you better know a lot of CVS/Entries.


Greg Stein, http://www.lyra.org/

View raw message