1 |
Martin Vaeth wrote: |
2 |
> The user has to put a corrected ebuild into his overlay and must |
3 |
> reemerge the package (currently, the latter could be skipped with |
4 |
> dynamic deps). |
5 |
> In fact, no matter whether you have static or dynamic deps, this is |
6 |
> the only way to cleanly avoid the problems if you want to keep a |
7 |
> package installed which is not maintained anymore: |
8 |
> *You* must maintain it. There simply is no magic which can avoid this. |
9 |
|
10 |
It could be avoided if portage tree sync applied each tree change |
11 |
locally rather than jump from old to new. There was a delta idea |
12 |
discussed a year or so ago in connection with some git discussions. |
13 |
|
14 |
The user's vardb could then automatically receive the last state of |
15 |
the ebuild, before it was removed. |
16 |
|
17 |
That's no small change though. |
18 |
|
19 |
|
20 |
//Peter |