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

Re: Externals - VSS

From: Andy Peters <devel_at_latke.net>
Date: 2006-11-17 21:25:08 CET

On Nov 17, 2006, at 4:25 AM, Steve O'Hara wrote:

> In my quest to convert from VSS to svn I've tinkered with the notion
> that all shared files have to exist in separate directories which are
> then referred to by the externals mechanism.
> However, am I right in thinking that if I make a change to a file that
> is from an external project, when I commit the changes, the changed
> external file will not be submitted to svn automatically?

i've found it safer and easier to never use an external that's not a
tag. Everything that's usable as an external is its own project and
maintained as such.

One reason for this that may not be obvious is if you tag a release
of your project, only your project's code is tagged. Say I have an
FPGA design (I'm a hardware guy) that uses a UART module. I include
the UART trunk as an external in my project, and I build my chip and
I'm happy. I tag the project. A couple of months later, a problem
pops up so I check out the tag to see what was used to build the
chip. Unfortunately, someone else has modified the UART module
(maybe added or removed a port or whatever). Since my project uses
the UART module trunk instead of a tag, now my FPGA won't build.

So for this reason I always use tagged versions of external modules.

-a

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Fri Nov 17 21:25:53 2006

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