| 1 |
Peter Stuge <peter@×××××.se> wrote: |
| 2 |
> Martin Vaeth wrote: |
| 3 |
>> In fact, no matter whether you have static or dynamic deps, this is |
| 4 |
>> the only way to cleanly avoid the problems if you want to keep a |
| 5 |
>> package installed which is not maintained anymore: |
| 6 |
>> *You* must maintain it. There simply is no magic which can avoid this. |
| 7 |
> |
| 8 |
> It could be avoided if portage tree sync applied each tree change |
| 9 |
> locally rather than jump from old to new. [...] |
| 10 |
> The user's vardb could then automatically receive the last state of |
| 11 |
> the ebuild, before it was removed. |
| 12 |
|
| 13 |
It doesn't help reliably, either, since the last state of the ebuild, |
| 14 |
before it was removed, will be outdated at some point, too. |
| 15 |
It *is* necessary to adapt the dependencies to the current tree, |
| 16 |
and if no maintainer is there to do this correctly for that package, |
| 17 |
all empirics to "push" such changes will fail in some situations. |
Archives