From: Michael Weber <xmw@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: update commands / world file pollution Re: [gentoo-dev] Stable sys-devel/gcc USE flag changes WAS: [gentoo-commits] gentoo-x86 commit in eclass: ChangeLog toolchain.eclass
Date: Fri, 18 Jan 2013 09:13:58 +0100 [thread overview]
Message-ID: <50F90446.2070100@gentoo.org> (raw)
In-Reply-To: <CAN-7s6a+LEpQnA_EU__pgaUMKXLvw+wxYcFS9N4P3Oif83xkVA@mail.gmail.com>
On 01/18/2013 08:36 AM, Benedikt Böhm wrote:
> On Fri, Jan 18, 2013 at 8:27 AM, Michael Weber <xmw@gentoo.org
> <mailto:xmw@gentoo.org>> wrote:
> I'd like to drop one strong suggestion about configuration management
> that might be beneficial here: use version control software!
> or even /etc/.git ... it saved my life on numerous occasions
Sure, bit thats's the point were diversity (hostnames, ssh_host_keys)
kicks in (which has been eliminated in mentioned example) and
the repo carries confidential information.
(Well, if somebody places an compromised update in the
local-overlay, i'd blindly install anything)
I even have / inside git for testing, with excludes on /opt/ /usr
/{s,}/bin /etc/ssl and so on.
It works and is handy to easily add apache config, web-app-config
installed roundcube, layman overlay list, but the maintenance of the
.gitignore raises and hardlink solutions like dirvish make more sense
for being complete backups (LD_LIBRRY_PATH=/backup/.../tree/usr/lib).
> for reference, here is my updateworld script, which also handles python,
> ruby, perl, revdep-rebuild and all that
> crap: https://github.com/zenops/cookbooks/blob/master/cookbooks/portage/files/default/scripts/updateworld
cool.
So basically everyone uses personal `apt-get update` (cvs co, porticron,
emerge+layman, eix-sync) strategies and even more
funny little scripts for `apt-get upgrade` (-avuND world, aliases,
scripts).
I wonder if anybody uses unattended [backup+]emerge as cron job.
I'm really temped to do so, but with users relying on these machines I'm
always chicken-out.
--
Michael Weber
Gentoo Developer
web: https://xmw.de/
mailto: Michael Weber <xmw@gentoo.org>
next prev parent reply other threads:[~2013-01-18 8:14 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20130115023053.8897C2171E@flycatcher.gentoo.org>
2013-01-15 7:20 ` [gentoo-dev] Stable sys-devel/gcc USE flag changes WAS: [gentoo-commits] gentoo-x86 commit in eclass: ChangeLog toolchain.eclass Michael Weber
2013-01-15 13:44 ` [gentoo-dev] Stable sys-devel/gcc USE flag changes Ian Stakenvicius
2013-01-15 14:03 ` Rich Freeman
2013-01-15 14:16 ` Dirkjan Ochtman
2013-01-15 14:27 ` Ian Stakenvicius
2013-01-15 14:39 ` Dirkjan Ochtman
2013-01-15 14:49 ` Ian Stakenvicius
2013-01-15 14:53 ` Ian Stakenvicius
2013-01-15 15:24 ` Rich Freeman
2013-01-15 20:18 ` Peter Stuge
2013-01-15 20:51 ` Dirkjan Ochtman
2013-01-16 16:36 ` Michael Weber
2013-01-16 16:47 ` Michael Orlitzky
2013-01-16 16:49 ` Michael Orlitzky
2013-01-16 17:24 ` Ian Stakenvicius
2013-01-16 17:33 ` Michael Orlitzky
2013-01-17 0:00 ` Michael Weber
2013-01-17 3:24 ` Rich Freeman
2013-01-17 14:45 ` Peter Stuge
2013-01-17 14:58 ` Ian Stakenvicius
2013-01-17 14:46 ` Zac Medico
2013-01-16 17:24 ` Ian Stakenvicius
2013-01-16 17:32 ` Michael Orlitzky
2013-01-17 14:52 ` Zac Medico
2013-01-17 16:31 ` Michael Orlitzky
2013-01-17 17:11 ` Ian Stakenvicius
2013-01-17 17:33 ` Michael Orlitzky
2013-01-17 23:55 ` [gentoo-dev] " Duncan
2013-01-16 2:20 ` [gentoo-dev] Re: Stable sys-devel/gcc USE flag changes WAS: [gentoo-commits] gentoo-x86 commit in eclass: ChangeLog toolchain.eclass Ryan Hill
2013-01-18 7:27 ` update commands / world file pollution Re: [gentoo-dev] " Michael Weber
2013-01-18 7:36 ` Benedikt Böhm
2013-01-18 8:13 ` Michael Weber [this message]
2013-01-18 8:28 ` Benedikt Böhm
2013-01-18 8:41 ` Michael Weber
2013-01-18 13:13 ` Benedikt Böhm
2013-01-18 13:18 ` Benedikt Böhm
2013-01-18 13:25 ` Ian Stakenvicius
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=50F90446.2070100@gentoo.org \
--to=xmw@gentoo.org \
--cc=gentoo-dev@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