[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: migration of an CVS-repository with aliases

From: Karl Fogel <kfogel_at_red-bean.com>
Date: Sat, 10 May 2008 03:21:40 -0400

Branko Čibej <brane_at_xbc.nu> writes:
> Well Karl, here's a nicely documented use case for my proposal for
> server-side aliases instead of externals, in the thread that
> culminated in http://svn.haxx.se/dev/archive-2008-04/1139.shtml. This
> one falls under the "CVS Modules done right" heading.

*nod* Thank you, it does help to have this concrete example (not, of
course, that it would have been that hard to construct, but... "cache
reality" is always a good principle).

I think the long-discussed idea of "viewspecs" (first proposed here by
David James IIRC, though of course he was just importing an idea from
other version control systems) is what we're really talking about. And
there's no reason a viewspec can't be just a versioned file (insert
appropriate hand-waving here). Which is short for "+1, but now it needs
to be designed".

-Karl

> Thomas wrote:
>> Hi there,
>>
>> Our CVS repository structure looks like this:
>>
>> cvs_root
>> |--module_one
>> | |--import <- alias to module_two/export
>> | |--src
>> | |--...
>> |
>> |--module_two
>> |--export
>> |--src
>> |--...
>>
>> during checkout or update of module_one the files from module_two/
>> export are also checked out or updated to module_one/import. no
>> problem so far. also tagging and branching of module_one modifies the
>> files in module_two/export.
>> now we wnat to migrate our repository to svn but i did not figure out,
>> how to handle this with svn. the svn:externals seem not be useful as
>> the tagging and branching will not affect the files linked with the
>> externals command. right?
>>
>> does anybody have an idea how to handle this with a pre-commit-hook? i
>> do not have an idea how to write one but think, this would be an
>> option.
>>
>> thx in advance
>> thomas
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe_at_subversion.tigris.org
>> For additional commands, e-mail: dev-help_at_subversion.tigris.org
>>
>>

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: dev-help_at_subversion.tigris.org
Received on 2008-05-10 09:22:04 CEST

This is an archived mail posted to the Subversion Dev mailing list.