From: Ciaran McCreesh <ciaran.mccreesh@googlemail.com>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Re: Re: Re: Re: RFC: Make 10.0 profiles EAPI-2 'compliant'
Date: Thu, 20 Aug 2009 21:23:08 +0100 [thread overview]
Message-ID: <20090820212308.4c867d37@snowcone> (raw)
In-Reply-To: <4A8D899E.7080501@trelane.net>
[-- Attachment #1: Type: text/plain, Size: 2422 bytes --]
On Thu, 20 Aug 2009 13:36:30 -0400
Andrew D Kirch <trelane@trelane.net> wrote:
> > > I look forward to seeing Funtoo's creation of EAPI funtoo-2.
>
> Obviously you don't get it. We aren't going to spend time writing
> this sort of spurious and unnecessary specification documents.
Why not? Are you saying you don't want the way Funtoo's package manager
works to be documented? I'll remind you that the feature in question
isn't documented anywhere.
It's a five minute job, and it will mean Funtoo's tree can be used by
any of the many third party tools that work with repositories.
I find it hard to believe that one of Funtoo's goals is to use
undocumented features and not have any way for contributors to know what
the package format is.
> Nor do you, as I have proven, have standing to file such a bug as you
> are not on the council (even as an alternate), and the SOLE option
> for packages violating PMS per the council is a council vote to mask
> the package.
That's not the sole option at all. The first thing to do is to get the
issue fixed. Masking is the nuclear option.
> Portage is a tool used by users, repoman is a tool used by developers
> for tree QA.
repoman isn't an effective way of getting messages to overlay
developers.
> Considering the zeal with which you are pushing this
> "accidentally works with Portage until Portage is fixed", I believe a
> reasonable person is going to look at the b.g.o bug, and at the
> Paludis bug and realize that you're more interested in process than
> innovation, and that you simply don't care about throwing needless
> confusing warnings at users (indeed a prima facia examination of
> Paludis would seem to confirm this, and my concerns WRT Paludis and
> the development methods are well known). I think they'll also
> realize that throughout this process you've been less than honest,
> and a huge impairment to the work going on at Funtoo.
The process for innovation is EAPIs. This allows innovation to go
through in a well defined manner that doesn't cause highly random
breakage every time a new feature comes along. Unfortunately, your
early misconception that EAPIs are about Paludis is getting in the way
of you taking a few simple steps to turn this from exploiting
undocumented behaviour to a well defined feature.
EAPIs are there to help you, not hold you back.
--
Ciaran McCreesh
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2009-08-20 20:23 UTC|newest]
Thread overview: 64+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-12 17:58 [gentoo-dev] RFC: Make 10.0 profiles EAPI-2 'compliant' Jeremy Olexa
2009-08-12 18:07 ` Ben de Groot
2009-08-12 18:15 ` Samuli Suominen
2009-08-12 18:41 ` Tomáš Chvátal
2009-08-12 18:46 ` Ciaran McCreesh
2009-08-13 5:55 ` [gentoo-dev] " Ryan Hill
2009-08-13 10:35 ` Tiziano Müller
2009-08-13 13:32 ` Nirbheek Chauhan
2009-08-13 13:45 ` Maciej Mrozowski
2009-08-13 12:29 ` Ciaran McCreesh
2009-08-14 0:13 ` Ryan Hill
2009-08-21 14:25 ` Arfrever Frehtes Taifersar Arahesis
2009-08-21 15:20 ` David Leverton
2009-08-21 21:17 ` Ryan Hill
2009-08-21 21:42 ` Arfrever Frehtes Taifersar Arahesis
2009-08-21 21:46 ` Ciaran McCreesh
2009-08-21 23:10 ` Maciej Mrozowski
2009-08-21 23:44 ` Robert Buchholz
2009-08-22 0:29 ` Chip Parker
2009-08-22 0:34 ` Ciaran McCreesh
2009-08-22 21:47 ` Chip Parker
2009-08-22 21:52 ` Ciaran McCreesh
2009-08-23 0:26 ` Chip Parker
2009-08-23 0:32 ` David Leverton
2009-08-23 1:10 ` Chip Parker
2009-08-23 1:16 ` Ciaran McCreesh
2009-08-23 1:19 ` David Leverton
2009-08-23 0:34 ` Ciaran McCreesh
2009-08-23 2:39 ` Arfrever Frehtes Taifersar Arahesis
2009-08-23 10:07 ` David Leverton
2009-08-22 1:45 ` Ryan Hill
2009-08-22 5:32 ` Andrew D Kirch
2009-08-22 9:35 ` Arttu V.
2009-08-22 20:48 ` Ryan Hill
2009-08-24 18:01 ` Christian Faulhammer
2009-08-23 15:26 ` Paul de Vrieze
2009-08-22 0:54 ` AllenJB
2009-08-22 6:18 ` Tiziano Müller
2009-08-22 6:23 ` Andrew D Kirch
2009-08-22 13:06 ` Tiziano Müller
2009-08-22 19:39 ` Ciaran McCreesh
2009-08-22 20:22 ` Arfrever Frehtes Taifersar Arahesis
2009-08-22 20:25 ` Ciaran McCreesh
2009-08-22 20:50 ` Ryan Hill
2009-08-22 3:40 ` Duncan
2009-08-13 12:50 ` Mark Bateman
2009-08-13 12:56 ` Ciaran McCreesh
2009-08-13 17:32 ` Mark Bateman
2009-08-13 17:53 ` Ciaran McCreesh
2009-08-13 18:06 ` Mark Bateman
2009-08-13 18:14 ` Ciaran McCreesh
2009-08-13 18:22 ` [gentoo-dev] " Steven J Long
2009-08-13 18:34 ` Ciaran McCreesh
2009-08-18 1:30 ` [gentoo-dev] " Steven J Long
2009-08-18 6:04 ` Rémi Cardona
2009-08-20 10:02 ` [gentoo-dev] " Steven J Long
2009-08-20 10:13 ` Andrew D Kirch
2009-08-20 14:52 ` Ciaran McCreesh
2009-08-20 17:36 ` Andrew D Kirch
2009-08-20 20:23 ` Ciaran McCreesh [this message]
2009-08-21 0:04 ` [gentoo-dev] " Steven J Long
2009-08-21 2:15 ` Chip Parker
2009-08-21 2:41 ` [gentoo-dev] " Ryan Hill
2009-08-12 18:53 ` [gentoo-dev] " Arfrever Frehtes Taifersar Arahesis
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=20090820212308.4c867d37@snowcone \
--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