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

Re: Projects with component dependencies

From: Ryan Schmidt <subversion-2007a_at_ryandesign.com>
Date: 2007-03-13 10:44:46 CET

On Mar 12, 2007, at 14:18, Luke Powell wrote:

> Brad, thanks for the pointer, externals look to be the concept that
> I need
> to pursue. How are releases and tags usually handled with the
> externals
> system? If we release software, we want to be able to rebuild from the
> same source, but it seems that there's no great way to "pin down" the
> external revision without modifying the property manually. Is that
> what is
> usually done?
>
> e.g.
>
> Project A has Project Z as an external. When copying Project A's
> trunk to
> a tags folder, would I normally manually copy Project Z underneath
> it in
> the repository and remove the svn:externals property from Project A?
> Alternately I could leave the externals definition and explicitly
> specify
> a revision number in the property. Is one of these the way these
> tags are
> customarily handled?

The latter is usually done, and if you use the svncopy.pl script to
make the tag, rather than using "svn copy" yourself, it will handle
that for you.

-- 
To reply to the mailing list, please use your mailer's Reply To All  
function
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Tue Mar 13 10:45:26 2007

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.