"Jason E. Stewart" wrote:
> 
> "Murray Cumming" <[EMAIL PROTECTED]> writes:
> 
...
> > Actually, it *would* be better to just rename src to xercesc and stop
> > copying the headers into include.
> 
> That does seem like an elegant solution.
> 
> One drawback is that it does mean mucking with the CVS repo, though
> (unless you want to remove and then add all the files back under
> xercesc -- Yuccchhh).
> 
> I would definately vote for this approach over the include/xercesc

I like that too. I don't have a pb with "mucking with the CVS repo".
I've done it several times. It's not ideal but there is no good solution
anyway. CVS is just not good at that type of operation.
For those who don't know, what it means is that someone goes in the CVS
repository and simply renames the directory there. The consequences are:

Every copy checked out stops working. Everyone needs to either start
with a new checkout or rename the directory in their version and update
the relevant CVS/Entries file manually.
It also means checking out an older version will give you a bogus
checkout, in which the new name is used instead of the old ones.

On the other hand, every file keeps all its history (logs and diffs) and
it doesn't cost any additional diskspace in the repository.

In the "official" way, moving a file simply means creating a new one
under the new directory, and removing the files under the old directory.
This means the history of every file is split in two. The version
numbers and logs are reset.


There is an intermediate solution which consists of copying all the
repository from the old directory to the new one. The advantage is that
it doesn't break anybody, it doesn't break checkouts of older version
(even though you'd get more files than there were), the history of every
file is complete so logs and diffs keep working.
But it costs a lot of diskspace on the repository.
-- 
Arnaud  Le Hors - IBM, XML Standards Strategy Group / W3C AC Rep.

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to