public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Mike Gilbert <floppym@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Re: [gentoo-python] New eclass for Python
Date: Wed, 29 Feb 2012 13:39:26 -0500	[thread overview]
Message-ID: <CAJ0EP42BUe5Sdx6gTmwQTcWnKGVBa=86iKLLzzA19bswZCLDOg@mail.gmail.com> (raw)
In-Reply-To: <4F4E62D5.7020801@gentoo.org>

On Wed, Feb 29, 2012 at 12:39 PM, Krzysztof Pawlik <nelchael@gentoo.org> wrote:
> On 29/02/12 09:11, Dirkjan Ochtman wrote:
>> On Tue, Feb 28, 2012 at 22:13, Krzysztof Pawlik <nelchael@gentoo.org> wrote:
>>> If there are no objections then during the weekend (March 3, 4) I will add this
>>> to portage (after finishing remaining TODO items, PyPy requires 4G of RAM(!!)).
>>
>> Can we perhaps just name it python-r2 rather than python-distutils-ng?
>> Seems descriptive enough...
>
> Yes and no - it's named python-distutils because main focus was this
> combination, it can work for other cases too, it's just that it combines
> functionality from both old eclasses. Besides I like the name, but I can be
> convinced to name it python-r2.eclass.
>

The distutils-based packages are a good starting point. The name is a
good fit for that.

Looking forward, I think it might make sense to move some of the
functionality to a "core" python eclass that would just be for utility
functions -- similar to the python/distutils split we have now. This
would be used in ebuilds that are not primarily based around distutils
(setup.py).



  reply	other threads:[~2012-02-29 18:40 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-28 21:13 [gentoo-dev] New eclass for Python Krzysztof Pawlik
2012-02-29  3:21 ` Sergei Trofimovich
2012-02-29 17:34   ` Krzysztof Pawlik
2012-02-29  5:13 ` [gentoo-dev] Re: [gentoo-python] " Mike Gilbert
2012-02-29 17:35   ` Krzysztof Pawlik
2012-02-29  7:49 ` [gentoo-dev] " "Paweł Hajdan, Jr."
2012-02-29 17:38   ` Krzysztof Pawlik
2012-02-29 18:03     ` Jeroen Roovers
2012-02-29  8:11 ` [gentoo-dev] Re: [gentoo-python] " Dirkjan Ochtman
2012-02-29 17:39   ` Krzysztof Pawlik
2012-02-29 18:39     ` Mike Gilbert [this message]
2012-02-29  8:17 ` [gentoo-dev] " Fabian Groffen
2012-02-29 17:34   ` Krzysztof Pawlik
2012-02-29 19:51 ` Alexandre Rostovtsev
2012-02-29 20:24   ` Krzysztof Pawlik
2012-02-29 21:08     ` Andreas K. Huettel
2012-02-29 21:19       ` Krzysztof Pawlik
2012-02-29 21:57     ` Alexandre Rostovtsev
2012-03-01 18:42       ` Krzysztof Pawlik
2012-03-03  7:59 ` [gentoo-dev] Re: [gentoo-python] " Arfrever Frehtes Taifersar Arahesis
2012-03-03  8:18   ` Zac Medico
2012-03-25 18:56 ` [gentoo-dev] " Krzysztof Pawlik
2012-03-25 19:08   ` Luca Barbato
2012-03-26  7:20   ` justin
2012-03-26 16:11     ` Krzysztof Pawlik
2012-03-26 16:23       ` Krzysztof Pawlik
2012-04-04  8:50         ` Corentin Chary
2012-04-04 14:22           ` Mike Gilbert
2012-04-04 14:29             ` Corentin Chary
2012-04-04 14:41           ` Mike Gilbert
2012-04-05  0:07             ` Brian Harring
2012-04-05  0:36               ` Mike Gilbert
2012-04-05  0:45                 ` Brian Harring
2012-03-26  7:21   ` justin
2012-03-26 16:02     ` Krzysztof Pawlik

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='CAJ0EP42BUe5Sdx6gTmwQTcWnKGVBa=86iKLLzzA19bswZCLDOg@mail.gmail.com' \
    --to=floppym@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