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

Re: combining svn:externals and branching

From: Tom Mornini <tmornini_at_infomania.com>
Date: 2004-04-03 23:10:37 CEST

On Apr 3, 2004, at 11:00 AM, Robert P. J. Day wrote:

> this repository would include pure
> source, and nothing else -- no build scripts or makefiles, at least i
> don't think so yet. the repository's job is to handle strictly source.

I think this is a bad idea. The source tree should include build and
make
scripts, certainly! What good is source code without a means of building
it? And, the build and make scripts will change with the source, so if
you
want history capability for the project, these files MUST be included in
source control.

> repository. although i haven't nailed down how to do this yet, i'm
> assuming it's not going to be hard for a project to define new
> branches in
> either of two places -- strictly within the current project, or back in
> the main software repository. is that doable?

I worked this through recently myself. Upon a label or branch, the
svn:external
definition will need to be updated to point to a label or branch of the
external
repository.

-- 
-- Tom Mornini
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Sat Apr 3 23:11:18 2004

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.