Sadly, it's not done yet.
Please collect related bugs into this tracker:
https://bugs.gentoo.org/show_bug.cgi?id=347639
Sebastian
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
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
- mentioning in
В Срд, 01/12/2010 в 17:35 +0100, Diego Elio Pettenò пишет:
Il giorno mer, 01/12/2010 alle 17.02 +0300, Peter Volkov ha scritto:
Comments inside are better suited for this task - you see/update notes
as you edit ebuild.
How many ATs/arch maintainers will look _within_ the ebuild when
On Fri, 03 Dec 2010 11:35:14 +0100
Sebastian Pipping sp...@gentoo.org 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
Il giorno ven, 03/12/2010 alle 14.50 +0300, Peter Volkov ha scritto:
Same logic applies for metadata.xml. Personally doing AT work I always
review ebuild. At the same time I never opened metadata.xml, so I
don't
see your point.
Have you read my post? I said to make _repoman_ spew the
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.
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 needs
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 Fri, 03 Dec 2010 13:29:14 +0100
Sebastian Pipping sp...@gentoo.org 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 --
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, Dec 3, 2010 at 4:35 AM, Sebastian Pipping sp...@gentoo.org wrote:
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
-
On 12/03/2010 07:05 AM, Michał Górny wrote:
On Fri, 03 Dec 2010 11:35:14 +0100
Sebastian Pipping sp...@gentoo.org 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
Hello list,
please find attached a couple of patches that have been worked on in the
gnome overlay for both gnome 2.32 release (gsettings integration),
better EAPI=3 support - although I believe work is not complete, prefix
feedback would be most welcome - and various cleanups that are long
On Fri, Dec 3, 2010 at 21:25, Gilles Dartiguelongue e...@gentoo.org wrote:
Please also find in these patches a proposal of a waf-utils eclass in
order to put waf related build management into an eclass. There is a
couple of ebuilds already in tree all doing things on their own and I
had a
Le vendredi 03 décembre 2010 à 21:54 +0100, Cyprien Nicolas a écrit :
On Fri, Dec 3, 2010 at 21:25, Gilles Dartiguelongue e...@gentoo.org wrote:
Please also find in these patches a proposal of a waf-utils eclass in
order to put waf related build management into an eclass. There is a
couple
Hello!
Current situation
=
Without specifying USE_PYTHON in /etc/make.conf ebuilds based on the
python eclass will install packages for no more ABIs than the two active
versions on the 2.x and 3.x lines. To give an example: with Python 2.6,
2.7 and 3.1 installed and 2.7 set as
Hello!
In the mean time I have sent the attached patch to people involved with
building Gentoo stages. Before further taking action on/with that patch
I am waiting for their response.
I am now posting it here in order to let you know about this change in
status and to give potentially
On Fri, 03 Dec 2010 23:25:21 +0100
Gilles Dartiguelongue e...@gentoo.org wrote:
Le vendredi 03 décembre 2010 à 21:54 +0100, Cyprien Nicolas a écrit :
On Fri, Dec 3, 2010 at 21:25, Gilles Dartiguelongue e...@gentoo.org wrote:
Please also find in these patches a proposal of a waf-utils eclass
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi.
On 03-12-2010 23:34, Sebastian Pipping wrote:
Hello!
In the mean time I have sent the attached patch to people involved with
building Gentoo stages. Before further taking action on/with that patch
I am waiting for their response.
I've
Il giorno ven, 03/12/2010 alle 19.46 -0600, Ryan Hill ha scritto:
This has come up enough times that we should write some common code.
Or resume the idea to simply provide a separate variable for
number-of-jobs rather than relying purely on MAKEOPTS.
--
Diego Elio Pettenò — “Flameeyes”
On Sat, 04 Dec 2010 03:29:45 +0100
Diego Elio Pettenò flamee...@gmail.com wrote:
Il giorno ven, 03/12/2010 alle 19.46 -0600, Ryan Hill ha scritto:
This has come up enough times that we should write some common code.
Or resume the idea to simply provide a separate variable for
В Птн, 03/12/2010 в 13:12 +0100, Diego Elio Pettenò пишет:
Il giorno ven, 03/12/2010 alle 14.50 +0300, Peter Volkov ha scritto:
Same logic applies for metadata.xml. Personally doing AT work I always
review ebuild. At the same time I never opened metadata.xml, so I
don't see your point.
23 matches
Mail list logo
