| 1 |
On 12/03/10 12:50, Fabian Groffen wrote: |
| 2 |
> On 03-12-2010 11:35:14 +0100, Sebastian Pipping wrote: |
| 3 |
>> to better communicate USE_PYTHON we could use: |
| 4 |
>> |
| 5 |
>> - a portage news entry |
| 6 |
> |
| 7 |
> why portage? |
| 8 |
|
| 9 |
I'm speaking of GLEP 42. No idea if pkgcore or paludis support these. |
| 10 |
That's why i said "portage". |
| 11 |
|
| 12 |
http://www.gentoo.org/proj/en/glep/glep-0042.html |
| 13 |
|
| 14 |
|
| 15 |
>> - notifications from within ebuilds |
| 16 |
>> |
| 17 |
>> - a users guide counterpart of |
| 18 |
>> http://www.gentoo.org/proj/en/Python/developersguide.xml |
| 19 |
>> |
| 20 |
>> - mentioning in 'man make.conf' |
| 21 |
> |
| 22 |
> why? make.conf is for "custom settings for Portage". |
| 23 |
|
| 24 |
Good point. Still, as of now that's where to put USE_PYTHON. |
| 25 |
I'm unsure if that's a reason strong enough to add it. |
| 26 |
|
| 27 |
|
| 28 |
>> As it involves a GLEP and GuideXML maybe that's perfect for involving |
| 29 |
>> people being recruited at the moment. |
| 30 |
> |
| 31 |
> Why a GLEP? |
| 32 |
|
| 33 |
It involves usage of a GLEP, not creating a new one. |
| 34 |
Sorry, if I did not put this clearly. |
| 35 |
|
| 36 |
Best, |
| 37 |
|
| 38 |
|
| 39 |
|
| 40 |
Sebastian |
Archives