[ On Monday, April 3, 2000 at 15:43:43 (CST), Win32 M$ wrote: ]
> Subject: Base directory, in CVS directory
>
> That is a great feature, but the problem is that it is the copy with the
> exact same name as an original. Then, if I try to grep for the files
> recursively in some directory, I will get the files in the "Base" as well.
> More - that files seems to have read-only cleared, so in the end quite often
> I will edit it instead of the real file... Very annoying... :(
That's only a problem with your search tools. If I'm not too far out of
touch I seem to recall that the "Base" directory is within the CVS
administrative sub-directory. So, you need to purposefully ignore the
stuff in the CVS administrative directories.
Yes I know this is a bit of a pain and lead to all sorts of simlilar
ugliness spread all throughout scripts and tools that build and manage
sources, but it's an old and common problem and there are many old and
common solutions to it already widely deployed. For example to generate
a list of just the non-administrative files:
find . -name CVS -prune -o -type f -print
If you make this into a shell alias/function/script then you can just
pipe its output to 'xargs' to run any command over all the files:
just-the-files | xargs grep "string-to-grep-for"
Note that a more generic solution for people who work in a wide variety
of environments is:
find . -name CVS -prune -o -name RCS -prune -o -name SCCS -prune -o -type f -print
I'm a touch typist and since I use a wide enough variety of systems the
management of such an alias/function/script would be harder for me than
just typing the appropriate 'find' command every time. It also helps
keep my mind sharp to have to figure out the logic of the 'find'
parameters each time! :-)
--
Greg A. Woods
+1 416 218-0098 VE3TCP <[EMAIL PROTECTED]> <robohack!woods>
Planix, Inc. <[EMAIL PROTECTED]>; Secrets of the Weird <[EMAIL PROTECTED]>
