| 1 |
On Wed, 12 Jul 2017 15:49:14 +1000 |
| 2 |
"Sam Jorna (wraeth)" <wraeth@g.o> wrote: |
| 3 |
> |
| 4 |
> I have trouble remembering what I ate for dinner last night, let alone |
| 5 |
> what I may or may not have merged a week, month or year ago, or what |
| 6 |
> options I used when merging it. |
| 7 |
|
| 8 |
And if you used --oneshot, it is also saying you are not maintaining |
| 9 |
your system or ever running --depclean. Since anything you installed |
| 10 |
via --oneshot would be removed with --depclean. |
| 11 |
|
| 12 |
> > What harm does a warning do? |
| 13 |
> |
| 14 |
> Depends on the user, which can't really be avoided, but means that |
| 15 |
> warnings should be clear and meaningful, otherwise they become |
| 16 |
> background noise. |
| 17 |
|
| 18 |
The example in the bug is as clear is it can get. |
| 19 |
|
| 20 |
!!! 'sys-devel/gcc' is a dependency of another package on your system |
| 21 |
or |
| 22 |
!!! 'sys-devel/gcc' is a package not found in system profile or world |
| 23 |
or |
| 24 |
!!! 'sys-devel/gcc' may not have been installed by you |
| 25 |
or |
| 26 |
some other message.... |
| 27 |
|
| 28 |
> Such as: |
| 29 |
> |
| 30 |
> emerge --unmerge dev-python/keyring |
| 31 |
> * This action can remove important packages! In order to be safer, |
| 32 |
> use |
| 33 |
> * `emerge -pv --depclean <atom>` to check for reverse dependencies |
| 34 |
> before |
| 35 |
> * removing packages. |
| 36 |
|
| 37 |
Didn't you just say something about meaningful output vs noise? That is |
| 38 |
always outputted and ends up becoming what you are saying. Funny! |
| 39 |
|
| 40 |
> >> or may have been installed as an orphan but is now a |
| 41 |
> >> dependency. |
| 42 |
> > |
| 43 |
> > Now being a dependency the warning would be valid. |
| 44 |
> |
| 45 |
> "Sometimes being accurate" is not the most noble of goals. |
| 46 |
|
| 47 |
What? |
| 48 |
|
| 49 |
> So the idea is to duplicate the functionality of '--depclean |
| 50 |
> <package> |
| 51 |
|
| 52 |
NO!!! |
| 53 |
|
| 54 |
emerge --depclean gcc |
| 55 |
|
| 56 |
is not the same as |
| 57 |
|
| 58 |
emerge --umerge gcc |
| 59 |
|
| 60 |
Depclean the user is cleaning things they are not aware of. Unmerge the |
| 61 |
user is removing something directly. They may think they do not need it. |
| 62 |
|
| 63 |
>' without actually checking to see if the package is a |
| 64 |
> dependency, |
| 65 |
|
| 66 |
Word it how ever. If the user did not install, they should be warned on |
| 67 |
removal of a package they did not install. |
| 68 |
|
| 69 |
> only whether it is listed in a set; or to check if it's a |
| 70 |
> dependency of /something/ and, if so, redirect the user to the |
| 71 |
> command they should be using anyway? |
| 72 |
|
| 73 |
You mean like emerge --unmerge does already that you pointed out |
| 74 |
above. After mentioning useful messages vs noise. Again funny! |
| 75 |
|
| 76 |
-- |
| 77 |
William L. Thomson Jr. |
Archives