From: Pacho Ramos <pacho@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Cc: dlcampbell@gmx.com
Subject: Re: [gentoo-dev] Going against co-maintainer's wishes (ref. bug 412697)
Date: Sun, 26 May 2013 09:56:38 +0200 [thread overview]
Message-ID: <1369554998.2884.7.camel@localhost> (raw)
In-Reply-To: <20130526085538.42214885@gentoo.org>
El dom, 26-05-2013 a las 08:55 +0200, Michał Górny escribió:
[...]
> > As far as resisting systemd, why is that so bad? Vertical integration is
> > generally a bad idea with the sole exception of when your use case(s)
> > line up perfectly with the ivory tower and you need all of the offered
> > features. If Gentoo falls to systemd, there will literally be no
> > Linux-based distros left to prevent it from taking over, and as a result
> > Linux-based systems will become more and more tightly integrated,
> > killing the choice that Gentoo truly stands for and homogenizing everything.
>
> It is bad because ebuilds are not place to put politics into. If you
> want to become dev, you should understand this. We are supposed to be
> serious people. Serious people don't break user systems or refuse to
> support them in the name of manifesting their wishes.
>
> It is bad because it's not systemd that's losing, it's Gentoo. Except
> for the fact that there's just a few people that take Gentoo seriously
> these days.
>
> Upstreams clearly show that they don't care. We can either sit
> in the corner and resent, or we can work on improving the situation.
> And going on flamewars or manifestations doesn't really improve
> anything, you should know that by now.
>
It's also bad because you are affecting to a lot of people that can/want
to use systemd, forcing you to have semi-usable setups because of your
personal preferences.
next prev parent reply other threads:[~2013-05-26 7:56 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <51A1A294.3000609@sporkbox.us>
2013-05-26 6:24 ` Re: [gentoo-dev] Going against co-maintainer's wishes (ref. bug 412697) Daniel Campbell
2013-05-26 6:55 ` Michał Górny
2013-05-26 7:37 ` Daniel Campbell
2013-05-26 7:56 ` Pacho Ramos [this message]
2013-05-25 16:14 Ben de Groot
2013-05-25 16:48 ` Michał Górny
2013-05-25 17:38 ` Rich Freeman
2013-05-25 20:02 ` Chí-Thanh Christopher Nguyễn
2013-05-25 20:40 ` Rich Freeman
2013-05-25 20:45 ` Michał Górny
2013-05-25 21:38 ` Luca Barbato
2013-05-26 7:23 ` Ben de Groot
2013-05-26 7:43 ` Michał Górny
2013-05-26 10:04 ` Rich Freeman
2013-05-26 15:21 ` Ben de Groot
2013-05-26 16:15 ` Rick "Zero_Chaos" Farina
2013-05-26 17:14 ` Matt Turner
2013-05-26 17:19 ` Andreas K. Huettel
2013-05-26 7:54 ` Pacho Ramos
2013-05-25 17:00 ` Pacho Ramos
2013-05-25 17:14 ` Carlos Silva
2013-05-26 7:15 ` Ben de Groot
2013-05-26 7:44 ` Pacho Ramos
2013-05-26 7:45 ` Michał Górny
2013-05-26 9:59 ` Luca Barbato
2013-05-25 18:13 ` Markos Chandras
2013-05-25 19:53 ` Anthony G. Basile
2013-05-25 19:58 ` Mike Gilbert
2013-05-25 21:55 ` Anthony G. Basile
2013-05-25 19:59 ` Rich Freeman
2013-05-26 7:00 ` Michał Górny
2013-05-26 7:22 ` Tiziano Müller
2013-05-26 7:46 ` Pacho Ramos
2013-05-26 7:49 ` Michał Górny
2013-05-26 7:00 ` Ben de Groot
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=1369554998.2884.7.camel@localhost \
--to=pacho@gentoo.org \
--cc=dlcampbell@gmx.com \
--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