RE: How well does CVS handle other types of data?

[Peter Fox]

Sorry, but to name binary icon files to identify the releases that they
should be present in. This seems a truly weird solution. Surely I shouldn't
have to rename my files to include them in a release.

Pete


> -----Original Message-----
> From: address@hidden [mailto:address@hidden
> Sent: Thursday, July 12, 2001 1:11 AM
> To: Lan Barnes
> Cc: CVS-II Discussion Mailing List
> Subject: Re: How well does CVS handle other types of data?
> 
> 
> [ On Wednesday, July 11, 2001 at 11:18:01 (-0700), Lan Barnes wrote: ]
> > Subject: Re: How well does CVS handle other types of data?
> >
> > Hmm. If I exclude the binaries in my projects from CVS, how 
> can I apply
> > tags to them so that I know which revisions of each binary 
> are meant to go
> > with which releases?
> 
> Man oh man oh man!  If there ever was an FAQ about CVS this 
> must be it!
> Does this have to be spelled out in some concrete script form 
> every two
> weeks, or what?
> 
> The answer is to use naming conventions on your binary files 
> (and/or the
> directories they are archived in) such that their relationship to your
> release management process can be determined by their name 
> alone.  From
> there your build process can easily be constructes to always pull the
> appropriate revision of a binary file into any given release build.
> Since the scripts/makefiles/whatever that control your build 
> process are
> ultimately source code you can effectively tag which binary revisions
> belong in which releases by simply tagging the build 
> makefile!  How much
> simpler could it ever be?
> 
> -- 
>                                                       Greg A. Woods
> 
> +1 416 218-0098      VE3TCP      <address@hidden>     
> <address@hidden>
> Planix, Inc. <address@hidden>;   Secrets of the Weird 
> <address@hidden>
> 
> _______________________________________________
> Info-cvs mailing list
> address@hidden
> http://mail.gnu.org/mailman/listinfo/info-cvs
> 


--

NOTICE:  The information contained in this electronic mail transmission is
intended by Convergys Corporation for the use of the named individual or
entity to which it is directed and may contain information that is
privileged or otherwise confidential.  If you have received this electronic
mail transmission in error, please delete it from your system without
copying or forwarding it, and notify the sender of the error by reply email
or by telephone (collect), so that the sender's address records can be
corrected.