| 1 |
TL;DR: It would be very nice if when I did: |
| 2 |
|
| 3 |
emerge --depclean -va |
| 4 |
|
| 5 |
That important packages like say, Postgres could go "hey, that's ... |
| 6 |
probably gonna break things, you haven't migrated, are you sure?" |
| 7 |
|
| 8 |
Seeing notices *after* removing postgres that my system is now broken is not too inspiring. |
| 9 |
|
| 10 |
In part, because you *CANT* perform a postgres migration after you remove the old version: |
| 11 |
|
| 12 |
1. You can't stop the old service, because the init script is gone. |
| 13 |
2. pg_upgrade doesn't work, because there's no binaries in the path passed to '-b' , as per: |
| 14 |
|
| 15 |
https://wiki.gentoo.org/wiki/PostgreSQL/QuickStart#Migrating_PostgreSQL |
| 16 |
|
| 17 |
This is especially annoying as: |
| 18 |
|
| 19 |
1. Its very easy to overlook one package in a 400 package depclean notice. ... |
| 20 |
2. Its not that postgres is no longer in world, but it got upgraded, |
| 21 |
and you all know what that means when *slots* are involved. |
| 22 |
|
| 23 |
Now imagine where I'd be if the version of postgres I just removed, I |
| 24 |
had no way of reinstalling. |
| 25 |
|
| 26 |
Related: |
| 27 |
|
| 28 |
It would also be nice if pkg_pretend ( or something like it ) happened *BEFORE* offering the [Y/N] |
| 29 |
prompt with `emerge -va `, not, as it currently does, wait until after |
| 30 |
you press "y" to execute those checks. |
| 31 |
|
| 32 |
Being able to generate notices, but not producing them until after you approve emerge is just daft. |
Archives