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


From: Bolstridge, Andrew <andy.bolstridge_at_intergraph.com>
Date: Mon, 23 Mar 2009 09:45:17 -0000

> -----Original Message-----
> From: David Weintraub [mailto:qazwart_at_gmail.com]
> Sent: Friday, March 20, 2009 6:12 PM
> To: Bolstridge, Andrew
> Cc: users_at_subversion.tigris.org
> Subject: Re: SVN as CMS
> It might be easier for a QA organization to pull off the needed
> binaries off an actual "Release Repository" rather than using
> Subversion for this task. Non-programmers may find pulling what they
> need off of a release repository easier than doing a checkout in
> Subversion.

It probably would, but I'd rather keep source and binary (and
in the same repository, closely tied together. It's easy to right-click
a directory
And have all the changed files get checked in; it's not so easy to
checkout a
directory (esp. a sparse one) where all the project binaries are stored
elsewhere. It may be suitable for a build system, but I'd think many
groups don't have the time or need to implement such a thing - you said
you had to take the pain to set it up so it worked, from my experience
they all take quite a bit of time to get and keep going.

It's a good idea for a solution though, but there are better ways to fix
the problem than working around it like this.....

> Another problem is that Subversion does not provides an easy way to
> delete older obsolete binaries, so the size of the repository can
> build up rather quickly.

I think the best resolution to everyone's needs is to get this feature
implemented, especially if its combined with the svn obliterate feature.
(in fact, the obliterate feature would allow this - obliterate your
binary, then check the new one in - job done, even if it requires a
manual step).

Even Sourcesafe can store just the latest version instead of making
deltas for obsolete binaries :)

This problem isn't just for built binaries though, what do you do with
images and other binary sources? You may have less of them than build
objects, but they'll still show the same problem.
Sure you probably still want these to be version controlled and every
version stored in the repo
but I can see a need to drop older versions over time (eg delete all
entries over a year old).


To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subversion.tigris.org].
Received on 2009-03-23 13:25:03 CET

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.