Hi all, I have a need to allow certain projects using cvs to have access to (and modify in their own branches) previously defined modules 'as at' a certain point in time. Having had bad experiences with projects using specific tags or branches of modules and inadvertantly corrupting them (or simply using the wrong ones), what I want to do is set up pseudo-modules that point to modules with a specific revision tag, so that by checking out a project alias module all of the components from the correct point in time are obtained, without the user having to specify the component modules and version tags separately. For instance, if we had a project TheBigProject which was aliased in the modules files as consisting of LittleComponent1, LittleComponent2, LittleComponent3, what I want to be able to do is specifiy through the alias module which versions of the component projects should make up TheBigProject, so that if I had another project TheOtherBigProject that used the same components but at a later revision I could do this. Any ideas? Mark Cooper --LongSig - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Any views or opinions presented in this Email message are solely those of the author and do not necessarily represent those of the Microlise Group unless otherwise specifically stated. Email communications are not necessarily secure and therefore the Microlise Group does not accept legal responsibility for the contents of this message. If you are not the intended recipient and have received this message in error, please notify Microlise immediately. Microlise Group Limited +44 (0)1773 713311 _______________________________________________ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
