From: Krzysztof Pawlik <nelchael@gentoo.org>
To: Nikolaj Sjujskij <sterkrig@myopera.com>
Cc: gentoo-python@lists.gentoo.org
Subject: Re: [gentoo-python] New eclass for Python
Date: Mon, 14 May 2012 20:00:28 +0200 [thread overview]
Message-ID: <4FB1483C.3070902@gentoo.org> (raw)
In-Reply-To: <op.wea7hbhlh7emz2@gentoobook.trollsnaetverk>
[-- Attachment #1: Type: text/plain, Size: 2168 bytes --]
On 14/05/12 19:42, Nikolaj Sjujskij wrote:
> Den 2012-05-14 20:12:51 skrev Krzysztof Pawlik <nelchael@gentoo.org>:
>
>> On 13/05/12 21:57, Dirkjan Ochtman wrote:
>>> On Sat, May 12, 2012 at 10:32 PM, Mike Gilbert <floppym@gentoo.org> wrote:
>>>> Why not emulate php/ruby and set a default value in the base profile?
>>>> See profiles/base/make.defaults.
>>>>
>>>> I think PYTHON_TARGETS="python2_7 python3_2" would be a reasonable choice.
>>>
>>> Yeah, I think we should provide a default value, and this default
>>> value looks good to me.
>>
>> Feel free to do so :) I would disagree with adding py3 to default, but it's
>> only me.
> It would be pretty strange if we had had Py3k as default Python (i.e. in
> stage3) and PYTHON_TARGETS for another version altogether.
I don't have Py3 installed at all on all my machines.
> And how would new eclass behave in such case? Just-out-of-stage3 system would
> have only Python 3.2 installed, but PYTHON_TARGETS="python2_7 python3_2". Let's
> say user tries to:
> # emerge -av pygments
> Of course, assuming dev-python/pygments had been ported to new eclass. Would
> python-distutils-ng handle this correctly and transparently? Without obscure
> errors like "You wants Python 2.7 but haz no Python 2.7"? Without pulling
> dev-lang/python:2.7 in? If not, I call this serious usability regression.
It seems you have no clue how this eclass works. If you have only py3 installed,
and you set PYTHON_TARGETS="python2_7" then dev-lang/python:2.7 will be added to
DEPEND and installed.
The user asked to install for py2:7 so he will get this done. It's not a
usability regression - it's expected behaviour: user wants to build for FOO:X.Y
then the eclass adds FOO:X.Y to DEPEND.
I fail to see how would you like to "correctly and transparently" (whatever it
means to you) do it. If you don't accept as a solution an error message or
pulling in py2:7 then there's no other way - you either install missing
dependencies or die with an error, no third way.
--
Krzysztof Pawlik <nelchael at gentoo.org> key id: 0xF6A80E46
desktop-misc, java, vim, kernel, python, apache...
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 554 bytes --]
next prev parent reply other threads:[~2012-05-14 18:00 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-28 21:13 [gentoo-python] New eclass for Python Krzysztof Pawlik
2012-02-29 5:13 ` Mike Gilbert
2012-02-29 8:11 ` Dirkjan Ochtman
2012-03-03 7:59 ` Arfrever Frehtes Taifersar Arahesis
2012-03-25 18:56 ` [gentoo-python] Re: [gentoo-dev] " Krzysztof Pawlik
2012-05-12 9:19 ` [gentoo-python] " Nikolaj Sjujskij
2012-05-12 10:04 ` Krzysztof Pawlik
2012-05-12 17:20 ` Michał Górny
2012-05-12 20:32 ` Mike Gilbert
2012-05-13 19:57 ` Dirkjan Ochtman
2012-05-14 16:12 ` Krzysztof Pawlik
2012-05-14 17:42 ` Nikolaj Sjujskij
2012-05-14 18:00 ` Krzysztof Pawlik [this message]
2012-05-13 6:55 ` Nikolaj Sjujskij
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=4FB1483C.3070902@gentoo.org \
--to=nelchael@gentoo.org \
--cc=gentoo-python@lists.gentoo.org \
--cc=sterkrig@myopera.com \
/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