Hi Ben,
Thanks for the info! This is indeed very close to what I was asking for.
They effectively allow one to link a project with another. Do you mind if
I push a little deeper in relation to that topic?
Do you know if there is a way to link only *some* files within the external
project?
ie using my previous example, if I had a "common" directory containing a
heap of
common files (say mybutton.h, mystring.h etc etc), I could link that entire
"common" directory in, but not a small subset - which would be cumbersome
if I only required one or two files from that common project.
The need for developers to reuse common code or classes in many different
projects would be reasonably widespread I would imagine, so I assume that
this concept has been tackled before. There must be a conventional way of
handling such a situation.
I possibly asked the wrong question.
What would be the recommended way of reusing an old file in a new project -
let's say "mystring.h"?
Do subversion users generally make a separate copy it and allow it to live
as a different file to all the other copies of that file? What is the
best way of making sure that any bugfixes to that file make their way out
to all other projects with their own copy of that file?
Thanks,
Chris Rogers
At 10:06 AM 23/07/2004, Ben Reser wrote:
>I think you'll want to look into svn:externals.
>You can read about them here in the book:
>http://svnbook.red-bean.com/svnbook/ch07s03.html
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Mon Jul 26 07:27:50 2004