new user - do people store compiled code under cvs
? That is, would you save versions of things like executables, p-code, or DLLs? My gut says no, better to pull the source code for the version/revision we want to run/test/distrubute and compile from that whenever we need it. But what do people generally do? Thanks, Rachel ___ Info-cvs mailing list [EMAIL PROTECTED] http://lists.gnu.org/mailman/listinfo/info-cvs
Re: new user - do people store compiled code under cvs
At 04:39 PM 11/29/2004, Rachel Suddeth \(Bloodhound Software\) wrote: would you save versions of things like executables, p-code, or DLLs No. Not in CVS. It's a good idea to save a copy of whatever you release to your clients so you can recreate your client's environment. However, CVS is not really good at storing binary information. I just make tar or zip files of whatever I release, name the file appropriately, and put it in a well-known place. There are far, far fewer of these than versions of source files in CVS. Fred ___ Frederic W. Brehm, Sarnoff Corporation, http://www.sarnoff.com/ ___ Info-cvs mailing list [EMAIL PROTECTED] http://lists.gnu.org/mailman/listinfo/info-cvs
RE: new user - do people store compiled code under cvs
Rachel Suddeth (Bloodhound Software) wrote: ? That is, would you save versions of things like executables, p-code, or DLLs? My gut says no, better to pull the source code for the version/revision we want to run/test/distrubute and compile from that whenever we need it. But what do people generally do? Your instincts are correct. Use CVS to manage files that cannot be recreated by an automated process. For example, your source files (C, C++, etc.), makefiles, and so on. CVS works best with mergeable text files, but it can also handle binary files such as images (.bmp, .gif, etc.) that are not generated by some build process. -- Jim Hyslop Senior Software Designer Leitch Technology International Inc. ( http://www.leitch.com ) Columnist, C/C++ Users Journal ( http://www.cuj.com/experts ) ___ Info-cvs mailing list [EMAIL PROTECTED] http://lists.gnu.org/mailman/listinfo/info-cvs
Re: new user - do people store compiled code under cvs
People do, but in most cases it's not considered best practice. If you can reproduce the binaries from source, then don't put them under CVS; tag the sources and store the environment in a reproducible way. If the binaries are not reproducible from source, then there are two schools of thought. The first is to install the binaries in some well-known place and treat them like any other aspect of the build environment. The second is to apply the rigor to the binaries like any other file that can't be reproduced without manual intervention (i.e. source files) and check them in and write a build/deployment process to match. Heated debate supports both practices. On Nov 29, 2004, at 1:39 PM, [EMAIL PROTECTED] wrote: ? That is, would you save versions of things like executables, p-code, or DLLs? My gut says no, better to pull the source code for the version/revision we want to run/test/distrubute and compile from that whenever we need it. But what do people generally do? ___ Info-cvs mailing list [EMAIL PROTECTED] http://lists.gnu.org/mailman/listinfo/info-cvs
Re: new user - do people store compiled code under cvs
Hello, * On Mon, Nov 29, 2004 at 04:53:51PM -0500 Jim.Hyslop wrote: Your instincts are correct. Use CVS to manage files that cannot be recreated by an automated process. Well, yes and no. The problem with recreating some files is, that this recreation might not work at any future point of time (you've get a new compiler, and the old one is not available anymore), or you need exactly what you compiled some time before (for example, for crash dump analyses, having the exact same binary helps much). On the other hand, of course, you are right. CVS is not good in managing binaries. So, I would store them off-line, as Frederic suggested in the other mail. Either make a tarball (.tar.gz or .tgz) if you are on a unix system, or generate a zip if you're running on Windows. On other OS, use something similar. Regards, Spiro. -- Spiro R. Trikaliotis http://www.trikaliotis.net/ http://www.viceteam.org/ ___ Info-cvs mailing list [EMAIL PROTECTED] http://lists.gnu.org/mailman/listinfo/info-cvs
