From: Rich Freeman <rich0@gentoo.org>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Re: [OT] Six non-Gentoo installs
Date: Tue, 14 Oct 2014 23:14:14 -0400 [thread overview]
Message-ID: <CAGfcS_=TcGP-cLZB+TpE76arhhFQzd5QbCwo9HXN5x4_HAcPGw@mail.gmail.com> (raw)
In-Reply-To: <m1kmpq$9g3$1@ger.gmane.org>
On Tue, Oct 14, 2014 at 10:39 PM, Grant Edwards
<grant.b.edwards@gmail.com> wrote:
> On 2014-10-15, Alec Ten Harmsel <alec@alectenharmsel.com> wrote:
>
>> The main problem (imnho) is that you think CentOS cares about
>> configurability/multiple ways of doing things.
>
> Oh, I don't think that -- it's pretty obvious that in the RedHat
> world, choice is not an option. It's one prix fixe menu, and you can
> either eat what's set in front of you or go hungry.
>
I can see the potential benefits of that. It sounds a bit like the
whole convention over configuration approach. As long as the
convention works, it does greatly simplify things.
One thing I do like is the trend towards putting default configs in
/usr and using /etc more for overrides. If everything went that way
(and we stuck stuff like /var/lib/portage/world in /etc) then you
could have an /etc with 20 short files in it that reflected all the
tweaking you did to a system from a generic install. Sure, I love
config protection and etc-keeper and the like, but I'd like it still
better if etc wasn't such a mix.
I'd really love it if I could dump 20 files in /etc and run emerge
-uDNv world and end up with a system identical to the one those 20
files were copied from.
--
Rich
next prev parent reply other threads:[~2014-10-15 3:14 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-14 22:36 [gentoo-user] [OT] Six non-Gentoo installs Grant Edwards
2014-10-15 0:17 ` Alec Ten Harmsel
2014-10-15 2:39 ` [gentoo-user] " Grant Edwards
2014-10-15 3:14 ` Rich Freeman [this message]
2014-10-15 12:14 ` thegeezer
2014-10-15 19:54 ` Rich Freeman
2014-10-15 14:37 ` Grant Edwards
2014-10-15 3:47 ` Alec Ten Harmsel
2014-10-15 1:08 ` James
2014-10-15 2:43 ` Grant Edwards
2014-10-16 14:21 ` [gentoo-user] " Tom H
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='CAGfcS_=TcGP-cLZB+TpE76arhhFQzd5QbCwo9HXN5x4_HAcPGw@mail.gmail.com' \
--to=rich0@gentoo.org \
--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