bug-cvs
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: different CVS_SERVER for different hosts


From: Mihai Bazon
Subject: Re: different CVS_SERVER for different hosts
Date: 30 Oct 2003 11:48:29 +0200

Yeah, the idea of using a CVS/environment file would be much better..

About my patch, a friend of mine pointed out that if I happen to run cvs
in a directory where someone dropped "by mistake" a .cvsserver with the
content "rm -rf *" bad things will happen, and he's right.  ;-)

Fortunately this won't be the case for me as I run this patched CVS on
my personal, client machine only.  But for public usage it could create
some problems..

A solution would be to list allowed server commands in some
configuration file in $HOME.

By the way, I am a long-term user of CVS and because it always worked as
I wanted I never messed too much with configuration.  So I have a
question, what exactly _is_ the ~/.cvsrc file?  Is it useful for more
than to pass default command line args?  If that's the case I'd say it's
pretty limited (but yet on the other hand, the fact with CVS_SERVER was
the only thing so far that I felt like it should be more configurable..)

Cheers,
-Mihai

On Wed, 2003-10-29 at 17:11, Derek Robert Price wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> 
> Mihai Bazon wrote:
> 
> |>I am not sure that is the best design path to follow.
> |
> |
> |Indeed, it's not.  My implementation is a dirty hack that only allows
> |per-directory alternate for CVS_SERVER.  But we could have a .cvsconfig
> |file that had more options that override ~/.cvsrc.  Flexibility is
> |good.  Look at ssh, for instance--you can set some defaults, but you can
> |also set different parameters for each host, in ~/.ssh/config.  I'm sure
> |that some guy at some point thought that it wouldn't be useful, but I
> |actually find it is ;-)
> 
> 
> Maybe something as simple as a CVS/environment file (like CVS/Root &
> CVS/Repository) for storing environment variable settings used to access
> the server for each workspace would be simple enough?
> 
> Something parallel to the host settings in ~/.ssh/config doesn't really
> seem necessary to me if workspaces can remember their settings.  They
> only need to be reinput on fresh checkouts.
> 
> Then again, if someone submitted a clean, efficient patch for something
> like ~/.ssh/config for CVS including docs and test cases, how could I
> pass it up?
> 
> Finally, the way the rest of the CVS commands work is to allow the file
> settings to override the environment, not visa versa.  Then the command
> line can override the file settings.
> 
> Derek
> - --
> ~                *8^)
> 
> Email: address@hidden
> 
> Get CVS support at <http://ximbiot.com>!
> - --
> OPHELIA  Could beauty, my lord, have better commerce
> ~  than with honesty?
> HAMLET  Ay, truly.  For the power of beauty will sooner
> ~  transform honesty from what it is to a bawd than the
> ~  force of honesty can translate beauty into his likeness.
> ~  This was sometime a paradox, but now the time gives it
> ~  proof.  I did love you once.
> OPHELIA  Indeed, my lord, you made me believe so.
> 
> ~     - Hamlet, Act III, Scene 1, Lines 109-116
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.0.7 (GNU/Linux)
> Comment: Using GnuPG with Netscape - http://enigmail.mozdev.org
> 
> iD8DBQE/n9iVLD1OTBfyMaQRAgseAJ0ZoqfTtazDM8YetQRmPHt3MLLi2ACgknRx
> cdcw6j0wgCTbUdgF9Rq7rJA=
> =4zVc
> -----END PGP SIGNATURE-----
> 
> 
> 
> 
> _______________________________________________
> Bug-cvs mailing list
> address@hidden
> http://mail.gnu.org/mailman/listinfo/bug-cvs
-- 
Mihai Bazon,
http://dynarch.com/mishoo/   [ applied W3 ]





reply via email to

[Prev in Thread] Current Thread [Next in Thread]