On Nov 12, 2006, at 23:40, Mark wrote:
> On 11/12/06, Mark Clements wrote:
>> "Gal Aviel" wrote:
>> > forgot one small but important fact : I want the property
>> information on
>> > files/dirs ... (ignores, etc - takes allot of time to re-
>> implement this
>> > on the new repos) otherwise (for pure tree structure and file
>> > I would follow your suggestion ..
>> I've been wondering about this too. I want to setup a 'default'
>> with a full directory structure, various properties set, and
>> possibly some
>> standard files/externals. This repository will obviously be
>> modified from
>> time to time as our working processes change.
>> I would like to be able to make my repo creation script install
>> the current
>> 'default repository' as revision 1 of any new repository it
>> creates. Can
>> anyone think of a way to do this?
> I haven't tried this out, but can't you just do an export of the
> golden, setit aside. Then have your repos creation script create a
> repository, do a checkout, copy the golden into the working copy, svn
> add everything, do all the prop setting you want, svn commit.
> Am I missing something?
Yes -- the properties.
The only way I can think of to do that would be:
$ svnadmin create newrepo
$ svn co $NEWREPO wc
$ svn export $OLDREPO wc
$ cd wc
$ svn add .
Then run "svn proplist -R -v $OLDREPO", and then create a script to
parse that output and set those properties again on the items in the
in-progress working copy. Then you can commit everything as the first
revision. Then you can "svnadmin dump" the new repo to create a
dumpfile that anyone can use to "svnadmin load" into a new repository.
Note that you should be distributing a dumpfile of this template
repository, and not copies of the repository itself, as the
repository contains a unique ID, which no two repositories should
share. True, that ID gets written to the dumpfile too, but it can
(and should be) ignored when loading: "svnadmin load --ignore-uuid".
I'm not sure though how you would go about enforcing that the --
ignore-uuid option always be used.
To unsubscribe, e-mail: email@example.com
For additional commands, e-mail: firstname.lastname@example.org
Received on Mon Nov 13 07:06:16 2006