From: Rich Freeman <rich0@gentoo.org>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Re: Custom ebuilds for CoreOS
Date: Wed, 3 Dec 2014 09:55:30 -0500 [thread overview]
Message-ID: <CAGfcS_kyyMPdELPGD+uhUsH9UQ7Zm1tgWs6_2g3r=JNPx=sA3g@mail.gmail.com> (raw)
In-Reply-To: <CAG2nJkNKyx7OUjZAGMi8d8Dw6m7banQSj7u9LDEz4OA=n_a4Ug@mail.gmail.com>
On Wed, Dec 3, 2014 at 9:28 AM, Mark David Dumlao <madumlao@gmail.com> wrote:
>
> but why? its its own frigging distro now. not gentoo by a long shot.
>
I think it is actually a compliment to the flexibility of Gentoo that
these derivatives are so different. Gentoo is a somewhat-generic
linux distro overall - in its default install it isn't too different
from Debian/Ubuntu/Fedora/Arch on the surface and in terms of typical
package selection. However, ChromeOS and CoreOS are very
non-traditional linux "distros."
When people ask me what Gentoo is "good for" I of course talk about
enthusiasts who care about both understanding their systems and having
a high degree of control, but I also talk about projects where you're
trying to blaze new trails and departing significantly from the
typical "linux desktop" or LAMP box. If all you want is a stable LAMP
box then honestly you're probably better off with the likes of
Debian/CentOS/etc. However, if you're doing something embedded, or
trying to change the world, then starting with Gentoo gives you a lot
more flexibility to blaze new ground while not having to build
EVERYTHING from scratch.
So, when people use Gentoo to do things that we personally don't find
useful, I think it is just a testimony to the fact that we've actually
accomplished one of our core missions: empowering our users to make
their own choices.
--
Rich
next prev parent reply other threads:[~2014-12-03 14:55 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-01 20:46 [gentoo-user] Custom ebuilds for CoreOS James
2014-12-01 21:24 ` Rich Freeman
2014-12-01 22:10 ` [gentoo-user] " James
2014-12-01 21:56 ` [gentoo-user] " Neil Bothwick
2014-12-01 22:32 ` Canek Peláez Valdés
2014-12-03 4:13 ` Saifi Khan
2014-12-02 12:36 ` Andreas K. Huettel
2014-12-02 13:35 ` Rich Freeman
2014-12-02 15:35 ` [gentoo-user] " James
2014-12-02 16:31 ` Rich Freeman
[not found] ` <CAGfcS_mQP9@mail.gmail.com>
2014-12-02 17:37 ` James
2014-12-02 18:39 ` Mark David Dumlao
2014-12-03 12:41 ` J. Roeleveld
2014-12-03 14:28 ` Mark David Dumlao
2014-12-03 14:55 ` Rich Freeman [this message]
2014-12-03 17:16 ` Saifi Khan
2014-12-03 15:17 ` James
2014-12-10 19:20 ` Tom H
2014-12-02 18:55 ` Rich Freeman
2014-12-03 4:17 ` [gentoo-user] " Saifi Khan
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_kyyMPdELPGD+uhUsH9UQ7Zm1tgWs6_2g3r=JNPx=sA3g@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