On Mon, 10 Jul 2017 15:07:37 -0400 Brian Evans <grkni...@gentoo.org> wrote:
> On 7/10/2017 2:59 PM, William L. Thomson Jr. wrote:
> > On Mon, 10 Jul 2017 00:43:11 -0400
> > "William L. Thomson Jr." <wlt...@o-sinc.com> wrote:
> > I think portage should also warn on removing packages that came in
> > from another. If you are removing any dependency of another package.
> >
> >
>
> Portage will refuse to remove a package if it is a dependency, but you
> have to change the invocation to be 'emerge -avc <package>'.
>
> Then it will be very verbose if something needs said package.
Nope, go try yourself. Remove any dep of another package that is not a
system package. You will not get any warnings but the generic one. It
does not know these are a dep and should not be removed. It is not
saying anything about that.
These are brought in by 2 packages I have installed,
dev-java/tomcat-server and java-virtuals/servlet-api
# emerge -pC tomcat-servlet-api
* This action can remove important packages! In order to be safer, use
* `emerge -pv --depclean <atom>` to check for reverse dependencies
before
* removing packages.
>>> These are the packages that would be unmerged:
dev-java/tomcat-servlet-api
selected: 6.0.53 7.0.77 9.0.0_alpha22
protected: none
omitted: none
All selected packages: =dev-java/tomcat-servlet-api-6.0.53
=dev-java/tomcat-servlet-api-7.0.77
=dev-java/tomcat-servlet-api-9.0.0_alpha22
>>> 'Selected' packages are slated for removal.
>>> 'Protected' and 'omitted' packages will not be removed.
Which I just had as a result of doing that previously
!!! ERROR: No provider is available for servlet-api-2.5
Please check your environment.
!!! ERROR: No provider is available for servlet-api-3.0
Please check your environment.
--
William L. Thomson Jr.
pgpOTZDJEqJTG.pgp
Description: OpenPGP digital signature
