On 12/03/2010 07:05 AM, Michał Górny wrote:
> On Fri, 03 Dec 2010 11:35:14 +0100
> Sebastian Pipping wrote:
>
>> to better communicate USE_PYTHON we could use:
>
> The first question that comes into my mind is -- why do we need
> to communicate that? I think that USE_PYTHON is a pretty specific
On 12/03/10 14:16, Michał Górny wrote:
> Then the question would be -- if that version causes so much trouble
> and requires a careful re-consideration of upgrade schema, why didn't
> anyone mask it yet?
I didn't dare to.
Sebastian
On Fri, 03 Dec 2010 13:29:14 +0100
Sebastian Pipping wrote:
> Depending on how fast we can fix that, communicating status quo before
> that may still help reduce user frustration. Especially as we have an
> unmasked 2.7.1 in tree for a few days now.
Then the question would be -- if that version
On 12/03/10 13:23, Sebastian Pipping wrote:
> Good point. Still, as of now that's where to put USE_PYTHON.
^^^ referring to /etc/make.conf itself.
> I'm unsure if that's a reason strong enough to add it.
^^^ referring to the man page of 'make.conf'.
Sebastian
On 12/03/10 13:05, Michał Górny wrote:
> The first question that comes into my mind is -- why do we need
> to communicate that? I think that USE_PYTHON is a pretty specific
> variable which should be used only if specially required (i.e. to keep
> multiple Python versions ready for use).
>
> What
On 12/03/10 12:50, Fabian Groffen wrote:
> On 03-12-2010 11:35:14 +0100, Sebastian Pipping wrote:
>> to better communicate USE_PYTHON we could use:
>>
>> - a portage news entry
>
> why portage?
I'm speaking of GLEP 42. No idea if pkgcore or paludis support these.
That's why i said "portage".
h
On Fri, 03 Dec 2010 11:35:14 +0100
Sebastian Pipping wrote:
> to better communicate USE_PYTHON we could use:
The first question that comes into my mind is -- why do we need
to communicate that? I think that USE_PYTHON is a pretty specific
variable which should be used only if specially required
On 03-12-2010 11:35:14 +0100, Sebastian Pipping wrote:
> to better communicate USE_PYTHON we could use:
>
> - a portage news entry
why portage?
> - notifications from within ebuilds
>
> - a users guide counterpart of
>http://www.gentoo.org/proj/en/Python/developersguide.xml
>
> - menti
Hello,
to better communicate USE_PYTHON we could use:
- a portage news entry
- notifications from within ebuilds
- a users guide counterpart of
http://www.gentoo.org/proj/en/Python/developersguide.xml
- mentioning in 'man make.conf'
This is overdue and has some urgency.
Are you volu
