From: Marco Atzeri <marco.atzeri@gmail.com>
To: cygwin@cygwin.com
Subject: Re: How to uninstall packages that were installed as dependency but are no longer required
Date: Tue, 30 Mar 2021 10:07:04 +0200 [thread overview]
Message-ID: <4c3c2dc4-6de3-9a3b-b39a-986e651275c3@gmail.com> (raw)
In-Reply-To: <20210330.145159.2203755649720422295.yasu@utahime.org>
On 30.03.2021 07:51, Yasuhiro Kimura wrote:
> Hello,
>
> If you repeat the update of installed Cygwin packages for a while,
> it's quite possible that there are some packages that were installed
> as dependency but are no longer required by any others.
>
> Then is there any way to detect and uninstall such ones?
>
> I expect such way as `apt autoremove` of Debian or `dnf autoremove` of
> Fedora.
>
> Best Regards.
>
> ---
> Yasuhiro Kimura
as currently we are not tracking between choosen packages
and installed by dependency, Cygwin is lacking such capabilities
the most likely candidates for removal are the different version
of the same libraries
$ cygcheck -cd | grep "^lib" | tee lib.txt
in my case I see
libvpx1 1.3.0-2
libvpx3 1.5.0-1
libvpx4 1.6.1-1
libvpx5 1.7.0-1
$ cygcheck-dep -q -n libvpx1 libvpx3 libvpx4 libvpx5
libvpx1: is needed for ( )
libvpx3: is needed for ( )
libvpx4: is needed for ( )
libvpx5: is needed for ( gstreamer1.0-plugins-good libvpx-devel )
Regards
Marco
next prev parent reply other threads:[~2021-03-30 8:07 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-30 5:51 Yasuhiro Kimura
2021-03-30 8:07 ` Marco Atzeri [this message]
2021-03-30 9:46 ` Yasuhiro Kimura
2021-03-30 17:18 ` Brian Inglis
2021-03-30 18:36 ` Marco Atzeri
2021-03-30 17:47 ` Achim Gratz
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4c3c2dc4-6de3-9a3b-b39a-986e651275c3@gmail.com \
--to=marco.atzeri@gmail.com \
--cc=cygwin@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).