Guus Leeuw writes:
>
> Hmm... the server goes ahead in server.c and calls ign_setup()
> from serve_questionable.
[...]
> So the strategy would be to remove this precious call to ign_setup() from
> within serve_questionable() and have the client ign_setup somehow
> detect, that the server might have something for him in the (!)
> $CVSROOT/CVSROOT/.cvsignore list only (!).
It's more complicated than that -- most of the individual cvs commands
also call ign_setup(), even when running in server mode.
I think the right thing to do, is to have all of the ignore processing
take place on the client side (asking the server for its
CVSROOT/cvsignore and including it at the appropriate place in the
processing) and have the client tell the server to ignore nothing. In
that case, the client would never send any Questionable requests to the
server and so serve_questionable() would never be called. (Of course,
you need to preserve backwards compatibility, so the client still has to
behave the old way if the server doesn't support the new request to get
CVSROOT/cvsignore, and the server still has to support the Questionable
request for old clients.)
> Hmm, are there a lot of people using real accounts on the CVS Server
> that can override the .cvsignore from the Client?
I sure hope not -- it's a bug, not a feature.
-Larry Jones
OK, there IS a middle ground, but it's for sissy weasels. -- Calvin
