| 1 |
On 10/14/11 3:32 PM, Thomas Sachau wrote: |
| 2 |
> What do you expect the council to do? |
| 3 |
|
| 4 |
Say it's OK to make python.eclass not die on EAPI-4. At least my use |
| 5 |
case will not become broken by this. |
| 6 |
|
| 7 |
> Neither you nor the council can force anyone to do anything. |
| 8 |
|
| 9 |
Not really. It should always be possible to escalate painful issues like |
| 10 |
this. |
| 11 |
|
| 12 |
> The only thing you can do is to kindly ask about remaining issues and helping with solving them. And |
| 13 |
> i am sure, that everyone would like to see some help to understand and improve the python eclass. :-) |
| 14 |
|
| 15 |
Maybe we should start over. Seriously, I'm considering proposing some |
| 16 |
lightweight eclass for python-dependent packages that *works* |
Archives