In article [EMAIL PROTECTED],
[EMAIL PROTECTED] wrote:
To this end I've written a script which checks in as much or as little
of /etc's text files as you want. And now I've found that CVS is
getting in the way, by wiping the group and file and directory
permissions of the files being added. (It
]]
Gesendet: Donnerstag, 13. September 2001 07:16
An: [EMAIL PROTECTED]
Betreff: CVS management of /etc - permissions problem
I've recently tackled a problem I've wanted to solve with CVS for a long
time now - namely, managing the configuration of a Unix machine
(especially desktop Linux machines
On Thu, Sep 13, 2001 at 03:15:39PM +1000, [EMAIL PROTECTED] wrote:
To this end I've written a script which checks in as much or as little
of /etc's text files as you want. And now I've found that CVS is
You might consider looking at cfengine, or something similar. You could
then use cvs to
On Thu, Sep 13, 2001 at 06:25:34AM +, Kaz Kylheku wrote:
So you see, it's a fundamental misconception that the conventional
metadata on the CVS version files is actually part of the versioned
content.
True enough.
If you want
something to be versioned, you have to capture it in a file
--- [EMAIL PROTECTED] wrote:
I've recently tackled a problem I've wanted to solve with CVS for a long
time now - namely, managing the configuration of a Unix machine
(especially desktop Linux machines), via CVS.
I do this to a certain extent as well.
...
To this end I've written a script
In article [EMAIL PROTECTED], Eric Siegerman wrote:
On Thu, Sep 13, 2001 at 06:25:34AM +, Kaz Kylheku wrote:
So you see, it's a fundamental misconception that the conventional
metadata on the CVS version files is actually part of the versioned
content.
True enough.
If you want
On 13 Sep, Kaz Kylheku wrote:
In article [EMAIL PROTECTED], Eric Siegerman wrote:
On Thu, Sep 13, 2001 at 06:25:34AM +, Kaz Kylheku wrote:
So you see, it's a fundamental misconception that the conventional
metadata on the CVS version files is actually part of the versioned
I've recently tackled a problem I've wanted to solve with CVS for a long
time now - namely, managing the configuration of a Unix machine
(especially desktop Linux machines), via CVS.
The rationale is that if I change a system config file, and months
later discover that something has stopped
