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

Re: post-commit export

From: Ryan Schmidt <subversion-2009b_at_ryandesign.com>
Date: Wed, 17 Jun 2009 02:09:23 -0500

On Jun 17, 2009, at 01:23, Justus Stadler_external wrote:

> the problem with the acces is that they do not have SVN, TSVN,
> Rapid....(or so on) installed. My job is to introduce, or rather
> test the
> functionality of SVN for the electronical engeneers division of an
> automitive supplier with about 3000 employes. I have to version the
> prototypes that leave for customers. All engeneers now have TSVN or
> (depending on their preferences) installed but the projectmanagers
> (these
> might sit in an different department/city) also need to have acces
> to the
> newest releases, or the momentarily status to discuss it with the
> customer. I cannot suggest that all those people have SVN installed or
> even move the workingarea somewhere else, it has to stay there.
> Sometimes
> even the engeneers do not know who their PM is....

Ok. And when you say "it has to stay there", "there" is the file
share we've been talking about, right? You've already been using this
system of having a read-only file share, and now you want to figure
out how to continue to have this once Subversion has been introduced,

I've had to do this kind of thing too. In our case, the projects were
websites. Every developer used some kind of svn client to manage one
or more working copies of the projects he was working on, which were
stored in the user's home directory on our development server, which
served them up via a web server. But we also had one central working
copy for each project which got auto-updated so that management had a
URL they could go to which always represented the latest state of a
project, without having to check out and keep updated a working copy
for themselves. But these central copies were still ordinary working
copies, updated with "svn up".

> Andrew sent(send?!? In other words: I have it already;-) ) me his
> script,
> which only needs a little rewriting, as he wrote. I'll give it a shot.

And the script tries to emulate "svn up" for an export as opposed to
a working copy, yes? If it works for you, great! But you're still
going to end up with about 450GB of space taken up with these
exports, right? I guess I'm unclear on why you can afford 450GB of
space for exports but not 900GB for working copies. :-P

P.S: And yes, "sent" is the past-tense of "send". :-)


To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subversion.tigris.org].
Received on 2009-06-17 09:11:00 CEST

This is an archived mail posted to the Subversion Users mailing list.