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

Re: Storing externals for future generations?

From: John Waycott <javajohn_at_cox.net>
Date: 2006-08-03 15:25:56 CEST

Gabriel Cooper wrote:
> John Waycott wrote:
>> As a CM manger, I have to ensure that developers always build with
>> the correct software and tools. I'm uncomfortable with the idea of
>> using an out-of-date (the local copy) externalLib if the current copy
>> is unavailable.
> Well... At that point you're either not using any library (*ka-blam!*
> you can't build) or you're using the last-known-good. Which resource
> you use is up to your particular project. As said in the Vendor Branch
> example page at one point they wanted to keep up to the bleeding edge
> of an Apache library, and eventually they cut back to releases only.
I need to clarify my statement: I'm uncomfortable using an out-of-date
version when I'm supposed to use the current version. This is a case
where I know I have to get the latest version to continue my work, but
it is not available. However, I usually want to be able to control when
I get it; I don't want to pick up the latest version of a library if I'm
not ready to use it. If it breaks my build unexpectedly, I have to go
back and figure out what happened.

-- John

To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Thu Aug 3 15:29:01 2006

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

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.