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

Re: Using svn:externals

From: Hari Kodungallur <hkodungallur_at_gmail.com>
Date: 2007-09-10 19:49:41 CEST

On 9/10/07, Rob Wilkerson <r.d.wilkerson@gmail.com> wrote:
> I've spent a lot of time looking and there's a lot of material out
> there, but either it doesn't cover my situation or I'm not informed
> enough to recognize the correlation. That's my attempt at an apology
> if my question has an obvious answer. :-)
> I have a set of code that needs to be shared across existing projects
> and also with future projects whose project directories haven't yet
> been created (I have one repository with many top level project
> directories). Essentially, every new project directory needs to
> include these same external directories. Is there any way to automate
> this? Once the project is identified, I create the project directory
> by importing a directory "template" that includes the /branches, /tags
> and /trunk directory.
> Is it possible to somehow attach the external directories to the trunk
> without another step to my process?

I do not know of any method that automates the setting of svn:externals for
newly created projects. It would have been nice if we could use auto-props
to set svn-externals [May be we can do it, but I have never tried it.. I
always thought you need an SVN_EDITOR to set the externals].

Rather than "import"ing the directory template, is it possible to keep the
template in the repository itself?

Something like:

  - template
     - trunk
     - branches
     - tags

Then set the externals on the trunk. And when you have a new project,
instead of importing, you can just copy the template directory to the new
project directory. That way, the externals get copied as well.

-Hari Kodungallur
Received on Mon Sep 10 19:46:34 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.