info-cvs
[Top][All Lists]
Advanced

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

Re: CVS management of /etc - permissions problem


From: luke
Subject: Re: CVS management of /etc - permissions problem
Date: Fri, 14 Sep 2001 11:09:15 +1000 (EST)

On 13 Sep, Kaz Kylheku wrote:
>  In article <address@hidden>, Eric Siegerman wrote:
>  >On Thu, Sep 13, 2001 at 06:25:34AM +0000, 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
>  >> representation, and make sure that file is versioned under CVS.
>  >
>  >Or convince CVS to capture it for you.  That it doesn't do so
>  >now, and that writing a script is a useful workaround, are not
>  >valid arguments that CVS *should* not capture and version file
>  >metadata.  (There may in fact be valid arguments to that effect,
>  >but these aren't among them.)

[All of Kaz's excellent points deleted.]

Thanks, Kaz - you've completely convinced me that you're right, and
that storing the file metadata implicitly in the repository would be a
bad move.

Maybe cfengine would be the right tool (though it sounds like overkill
for my needs), or maybe something else will.  Probably something else,
since I'd still have the problem of recording the initial metadata that
cfengine would maintain, and recording fresh metadata as fresh files
get added.

Thanks, Eric, too, for making my arguments for me after Kaz's first
response, which lead to Kaz's 2nd even more convincing response.  :-)

I'll now go away and write or find a tool to record the metadata for
all the files concerned, and maintaining it as new ones are added.

Regards,

luke




reply via email to

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