Have you checked out the 'svn:externals' property at all? We use it
for similar things. See
$ svn co http://svn.collab.net/repos/cvs2svn/trunk/
...for an example of how svn:externals is used this way. (I don't
think it will solve all your problems, for example not the Project D
scenario, but it might help with some of your needs).
-Karl
glenn <gdavy@tpg.com.au> writes:
> Bad subject, but didn't know how to phrase it.
>
> I'm looking for some clear thinking about how I should approach this
> situation. Many of you must have been here before me.
>
> In this scenario:
>
> I have my a set of includes that I maintain in their own right and
> include in a number of other projects. Lets call these project A
>
> So now I want to start project B, which includes project A, but will be
> version controlled in its own right, as A is also now included in
> project C.
>
> So when working on B, I fix a couple of bugs in B's copy of A, and
> perhaps add an enhancement, and at some point I'm going to want to
> commit these back, and update them to C, and of course vice versa.
>
> At the moment I"m keeping A in its own working copy, and using symbolic
> links, but I don't see this as a durable solution. Esp when multiple
> users and machines get involved.
>
> Just to complicate things Project D, may be established, and would like
> to only inherit the bug fixes, but not the new features, and perhaps
> more dramatic changes and re-organisings of A which could de-stablise
> it.
>
> Please, can any one suggest how I can tackle this?
>
> Thanks
> Glenn
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
> For additional commands, e-mail: users-help@subversion.tigris.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Wed Jun 2 18:40:42 2004