From: Ciaran McCreesh <ciaran.mccreesh@googlemail.com>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] gtk3 useflag and support of older toolkits
Date: Mon, 11 Jun 2012 18:08:28 +0100 [thread overview]
Message-ID: <20120611180828.51dbddcd@googlemail.com> (raw)
In-Reply-To: <CADqQcK6_zKuHq9zQTKWNjjFm5SisEmDfhr2dgCjX72nEQ1kudg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1465 bytes --]
On Mon, 11 Jun 2012 13:15:40 +0100
Nirbheek Chauhan <nirbheek@gentoo.org> wrote:
> On Sun, Jun 10, 2012 at 9:49 PM, Ciaran McCreesh
> <ciaran.mccreesh@googlemail.com> wrote:
> > On Sun, 10 Jun 2012 21:45:27 +0100
> > Nirbheek Chauhan <nirbheek@gentoo.org> wrote:
> >> It's a simple workaround for the lack of proper ebuild namespacing
> >> on the basis of slots.
> >>
> >> So, till we have that, this works pretty well. :)
> >
> > Until you have that, or something else designed to do what you want,
> > don't come up with some disgusting hack.
>
> So the PMS process should be a bottleneck to getting software out to
> users? I think that's counter-productive.
There is no PMS bottleneck. There is a Portage bottleneck, and there is
a "figuring out how to ensure new features don't interact badly with
either old features or stupid hacks people have done". Abuse of the
kind under discussion is a large contributor to both of those
bottlenecks.
> Our goal here is not to facilitate package manager development but to
> package and distribute software to users.
No, your goal is to provide a distribution. Gentoo has repeatedly shot
itself in the foot, leg, groin etc by favouring short-term hacks over a
well thought out, validated, self-enforcing design. Right now nearly
all of the package manager work is on paying off previously incurred
technical debt, and in the mean time you're busy adding to it.
--
Ciaran McCreesh
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2012-06-11 17:13 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-10 2:38 [gentoo-dev] gtk3 useflag and support of older toolkits hasufell
2012-06-10 3:54 ` Alexandre Rostovtsev
2012-06-10 8:45 ` Maxim Kammerer
2012-06-10 9:47 ` Pacho Ramos
2012-06-10 19:55 ` Sebastian Pipping
2012-06-23 12:53 ` Gilles Dartiguelongue
2012-06-23 12:56 ` Ciaran McCreesh
2012-06-10 20:19 ` Ciaran McCreesh
2012-06-10 20:27 ` hasufell
2012-06-10 20:42 ` Ciaran McCreesh
2012-06-10 20:45 ` Nirbheek Chauhan
2012-06-10 20:49 ` Ciaran McCreesh
2012-06-11 12:15 ` Nirbheek Chauhan
2012-06-11 17:08 ` Ciaran McCreesh [this message]
2012-06-11 18:41 ` Pacho Ramos
2012-06-11 18:48 ` Ciaran McCreesh
2012-06-23 13:02 ` Gilles Dartiguelongue
2012-06-23 13:08 ` Ciaran McCreesh
2012-06-23 13:33 ` Gilles Dartiguelongue
2012-06-23 13:40 ` Ciaran McCreesh
2012-06-23 14:45 ` Gilles Dartiguelongue
2012-06-23 16:09 ` Ciaran McCreesh
2012-06-24 4:15 ` Doug Goldstein
2012-06-24 8:07 ` Ben de Groot
2012-06-24 9:09 ` hasufell
2012-06-24 10:11 ` Gilles Dartiguelongue
2012-06-24 10:33 ` hasufell
2012-06-23 18:26 ` Michał Górny
2012-06-23 18:29 ` Ciaran McCreesh
2012-06-24 3:49 ` Doug Goldstein
2012-06-24 9:28 ` Michał Górny
2012-06-23 13:39 ` Gilles Dartiguelongue
2012-06-23 18:31 ` hasufell
2012-06-24 3:47 ` Doug Goldstein
2012-06-23 15:59 ` Michał Górny
2012-06-11 9:24 ` hasufell
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=20120611180828.51dbddcd@googlemail.com \
--to=ciaran.mccreesh@googlemail.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