[ On Friday, February 25, 2000 at 20:28:11 (-0500), Noel L Yap wrote: ]
> Subject: Re: removing the need for "cvs add file" to contact the server....
>
> I want to take a poll with regards to the following issue:
> 
> "cvs add" must specially handle empty directory hierarchies such that no CVS
> admin subdirectories are created within them.  (I've tried to be as unbiased
> with this statement as I can).

This isn't an issue that users can simply decide and then "make it so".
The current CVS implementation takes this matter right to its core and
it cannot be kept consistent and logical without treating empty
directories as simply left-over garbage that must be removed.  This
should be self evident to even someone who is not intimate with the
implementation given they are aware of the constant barrage of replies
to FAQs that tell people to always use "cvs checkout -P" and "cvs update
-d -P" (preferably by putting those options in their ~/.cvsrc) and the
fact that CVS forces the '-P' option whenever the workspace is derived
from a branch.

In relation to this thread I will note again that my "cvs add" will not
do anything if no new files are found to add (i.e. it won't create any
CVS administrative files unless they are necessary to describe a
directory where a new file is being added, or any of the parent
directories of that directory).  I will also note again that this is
mostly just an optimisation (something that anyone using the NetBSD
"pkgsrc" or FreeBSD "ports" or similar collections under CVS will
appreciate immensely!).  Finally I will note, *again*, that this
implementation also helps to avoid giving the wrong impression to CVS
users about what directories are and what they do within the context of
CVS.

-- 
                                                        Greg A. Woods

+1 416 218-0098      VE3TCP      <[EMAIL PROTECTED]>      <robohack!woods>
Planix, Inc. <[EMAIL PROTECTED]>; Secrets of the Weird <[EMAIL PROTECTED]>

Reply via email to