From: "David Grant" <davidgrant@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Re: etc-update vs dispatch-conf
Date: Tue, 17 Oct 2006 14:43:44 -0700 [thread overview]
Message-ID: <d18977190610171443o725852d7qd80c22e72687f0ad@mail.gmail.com> (raw)
In-Reply-To: <egomu1$shh$1@sea.gmane.org>
On 10/13/06, Remy Blank <remy.blank_asps@pobox.com> wrote:
> maxim wexler wrote:
> > What does the group think?
>
> I don't know about the group, but I use etc-update and keep all of /etc
> in a Subversion working copy. This allows quickly seeing any changes
> made on updates and emerges, reverting changes if anything breaks, and
> keeping track of the reasons for specific changes in commit log messages.
>
> I also use a tool to store file and directory ownership and ACLs in an
> SVN property. I believe dispatch-conf doesn't track ownership and
> permissions.
>
> I even thought about using a distributed VCS like git to be able to push
> changes to a group of machines for e.g. updates, but then again, I don't
> have enough installations to maintain. Has anybody done something in
> this direction?
Great idea to use SVN. RCS on it's own is a pain to deal with.
--
David Grant
http://www.davidgrant.ca
--
gentoo-user@gentoo.org mailing list
next prev parent reply other threads:[~2006-10-17 21:49 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-13 16:56 [gentoo-user] etc-update vs dispatch-conf maxim wexler
2006-10-13 17:49 ` Boyd Stephen Smith Jr.
2006-10-13 17:59 ` Justin Patrin
2006-10-13 18:06 ` Mark Shields
2006-10-14 5:29 ` maxim wexler
2006-10-13 18:46 ` [gentoo-user] " Remy Blank
2006-10-13 22:30 ` Erik
2006-10-14 5:21 ` Trenton Adams
2006-10-14 11:40 ` Steve Evans
2006-10-14 15:40 ` Trenton Adams
2006-10-17 21:43 ` David Grant [this message]
2006-10-14 9:46 ` [gentoo-user] " Hemmann, Volker Armin
2006-10-14 11:08 ` Neil Bothwick
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=d18977190610171443o725852d7qd80c22e72687f0ad@mail.gmail.com \
--to=davidgrant@gmail.com \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox