P.Marek wrote: > On Saturday 20 December 2008 Peter Rabbitson wrote: >> P.Marek wrote: >>> It might make sense to keep /etc/fsvs; the URLs list gets moved to the >>> WAA with current trunk, and you're ignore patterns would be stored, too. >> I did that, however now I am confronted by another problem - timestamp >> changes on directories are constantly tracked. So I either have to >> commit the new mtime of the unchanged directories (thus polluting the >> log) or always commit files by name, excluding the changed dirs over and >> over again. >> >> Is there a general way to prevent fsvs from tracking timestamps, when >> fsvs status -CC shows no changes? > Well, you could tell FSVS that only "text" changes are of interest; there's > the filter option. > Just create a "config" file in /etc/fsvs (or, if you want that more specific, > in /etc/fsvs/<your wc base directory>), and put > filter=text > in it. > Then the mtime will still be tracked, but "status" and "commit" will decide > to > show only new, deleted, or content-changed entries. > > Is that what you want? >
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. 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. >> Also (and I realise this is material for a new thread) - is there a way >> to separate install commits from configuration commits? Like any time I >> apt-get install something, I'd want to commit it to some url, and then >> whenever I make actual config changes - I'd like to commit it to a >> separate url, so I can see all manual changes just by browsing the svn >> log. Is this something that can be achieved with the multiurl capability >> of fsvs? > Well, the multi-URL commit is one way; or, maybe better (and simpler), just > drive *two* different repositories from the same WC, by using some wrapper > (like a shell-script named config-fsvs or install-fsvs) that sets $FSVS_WAA > and $FSVS_CONF to other values. > > Then you can track your WC in two repositories simultaneously, independent of > each other. > > > 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 Thank you for taking the time to explain this stuff, much appreciated. Peter ------------------------------------------------------ http://fsvs.tigris.org/ds/viewMessage.do?dsForumId=3928&dsMessageId=988407 To unsubscribe from this discussion, e-mail: [[email protected]].
