[EMAIL PROTECTED] wrote:
>
> Lastly, if anyone has any ideas about the best way to implement
this
>feature, I'd like to hear them. My thought was to add another
command
>line switch, -S, for "store without revision". I guess that this
switch
>would just go into the CVS/Entries file in the same spot that -kb
goes,
>and on a commit the client would just transmit the file directly and
the
>server would store it, possibly even without the ",v" extension
(although
>I'm not sure what the role of this extension is, yet). On checkouts
or
>updates, the server would just take the file directly, rather than
doing
>any version processing.
>
CVS was originally a set of wrappers around RCS. Eventually CVS
became a standalone product but it still uses RCS-compatible files.
RCS puts ,v at the end of the files to differentiate the version
controlled files from the working files.
If you plan on putting stored files in the repository, I recommend
that you don't put ,v after it. Otherwise, CVS will assume it is
version controlled and will cough up a hair ball when it finds it
isn't.
Currently, CVS won't find any files that don't have a ,v option. I
use this feature to temporarily back up certain moddule (e.g. when
doing a third party import). Therefore, if you are committed to this,
I recommend adding another extension -- perhaps ,s for "stored".
However, if you are not maintaining any history, I don't see any
reason to store it in the repository. Just have a centralized
directory structure where developers can place these files. We
develop on Unix and have an NFS directory, /tgi/ops/deps, for storing
these kind of files.
--
Stephen Rasku E-mail: [EMAIL PROTECTED]
Senior Software Engineer Phone: (604) 872-6676
TGI Technologies Web: http://www.tgivan.com/
