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

Hook script issue

From: Romain Prévost <prevost.romain_at_gmail.com>
Date: 2005-08-03 16:15:15 CEST

Hi,

For a migration test to subversion, I have to emulate shared
components, from the old SCM. That is, when a file is updated
somewhere, it's also updated on the others registered locations.

I thought about it a lot, and end up with this kind of idea (not yet
implemented) :
- add to a file I want shared some properties like :
   gl:shared /proj1/myshared.file /proj2/myshared.file /proj3/myshared.file

- use a pre-commit script, whose role would be to check if there's no
problem with the property, and therefore allow or not the commit
- use a post-commit script, whose role would be to copy the updated
file to all the listed locations.

Now the best part, issues :) :

- Is there a clean way to replace the old files ? I can't merge
without a working copy, and the only other option seems to be a
delete-and-copy, which makes 2 revisions.

- I can't find a way to regroup all those operations in one. From
there comes the BIG issue : Since all our projects will be in the same
repos (to allow those shared files), every projects has something like
10 to 20 of them mirrored on 10 to 60 locations, we have 300
developers, each doing 2-5 commit a day, 20 times a month, we end up
with 1,200,000 to 36,000,000 revisions a month !!! Of course, this is
'slightly' overestimated, but still impressive, even for a good
filesystem.

Any thought welcome :)

PS : I'm pretty sure anyone reading this will smile at the 36 000 000 :)

-- 
Romain Prévost
Epitech promotion 2007
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Wed Aug 3 16:18:33 2005

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.