From: "Buchbinder, Barry (NIH/NIAID) [E]" <BBuchbinder@niaid.nih.gov>
To: "cygwin@cygwin.com" <cygwin@cygwin.com>
Subject: RE: [ANNOUNCEMENT] New package: cygcheck-dep-1.0-1
Date: Sat, 09 Nov 2013 04:11:00 -0000 [thread overview]
Message-ID: <6CF2FC1279D0844C9357664DC5A08BA21B2CD9@MLBXV06.nih.gov> (raw)
Mikhail Usenko sent the following at Tuesday, November 05, 2013 3:55 AM
>Subject: New package - cygcheck-dep-1.0-1
>
>Version 1.0-1 of cygcheck-dep has been uploaded.
>
>cygcheck-dep is a bash script helping to show dependencies for installed
>Cygwin packages. It can be useful if you are trying some Cygwin's
>software and along the line you are installing and uninstalling some
>packages and want to keep your Cygwin's setup root directory clean of
>unused packages.
This is GREAT! Thanks for putting it together. I've cleaned out over
100M of cruft.
I'd be interested in getting a more detailed explanation of the
difference between -i and -I. The best I can tell from experiment, one
can uninstall all packages listed in an island by -i. But the listings
of -I cannot be uninstalled because package not in the list depend on
them. If that is correct, how does one use the information given by -I?
What can one do with it?
Thanks again,
- Barry
Disclaimer: Statements made herein are not made on behalf of NIAID.
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
next reply other threads:[~2013-11-09 4:11 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-09 4:11 Buchbinder, Barry (NIH/NIAID) [E] [this message]
2013-11-09 20:46 ` Mikhail Usenko
-- strict thread matches above, loose matches on Subject: below --
2013-11-06 5:18 Mikhail Usenko
2013-11-08 11:52 ` Adam Dinwoodie
2013-11-08 12:30 ` Mikhail Usenko
2013-11-08 13:25 ` Adam Dinwoodie
2013-11-08 13:40 ` Mikhail Usenko
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=6CF2FC1279D0844C9357664DC5A08BA21B2CD9@MLBXV06.nih.gov \
--to=bbuchbinder@niaid.nih.gov \
--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).