From: Mike Gilbert <floppym@gentoo.org>
To: gentoo-python <gentoo-python@lists.gentoo.org>
Subject: Re: [gentoo-python] Python 3 in Gentoo
Date: Mon, 30 Jul 2012 13:05:05 -0400 [thread overview]
Message-ID: <CAJ0EP41676TKsnKM4L1g5FfeCWA6F-qM+7+c=H9mk6QyFkMnxg@mail.gmail.com> (raw)
In-Reply-To: <CAKmKYaDTG03OHLt67Bo_DnJZVuHaYD5dSSmLuKikrv-S6tYwFw@mail.gmail.com>
On Mon, Jul 30, 2012 at 12:53 PM, Dirkjan Ochtman <djc@gentoo.org> wrote:
> On Mon, Jul 30, 2012 at 5:56 PM, Mike Gilbert <floppym@gentoo.org> wrote:
>> Where else in the tree could this concept be applied?
>
> I think php5 was first handled this way? Maybe apache2?
> dev-python/jinja2, for sure.
>
>> I would prefer to avoid going through the EAPI process if it is just
>> going to be used for python. And even then, I'm not really excited
>> about the prospect of explaining it.
>
> Nor am I, really. And may be we should pursue your idea at the same
> time. But I think it would sure be nice if we can prevent painting
> ourselves into a similar corner a few years down the road.
>
Ok. I think we will need something a bit more formally defined before
we take such a proposal to a wider audience.
>> A solution that works within the confines of the current EAPI spec
>> should be greatly preferred.
>
> So do you know how many ebuilds we'd have to update to get it right?
>
At the moment, no. If someone could help me write a script to identify
affected packages, that would be great.
If said script uses the portage api to determine the dependency tree,
we will want to modify python.eclass first to reduce the number of
hits. This could be done in a local copy of the tree.
next prev parent reply other threads:[~2012-07-30 17:05 UTC|newest]
Thread overview: 53+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-30 2:13 [gentoo-python] Python 3 in Gentoo Mike Gilbert
2012-07-30 2:23 ` Richard Yao
2012-07-30 5:38 ` Rafael Goncalves Martins
2012-07-30 7:36 ` Dirkjan Ochtman
2012-07-30 8:23 ` Richard Yao
2012-07-30 8:32 ` Dirkjan Ochtman
2012-07-30 9:06 ` Michał Górny
2012-07-30 9:09 ` Dirkjan Ochtman
2012-07-30 9:16 ` Michał Górny
2012-07-30 9:23 ` Dirkjan Ochtman
2012-07-30 9:50 ` Michał Górny
2012-07-30 11:56 ` Dirkjan Ochtman
2012-07-30 13:11 ` Matthew Summers
2012-07-30 13:18 ` Matthew Summers
2012-07-30 13:39 ` Nikolaj Sjujskij
2012-07-30 14:05 ` Jesus Rivero (Neurogeek)
2012-07-31 7:11 ` Nikolaj Sjujskij
2012-07-31 12:09 ` Ben de Groot
2012-07-31 12:14 ` Nikolaj Sjujskij
2012-07-31 14:40 ` Ben de Groot
2012-07-31 16:46 ` Nikolaj Sjujskij
2012-07-30 14:00 ` Jesus Rivero (Neurogeek)
2012-07-30 14:04 ` Michał Górny
2012-07-30 14:07 ` Matthew Summers
2012-07-30 14:11 ` Michał Górny
2012-07-30 15:19 ` Mike Gilbert
2012-07-30 15:22 ` Dirkjan Ochtman
2012-07-30 15:30 ` Mike Gilbert
2012-07-30 15:40 ` Dirkjan Ochtman
2012-07-30 15:56 ` Mike Gilbert
2012-07-30 16:05 ` Matthew Summers
2012-07-30 16:16 ` Mike Gilbert
2012-07-30 16:20 ` Matthew Summers
2012-07-30 16:53 ` Dirkjan Ochtman
2012-07-30 17:05 ` Mike Gilbert [this message]
2012-07-31 15:31 ` Mike Gilbert
2012-08-08 21:07 ` Mike Gilbert
2012-08-08 21:44 ` Thomas Sachau
2012-08-08 22:09 ` Jesus Rivero (Neurogeek)
2012-08-13 19:05 ` Richard Yao
2012-08-13 9:46 ` Dirkjan Ochtman
2012-08-13 19:07 ` Richard Yao
2012-08-13 19:38 ` Dirkjan Ochtman
2012-08-31 2:13 ` Mike Gilbert
2012-09-02 12:21 ` Thomas Sachau
2012-09-02 17:16 ` Mike Gilbert
2012-09-02 17:34 ` Michał Górny
2012-09-02 17:54 ` Mike Gilbert
2012-09-02 19:02 ` Michał Górny
2012-09-03 21:12 ` Mike Gilbert
2012-09-03 21:20 ` Michał Górny
2012-07-30 21:33 ` Thomas Sachau
2012-07-30 7:45 ` 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='CAJ0EP41676TKsnKM4L1g5FfeCWA6F-qM+7+c=H9mk6QyFkMnxg@mail.gmail.com' \
--to=floppym@gentoo.org \
--cc=gentoo-python@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