Hello,
Just curious Geoff, why is it a bad idea to build as the superuser? Is it
something specific to the CVS build, or just generally a good policy?
Also, I've noticed something kind of odd with gnome-terminal... If I am in
one gnome-terminal and I define CVSROOT, and export it, when I open
Thomas Wharton [EMAIL PROTECTED] wrote:
Also, I've noticed something kind of odd with gnome-terminal... If I am in
one gnome-terminal and I define CVSROOT, and export it, when I open another
gnome-terminal (from the first), I dont see CVSROOT (using set). However,
if I open an xterm (from the
Hi Thom,
Just curious Geoff, why is it a bad idea to build as the superuser? Is it
something specific to the CVS build, or just generally a good policy?
It's nothing specific to the CVS build; it's just not a good idea to
build *anything* as the superuser. (A good general rule is to perform
Hi to all,
This may be odd question but I've got to throw it out,
where would I set the CVSROOT environment?
Classpath? Path?
Kent
___
Info-cvs mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/info-cvs
You add a new one named CVSROOT
Kent E. wrote:
Hi to all,
This may be odd question but I've got to throw it out,
where would I set the CVSROOT environment?
Classpath? Path?
Kent
___
Info-cvs mailing list
[EMAIL PROTECTED]
Hi Kent,
It's an environment variable, just like CLASSPATH and PATH are
environment variables.
In Unix, it'll be something like :
CVSROOT=:ext:[EMAIL PROTECTED]:/cvsroot
export CVSROOT
In Windows NT+, you can set it in the control panel.
At the DOS prompt in Windows, it'd be :
set
