On Wed, 12 Jul 2017 16:40:11 +1000 "Sam Jorna (wraeth)" wrote: > If my concern in removing a package was whether it was a dependency, > it would make more sense to use --depclean in the first place. If I'm > using --unmerge, it's because I want the package unmerged regardless. But you can't remember what you installed or ate for dinner. What if you are removing something you need? > > Didn't you just say something about meaningful output vs noise? > > That is always outputted and ends up becoming what you are saying. > > Funny! > > > And your suggesting adding more noise to it... Funny, I know. No a warning that mentions the package not being removed is not noise. It is useful output, like the warnings that exist for other things now. I guess in your opinion this warning is noise to you. !!! 'sys-devel/gcc' is part of your system profile. !!! Unmerging it may be damaging to your system. It is YOUR comments that are funny, and going in a circular argument just to be argumentative and bringing nothing useful to the discussion. Which should be over now that bugs are filed.... > > Depclean the user is cleaning things they are not aware of. Unmerge > > the user is removing something directly. They may think they do not > > need it. > > No. > > '--depclean' is the user removing things they are not aware of. You literally just re-typed what I did above replacing cleaning with removing. Are you paying any attention? > '--depclean foo' is the user removing something they /are/ aware of > *if it's not a dependency*. That does not work the same. It will not remove a package from world. > '--unmerge foo' is the user explicitly removing something regardless > of whether it's a dependency. BUT they are warned now for things that are in a profile or set. Thus they should be warned if a dependency. Its simply, but clearly your having a hard time grasping. > Therefore, '--depclean foo' can be seen as a safe '--unmerge foo' > which, from what I understand, is what you're aiming for. No, as they are not the same. You cannot remember what you ate. Please stop trying to assume what I am after. Clearly we are very different. I know what I ate last night... > That's what the current warning to --unmerge says - removing packages > can break things, so please make sure this isn't a dependency and you > really want to remove this. They do not say anything about dependencies. It says the same message for everything. In some cases for system and set packages you get a warning. > How does replacing one warning with another warning that may or may > not be meaningful ("maybe it's a dep, maybe it isn't" as opposed to > "this can be dangerous, please make sure you know what you're doing") > make it any better? It is not replacing a warning. It is adding the same warning that exist in other situations in one it does not exists now, removing dependencies. Clearly you are having a hard time grasping this very simple concept. I am done, reply if you like, but this thread is serious noise now... -- William L. Thomson Jr.