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

Re: Re: Re: Recursive externals problem

From: Hilco Wijbenga <hilco.wijbenga_at_gmail.com>
Date: Sat, 13 Dec 2008 12:36:36 -0800

2008/12/12 Koh Hwee Miin <hweemiin_at_hotmail.com>:
> By the way, can you evaluate more about "think twice before I'd commit build results into Subversion"? I'm still a newbie when managing projects on svn, hope you won't mind sharing your experience on svn.

If you commit your build results you'll never be sure how those build
results were generated. Imagine being in a hurry so you quickly fix
some bug (locally) and commit only the build results. Now the source
and binaries no longer match. It can happen without any bad intent,
simply the result of a mistake or omission.

The build should be reproducible and should be the only way to create
the binaries. After that, an official release process can make those
binaries available to everybody else. Any changes should happen in
code first, followed by a release (with a new unique version number).

> Also, do you know any good articles/books on managing c++ projects on svn?

No, but I encourage you to have a look at Maven
(http://maven.apache.org/). This is mostly for Java projects so it
will not help you directly but the ideas behind it are universally
applicable. Note, especially, the notion of a central repository for
binaries (so you don't have to rebuild all your dependencies every


To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subversion.tigris.org].
Received on 2008-12-13 21:37:43 CET

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