| 1 |
2011/12/28 Zac Medico <zmedico@g.o>: |
| 2 |
> On 12/28/2011 05:12 AM, Francesco Riosa wrote: |
| 3 |
>> Disclaimer: this is just one idea that come at lunch, and sharing (in |
| 4 |
>> a short pause before my demanding daughter request me) here to not |
| 5 |
>> forget in the next busy days. |
| 6 |
>> |
| 7 |
>> Seem to me that append a time slice to the function, in the name or as |
| 8 |
>> a parent function that call the underling function can solve most of |
| 9 |
>> the versioning/deprecation problems |
| 10 |
>> |
| 11 |
>> how could it work: |
| 12 |
>> |
| 13 |
>> 1) package manager record the time it start an emerge "transaction", |
| 14 |
>> and share it via the environment with ebuilds and eclasses. The time |
| 15 |
>> could be faked by an argument via command line too. |
| 16 |
>> 2) the bash functions which are "versioned" this way chose the right one |
| 17 |
>> 3) package manager save the build time in the binpkg and in /var/db |
| 18 |
>> for unmergin and other purposes |
| 19 |
> |
| 20 |
> You're idea is irrelevant for binary packages and unmerge of installed |
| 21 |
> packages, since they make use of environment.bz2 which contains a |
| 22 |
> snapshot of the eclass functions / environment from build time. |
| 23 |
> |
| 24 |
The environment would contain all the versioned functions but it will |
| 25 |
also contain the timestamp of the original merge possibly solving the |
| 26 |
dilemma |
Archives