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?
> > Do you plan to blog about that, and your experience? If you ever do,
> > please send me the link, so I can mention it in the documentation.
>
> Actually I do not plan to use fsvs a backup tool (I have separate
> blanket backup strategies), but as an audit log instead. This is also
> why I am interested in skipping the timestamp changes, as they are of no
> interest to me.
Ok.
> 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.
> Eventually when time permits I want to setup a new Linode from scratch
> with a debian bootstrap, making fsvs commits at every point where
> something of interest happens. I think that if I am careful enough, I
> can make the log actualy make sense. Then simply exposing the fsvs
> repository via svnweb, will yield a complete "LFS by example" reading,
> which will constantly evolve alongside my server. If I ever get to this
> point, and it starts shaping up as a viable idea, I will certainly share
> a link with the mailing list.
Fine, that's something I'm looking forward to!
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=988189
To unsubscribe from this discussion, e-mail:
[[email protected]].
