[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: Bolstridge, Andrew <andy.bolstridge_at_intergraph.com>
Date: Fri, 20 Mar 2009 16:49:43 -0000

Not storing temporaries is an obvious 'best practice' for any SCM, but
there is often a requirement to store the built objects - eg the exes,
dlls or other binary targets.

If you do store binaries in SVN, then you can get them out easily
without re-building them. Often a implementation, project or QA person
will not have the skills or setup required to re-build, so needs to have
the binaries pre-built. If they're stored in SVN, then they can also get
the correct version without worrying that what they get to re-build will
be what was originally shipped.

We store all shippable binaries in SVN, and use svn:externals to help
ease fetching them from the repository.

Andy

------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=1065&dsMessageId=1365778

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