From: Dirkjan Ochtman <djc@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] [RFC] Initial python-r1.eclass & distutils-r1.eclass
Date: Sat, 29 Sep 2012 16:37:15 +0200 [thread overview]
Message-ID: <CAKmKYaBPRCbdWwGktgvxwCJPpJJDMcZcFvSOSTNNk8=1j_qAdw@mail.gmail.com> (raw)
In-Reply-To: <5067052D.7050205@gentoo.org>
On Sat, Sep 29, 2012 at 4:26 PM, hasufell <hasufell@gentoo.org> wrote:
> That still does not explain the reasons why this work was initiated.
>
> If there is any way to fix the current eclass, that should be preferred.
I tend to agree. Michał, let me first say I value the time you have
invested to make the eclasses better. However, at this point I have a
strong feeling that we have more people willing to write code to fix
things than we have people building consensus on what
features/policies/mechanisms we need to make it easy to write
high-quality ebuilds for Python/distutils. I would prefer discussions
on problems that the current ebuilds have and discussions on how to
solve them, not at the code level, but that the mechanism level.
Cheers,
Dirkjan
next prev parent reply other threads:[~2012-09-29 14:38 UTC|newest]
Thread overview: 48+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-29 8:53 [gentoo-dev] [RFC] Initial python-r1.eclass & distutils-r1.eclass Michał Górny
2012-09-29 10:00 ` Tomáš Chvátal
2012-09-29 10:23 ` Michał Górny
2012-09-29 10:45 ` Michał Górny
2012-09-29 19:34 ` Luca Barbato
2012-09-29 10:20 ` Markos Chandras
2012-09-29 10:49 ` Michał Górny
2012-09-29 13:49 ` hasufell
2012-09-29 14:19 ` Ian Stakenvicius
2012-09-29 14:26 ` hasufell
2012-09-29 14:37 ` Dirkjan Ochtman [this message]
2012-09-29 18:39 ` Michał Górny
2012-09-29 20:48 ` hasufell
2012-09-30 14:01 ` Michał Górny
2012-09-29 15:37 ` Ian Stakenvicius
2012-09-29 15:45 ` hasufell
2012-09-29 15:50 ` Ian Stakenvicius
2012-09-29 15:54 ` hasufell
2012-09-29 15:54 ` Ciaran McCreesh
2012-09-29 18:40 ` Michał Górny
2012-09-29 19:20 ` Pacho Ramos
2012-09-29 20:34 ` Michał Górny
2012-09-30 8:31 ` Pacho Ramos
2012-09-30 8:58 ` Fabian Groffen
2012-09-30 9:47 ` Pacho Ramos
2012-09-30 13:28 ` Michał Górny
2012-09-30 13:47 ` Fabian Groffen
2012-09-30 13:57 ` Michał Górny
2012-09-30 14:12 ` Fabian Groffen
2012-09-30 18:15 ` Zac Medico
2012-09-30 21:47 ` Brian Harring
2012-10-01 6:36 ` Fabian Groffen
2012-10-01 7:19 ` Brian Harring
2012-10-01 15:17 ` Marien Zwart
2012-10-01 15:44 ` Fabian Groffen
2012-09-29 15:47 ` hasufell
2012-09-29 18:35 ` Michał Górny
2012-09-30 5:09 ` Ben de Groot
2012-10-05 12:42 ` Michał Górny
2012-10-25 16:41 ` hasufell
2012-10-25 17:10 ` Ian Stakenvicius
2012-10-25 17:43 ` Michał Górny
2012-10-25 18:55 ` hasufell
2012-10-25 20:13 ` Michał Górny
2012-10-26 18:28 ` hasufell
2012-10-25 20:37 ` Michał Górny
2012-10-25 19:19 ` hasufell
2012-10-25 20:40 ` Michał Górny
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='CAKmKYaBPRCbdWwGktgvxwCJPpJJDMcZcFvSOSTNNk8=1j_qAdw@mail.gmail.com' \
--to=djc@gentoo.org \
--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