Peter Gerwinski wrote:
Matthias Klose wrote:
Having CVS read access is nice, but currently, there seems to be something wrong with the configuration. Doing a daily update, you get every day all files; do they get touched when making the daily snapshot releases?
They are committed with `cvs -fR' in order to store the correct permissions in the CVS repository. Unfortunately this seems to have the effect you describe.
Anyone knows a better solution how to preserve permissions in CVS?
I think that's a misunderstanding on your part. I suggested using `-f' (force) to *re*-upload a few files which had been uploaded with wrnog permissions (reported by Russ Whitacker a few weeks ago, now fixed). AFAIK, `-f' has nothing to do with permissions per se. Rather, (cvs)Special Files says:
: If the configuration variable `PreservePermissions' (*note config::) : is set in the repository, CVS will save the following file : characteristics in the repository: [...]
Frank