| 1 |
On Mon, Jul 28, 2014 at 2:50 PM, Martin Vaeth <martin@×××××.de> wrote: |
| 2 |
> |
| 3 |
> In both cases of 6., the user is not even aware that he uses |
| 4 |
> long obsolete packages unless portage prints a big fat warning |
| 5 |
> for orphaned packages (which currently is not the case. |
| 6 |
> Well, at least eix -t will be print a message.) |
| 7 |
> |
| 8 |
|
| 9 |
This is really the crux of these sorts of issues. It doesn't matter |
| 10 |
if dependencies are static or dynamic - if you hang onto orphans then |
| 11 |
you're going to have cruft in your vdb which is going to lead to |
| 12 |
blockers of some kind eventually. |
| 13 |
|
| 14 |
Portage should probably generate a warning when there are orphan packages. |
| 15 |
|
| 16 |
The same is true if you keep cruft in a local overlay or such. We can |
| 17 |
have all the pretty virtuals/etc we want, but if users stick |
| 18 |
hard-coded obsolete package names in their overlays or have them in |
| 19 |
their vdb, then they're going to get blockers. Though, we could do a |
| 20 |
better job with the error messages even when that happens... |
| 21 |
|
| 22 |
Rich |
Archives