On Saturday 20 December 2008 Peter Rabbitson wrote:
> Yes and no. The filter option is general - there is no granularity. Back
> to my use case - I am versioning /etc/fsvs/<hash>/Ign - which implies
> that I version both /etc/fsvs/<hash> and /etc/fsvs, whose timestamps
> change on every commit/update. Those I do not want to status/commit.
> However I would like to see mtime changes on... I don't know /sbin for
> instance, as if this happens between apt-get's, this means someone is up
> to no good.
Yes, that's right.
> From what I can gather it is not possible to set filter on
> per-path basis, so I guess this can go as a low-priority wishlist. Thank
> you for clarifying though.
Ok; please remind me ;-)
> > If you use multi-URL, then you'd have to specify the "commit_to" option,
> > to tell FSVS which repository should get sent these changes ... but that
> > could get messy.
>
> Hm... how is it different if I use two WAA's via wrapper scripts as you
> suggest versus using two urls with wrapper scripts filling in
> -commit_to? I understand it can be done both ways, I am just trying to
> gain some wisdom on why one way is messier than the other
Using "multi-URL" means a shared WC, where a single entry is at a *single* [1]
URL; changing FSVS_WAA and FSVS_CONF does this like two completely unrelated
WCs, where each entry is in *both* repositories.
[1]: But there are some priorities involved, which get used if an entry is in
more than a single URL.
> Thank you for taking the time to explain this stuff, much appreciated.
You're welcome!
Regards,
Phil
--
Versioning your /etc, /home or even your whole installation?
Try fsvs (fsvs.tigris.org)!
------------------------------------------------------
http://fsvs.tigris.org/ds/viewMessage.do?dsForumId=3928&dsMessageId=988796
To unsubscribe from this discussion, e-mail:
[[email protected]].
