Re: what's to stop a developer from nuking the repository?

2004-02-29 Thread xyzzy
On Tuesday 20 January 2004 11:46 am, Andrew Marlow wrote: Rhodes, Phillip C. [EMAIL PROTECTED] writes: I am nervous that all my cvs archives are owned by a group that all of our developers are a member of. That is, any developer with a unix account (all of them) can nuke the archives.

Re: what's to stop a developer from nuking the repository?

2004-02-29 Thread Mark D. Baushke
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 [EMAIL PROTECTED] writes: The problem is that the cvs directory is on the same machine as all the other server stuff including user's server home directories. What you describe is a non-optimal setup. Do try to use a dedicated machine which does

Building inside local repo?

2004-02-29 Thread Joel Konkle-Parker
I'm somewhat new to CVS, and I have sort of a best-practices question. I just checked out the Wine sources into ~/wine. To build them, I `cd` into ~/wine and do a `./configure make make install`. Is this for some reason a really bad idea? Is it harmless to build the source inside my local

Re: Building inside local repo?

2004-02-29 Thread Paul Gelderblom \(ptok\)
Build them right where they are now. The sources you have now got locally, are _not_ the repository. They are your private copy -often called a sandbox by CVS users. Like a real sandbox, they are your spot for doing anything you like. You can change them, without any risk for the real Wine