From: "Nikolaj Sjujskij" <sterkrig@myopera.com>
To: gentoo-python <gentoo-python@lists.gentoo.org>
Cc: "Mike Gilbert" <floppym@gentoo.org>
Subject: Re: [gentoo-python] python-distutils.eclass vs. python.eclass + distutils.eclass
Date: Fri, 01 Jun 2012 16:42:37 +0400 [thread overview]
Message-ID: <op.we75lbrnh7emz2@verkdatorn.npdb> (raw)
In-Reply-To: <CAJ0EP43mMXZJ1aKAEO9YSNSiexyVkGUk1BL+9sx8qmqOutaNMA@mail.gmail.com>
Den 2012-05-26 17:33:45 skrev Mike Gilbert <floppym@gentoo.org>:
>> Let's take a "stable" user who updates (`emerge --update --deep
>> --newuse
>> @world`) his/her system regularly.
>> Python 3.3 is released, added to Portage tree and eventually unmasked.
>> PYTHON_TARGETS variable is changed to include 3.3. And suddenly `emerge
>> --newuse @world` on stable system suggests rebuilding of every package
>> using
>> new eclass, because new (though disabled) USE-flags was added. And when
>> Python 3.3 is keyworded stable, hence bringing new default
>> PYTHON_TARGETS,
>> user should now rebuild those packages once more, but now, at least, not
>> uselessly.
> This is why I do my world updates with --changed-use instead of
> --newuse. The package manager already has the ability to deal with
> such scenarios intelligently, you just have to let it.
Point taken, but --newuse is still "recommended" option (i.e.,
`--depclean` suggests it and Handbook describes it as well). Whereas
'--changed-use' is more or less "spoken lore" among users.
> I did not speak up in the previous thread, but here are some of the
> advantages to a use flag based approach (PYTHON_TARGETS):
> ...
Agreed.
> Here is how I justify the current default value of PYTHON_TARGETS: Due
> to past decisions, python3.2 is installed by default on all amd64 and
> x86 systems, so having python3_2 enabled by default makes sense.
> However, there are many things do not work in python 3, so the
> python2_7 target is a necessity.
Yes, I understand that. It is really the most sensible default in the
circumstances.
Still, it is a bit clumsy with new installs. It'd be nice if stage3 had
PYTHON_TARGETS="python32" (since it's the only Python interpreter
installed), while profile had current default.
Of course, news item is a must for that kind of thing. Describing new
variable, suggesting `--changed-use` instead of `--newuse` etc.
next prev parent reply other threads:[~2012-06-01 12:42 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAB_KkxwspDjWOpV7FSdwxD5MHS-qjtxrUQBiwbsc2yRhqXQntQ@mail.gmail.com>
2012-05-26 9:32 ` [gentoo-python] python-distutils.eclass vs. python.eclass + distutils.eclass Maxim Koltsov
2012-05-26 9:53 ` Dirkjan Ochtman
2012-05-26 13:01 ` Nikolaj Sjujskij
2012-05-26 13:07 ` Michał Górny
2012-05-26 13:09 ` Nikolaj Sjujskij
2012-05-26 18:28 ` Krzysztof Pawlik
2012-05-26 18:45 ` Maxim Koltsov
2012-05-26 19:07 ` Michał Górny
2012-06-01 10:36 ` Nikolaj Sjujskij
2012-05-26 13:33 ` Mike Gilbert
2012-06-01 12:42 ` Nikolaj Sjujskij [this message]
2012-05-26 9:53 ` Michał Górny
2012-05-26 9:55 ` Dirkjan Ochtman
2012-05-26 10:06 ` Michał Górny
2012-05-26 18:31 ` Krzysztof Pawlik
2012-05-26 23:18 ` Mike Gilbert
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=op.we75lbrnh7emz2@verkdatorn.npdb \
--to=sterkrig@myopera.com \
--cc=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