Hello Pieter!
>>> Is there an elegant solution to my problem, apart from ignoring
>>> "/etc/fsvs", which is a solution I don't really like?
>
>> Not yet. And if you ignored the whole directory, you wouldn't have the ignore
>> patterns versioned anymore.
>
> Ok, I agree that ignore patterns should go in /etc. But...
...
> But why should the state of the 'current revision' go in /etc as well?
>
> Referring to the the FHS[*] this may not be the best (or at least an
> unusual) location for it. FHS mentions that files in /etc should be
> 'configuration files' and also be 'static'. At the same time it suggests
> /var for "spool directories and files, administrative and logging data,
> and transient and temporary files".
>
> I was wondering whether we could realise this split for fsvs too. If so,
> my first hunch would be that this will solve the discussed problem as a
> bonus since, indeed, /etc will only contain static files.
FSVS already uses /var/spool/fsvs for spool files - eg and the *list* of
entries (that
is mostly a cache of the repository data at revision N) is already there.
> But why should the state of the 'current revision' go in /etc as well?
Because in /etc it will be versioned - and that's good, because to restore a
machine to
*exactly* the state it was in you'll need the information which URL*s* you had
at which
revision.
I grant you that for a single URL (which will mostly be at HEAD) it's not such
an
important point - but if you use some 50 URLs at varying revisions, you'll be
grateful
if you can later see what you had 3 weeks ago, "when it still worked" ...
But I won't forgot your suggestion; it's duly noted :-)
Regards,
Phil
--
Versioning your /etc, /home or even your whole installation?
Try fsvs (fsvs.tigris.org)!
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
