| 1 |
>>>>> On Tue, 18 Dec 2007, Ciaran McCreesh wrote: |
| 2 |
|
| 3 |
> | Possibility to extend the behaviour of inherit and add new global |
| 4 |
> | scope functions (as a result of not sourcing ebuilds with |
| 5 |
> | unsupported EAPI). |
| 6 |
|
| 7 |
It seems to me that this will inconvenience the users, in order to |
| 8 |
solve a technical problem of the package manager. |
| 9 |
|
| 10 |
Is this really the right way to go? |
| 11 |
|
| 12 |
>> Making the file extension variable by adding "-<EAPI>" to it would, |
| 13 |
>> in my opinion, make the portage tree a bit less clean and not as |
| 14 |
>> elegant. |
| 15 |
|
| 16 |
+1 |
| 17 |
|
| 18 |
>> Wouldn't software (like editors determining file type by looking at |
| 19 |
>> what is after the ".") also need to be reworked to recognize a |
| 20 |
>> variable string after "-" at the end? |
| 21 |
|
| 22 |
> Yep, but that's not very difficult. And as a side effect, editors |
| 23 |
> could then provide EAPI aware highlighting. |
| 24 |
|
| 25 |
They can also do this if EAPI is set within the file. |
| 26 |
|
| 27 |
Ulrich |
| 28 |
-- |
| 29 |
gentoo-dev@g.o mailing list |
Archives