Hey! On 30/Jul/2010, at 7:34 AM, Farrukh Ijaz wrote: > On 30-Jul-2010, at 3:57 PM, Valerio Luccio <valerio.luc...@nyu.edu> wrote: >> Farrukh Ijaz wrote: >>> At first place I would avoid svning the tar as it is a binary file and even >>> a minor change will change the binary and I guess every time the commit >>> will recognize it as new file will commit the whole tar instead of >>> differences, as a result it will start eating repository disk space very >>> fast. I see plan C would be the best choice iff you can switch to hudson. >>> Otherwise instead storing the tar, tag the successful revision. >>> Farrukh >> True, but I don't create tarballs that often and it's only 1.1 MB, storage >> space is not an issue. I guess they could check out the code from dist just >> as well, I'm not sure why I went down the tarball route ... > Then go for plan B. Have a separate folder under your project and either > generate the tar in it or move from dist to it.
Um, SVN stores differences in binary files and not the whole file each time! Thank the gods that we're no longer following the RCS/CVS plan! ;-) See: http://svnbook.red-bean.com/nightly/en/svn.forcvs.binary-and-trans.html Wrt how to achieve your original goal, I would go with Chuck's solution and copy each new tar ball to a new folder! ;-) Good Luck! M. _______________________________________________ Do not post admin requests to the list. They will be ignored. Webobjects-dev mailing list (Webobjects-dev@lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
