| 1 |
On Mon, Jul 10, 2017 at 3:45 PM, William L. Thomson Jr. |
| 2 |
<wlt-ml@××××××.com> wrote: |
| 3 |
> On Mon, 10 Jul 2017 14:39:00 -0500 |
| 4 |
> Ben Kohler <bkohler@×××××.com> wrote: |
| 5 |
>> |
| 6 |
>> > You aren't taking the time to read your own emerge output. |
| 7 |
> |
| 8 |
> It always says that same generic message. If that is the case, then why |
| 9 |
> even have that option? |
| 10 |
|
| 11 |
The --unmerge option is there to let people shoot themselves in the |
| 12 |
feet if they know what they're doing. Anybody who uses it routinely |
| 13 |
is going to get burned by it sooner or later. It simply is not |
| 14 |
intended for day-to-day-use. I'd be all for renaming it to something |
| 15 |
like --unsafe-unmerge and getting rid of the short abbreviation. |
| 16 |
|
| 17 |
--depclean is the option people should be using day-to-day. |
| 18 |
|
| 19 |
There are cases with blocks that portage doesn't handle correctly |
| 20 |
where --unmerge is sometimes the simplest way around them. Fortunate |
| 21 |
this is rare these days. |
| 22 |
|
| 23 |
-- |
| 24 |
Rich |
Archives