[ale] CVS and binary releases

[John Mills]

ALErs -

I would like to use CVS in a particular manner, primarily with regard to
binary files: I would like each revision's files to be directed into a
separate subdirectory, the name of which reflects the revision level.
Each subdirectory might contain multiple binary and support files, as well
as CVS overhead files. This is the way our 'mks' _SourceIntegrity_ archive
works, and it matches our release environment well.

I just set up a CVS repository, and it appears the 'cvswrappers' settings
of "-k'b' -m'COPY'" are not doing quite what I want: I can unpack the
binary file OK, but my first impression is that newer revs were being
adjoined to the older ones, rather than replacing them.

I would like to come out roughtly as follows:
$CVSROOT/Installations/apps1/1.1/<binary_image_1_1_A>
                            /1.1/<binary_image_1_1_B>
                            /1.1/CVS/<CVS overhead files>
                            /1.2/ [... etc ... ]
                            /1.3/
                            /1.3.1.1/
                            /1.3.1.2/

What I want to avoid is CVS storing multiple revision levels under the
same image filename in the archive.

I expect I will need to write and invoke some scripts to achive this, and
I would appreciate any pointers from folks who may have tried something
like this.

Thanks.
 - John Mills


---
This message has been sent through the ALE general discussion list.
See http://www.ale.org/mailing-lists.shtml for more info. Problems should be 
sent to listmaster at ale dot org.