[ On Monday, February 28, 2000 at 09:21:42 (-0500), Noel L Yap wrote: ]
> Subject: Re: removing the need for "cvs add file" to contact the server....
>
> I wasn't asking for a vote. I was asking for a poll to gauge how my opinion
> compares with that of the populous. I've always said that "cvs co", "cvs
> export", and "cvs up" should be the only commands treating empty hierarchies in
> any special way.
I'm telling you it's simply not a matter of "opinion". It's done deal
in the current implementation. Period. Changing this would not only
require a complete re-implementation but also some significant re-design
of the repository structure.
> Packages that have any (ie empty or not) directories they wish not to be "CVS
> managed" (by your definition) should not be within any CVS-managed directories.
> They should fix their build to reflect this.
Wrong. This is the job for the "ignore" facility. It works A-OK too.
> Since "cvs add empty-hier" is an optimisation, it is not *necessary*.
Who said that!?!?!? The optimisation is in not doing anything *after*
not finding any files to add. There's no "problem" with actually
running the command "cvs add empty-hier" -- it just won't cause any
changes in the current workspace. Please try to keep your logic
straight.
> It may
> even be dangerous 'cos you give the false impression that there is no way to get
> CVS admin subdirectories within local empty directory hierarchies.
Huh? What kind of hyperbole is that? If you want to add a file then
add a file! If you don't then be happy that CVS will be careful not to
do anything "extra" so that you won't end up wasting a potentially
massive amount of time and effort with every subsequent command you ever
run in that workspace.
> Once there exists CVS admin subdirectories, how will "cvs ci" treat them if they
> exist within empty directory hierarchies?
That's a pretty silly question. CVS with my "cvs add" implementation
won't treat them any differently than it will today.
I.e. if there are no *files* to commit in the directories then *nothing*
will be done!
> Will "cvs ci" further check if the
> hierarchies are empty before creating the directories within the repo?
No.
> Will
> "cvs ci" only create the repo directories once it detects a file?
Yes, that's what the proposal states.
> If so, "cvs
> ci" will also have to create CVS/fileattr within the repo for each of the
> directories it has created.
If necessary, yes. However that's a side issue that only affects a
secondary set of sub-commands. Normally there is no CVS/fileattr stuff
in the repository unless you've used one of the sub-commands that
specifically require it.
--
Greg A. Woods
+1 416 218-0098 VE3TCP <[EMAIL PROTECTED]> <robohack!woods>
Planix, Inc. <[EMAIL PROTECTED]>; Secrets of the Weird <[EMAIL PROTECTED]>
