Wasup Billy-O and Hiya Every1,
One of the easier ways to do this will be to use "symbolic links" on the
svn filesystem. Unfortunately AFAIK, this is not yet implemented, but is
one of the objectives of the dev. team.
Maybe for now it would be easier to maintain 2 diff projects. One for your
base code and one for your new code.

Hector.

> Hey all,
>
> I have been thinking about using subversion at work, hopefully
> replacing the existing source control program.  But there is a feature
> in our existing system that we use quite often.
> Basically, we have a set of common base code.  When we release a new
> product, all the base code is included along with some product
> specific code.  All the products are based on this common base code.
> In our current system, we can link this common base code into the
> different products we produce.  This gives us the freedom to update
> the common base code and all the products will automatically get the
> updates (because they are linked instead of copies of the common base
> code).
> Is there any way to do this in subversion?
>
> Thanks,
> -Bill Nelson
>
> _______________________________________________
> RLUG mailing list
> [EMAIL PROTECTED]
> http://lists.rlug.org/mailman/listinfo/rlug
>


_______________________________________________
RLUG mailing list
[EMAIL PROTECTED]
http://lists.rlug.org/mailman/listinfo/rlug

Reply via email to