1 |
2011/12/28 Zac Medico <zmedico@g.o>: |
2 |
> On 12/28/2011 05:12 AM, Francesco Riosa wrote: |
3 |
>> Seem to me that append a time slice to the function, in the name or as |
4 |
>> a parent function that call the underling function can solve most of |
5 |
>> the versioning/deprecation problems |
6 |
> |
7 |
> I've overheard Arfrever discussing a similar approach in funtoo's irc |
8 |
> channel, where the ebuild would set a variable prior to inherit if it |
9 |
> wants to use a specific eclass API. For the python eclass, he's planning |
10 |
> to have ebuilds set the PYTHON_ECLASS_API variable to use the new API. |
11 |
> When the variable is unset, the eclass will default to the older API. |
12 |
|
13 |
There is a fundamental difference, with "timeslices" it's not the |
14 |
ebuild that select the implementation but the point in time it's used, |
15 |
or the user forcing a fake time. From what I've read Artfever approach |
16 |
require changes in every ebuild and keeping old functions forever. On |
17 |
the other hand it may be risky to change the preferred interface from |
18 |
the eclass and not the ebuild. |
19 |
|
20 |
Thanks for reviewing, |
21 |
Francesco |