Help moving from a CVS paradigm!

Hi all,

I am a user of CVS, investigating the option of moving to Subversion.

I have a (newbie) question, which reveals my lack of understanding of how
subversion is supposed to work. I hope someone can shine some light on it
for me.

We have a lot of common source files, which are general files used in
dozens of different projects (let's say - mybutton.h, mystring.h etc).
Under CVS, I was able to setup a "common" project which included these
files and had other projects link these in. Then when one is updated, all
the other projects will see these changes.
 From what I can understand, this is not how things work in the world of
subversion (where there are no real "links" between projects). Manually
merging a changed file across all projects that use it (and remembering
which ones use it in the first place) will bring me into grief.

This is such a common type of setup that I know most people will have had
to think about this and come up with workable solutions.
How do you do achieve what I describe above, being able to easily update
commonly shared code?

Cheers,
Chris

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Fri Jul 23 01:27:39 2004