This is way more than USD 0.02. Most CVS commands take directories and files as
arguments (ie "cvs update"). The only exception I know are "cvs checkout" and
"cvs export" since there can't be any directories assumed at that point.
Noel
[EMAIL PROTECTED] on 2000.04.03 02:53:14
To: [EMAIL PROTECTED]
cc: (bcc: Noel L Yap)
Subject: RE: "cvs release" wishlist
> -----Original Message-----
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
> Sent: 01 April 2000 01:03
> To: [EMAIL PROTECTED]
> Subject: "cvs release" wishlist
>
>
> Greetings!
>
> When our build tool recognizes that someone has removed a CVS
> module from a
> build area, I had planned to "cvs release -d $module" to
> remove it from the
> build area and then do a "make clean" everywhere to make sure
> I had a clean
> build area.
>
> I was bummed to find out that 'cvs release' doesn't take a
> module definition,
> but a DIRECTORY. I would think if I could checkout a module,
> I would be able
> to remove a module. Even better, a "-f" option to force the
> removal even if
> there are locally-modified files would make this whole thing
> much more
> automatable.
>
> Does this sound reasonable? Possible? Desirable?
It sounds reasonable, but...
What if I have checked out two versions of one module? Say:
$ cvs co -d my_prog_v10 -r Version_1_0 myprog
$ cvs co myprog
There is no link as to what module you want when just saying
release module myprog.
Just my 2 cents.
Guus
