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

Re: SVN as CMS

From: Les Mikesell <lesmikesell_at_gmail.com>
Date: Fri, 20 Mar 2009 13:40:57 -0500

Bob Archer wrote:
>> 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.
> Why can't a subversion repository be this "release repository". I see no
> problem using the tool this way. Other wise you have to create your own
> release folder structure, version it yourself, etc. Or, just always put
> the latest version only out there. Isn't this basically what svn gives
> you without all the work?

One problem is that it is next to impossible to really delete anything
from a subversion repository, so if you regularly push binaries in
you'll end up with a big repository of mostly-obsolete data, but still
important to keep backed up. And if you set things up to use its native
  'update' mechanism you end up with 2 copies and some extra metadata
everywhere you use it.

   Les Mikesell
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subversion.tigris.org].
Received on 2009-03-20 19:41:52 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.