>
> > ~user/.cvsignore is global, however, applying to
> > all CVS work a user does.
> >
> > In your home directory, these different meanings clash.
>
> Yet another good reason why you should always *always* use a "build"
> procedure to install files into their proper place from any arbitrary
> working directory....
Somehow I knew you would say that, Greg :-)
---
Actually, I will happily use a build procedure,
if it is reversible.
E.g. once I have checked out the file called
dir/foo in the repository
and had it renamed via the build procedure to dir/bar,
then, if I edit dir/bar,
I want to have a command that will take the changes
I make to dir/bar and apply them the file named dir/foo
in the repository.
Basically, I am often too lazy,
and find the process too error-prone
of editting dir/bar in my workview,
tracking down that it maps to dir/foo in the repository,
and then arranging to check it in there.
Similarly wrt symlinks, etc. --- any build process
that is one to one, and even many that just extract info
from a multiversion form.
Of course, if I had such a tool
I would use it instead of CVS.
