From: Christopher Faylor <cgf-use-the-mailinglist-please@cygwin.com>
To: cygwin-apps@cygwin.com
Subject: Re: [ITP] cygcheck-leaves - a script to list installed packages not required by any
Date: Mon, 04 Nov 2013 18:28:00 -0000 [thread overview]
Message-ID: <20131104182807.GD5526@ednor.casa.cgf.cx> (raw)
In-Reply-To: <20131104175403.GA30316@calimero.vinschen.de>
On Mon, Nov 04, 2013 at 06:54:03PM +0100, Corinna Vinschen wrote:
>On Nov 4 12:45, Christopher Faylor wrote:
>> On Mon, Nov 04, 2013 at 01:39:25PM +0100, Corinna Vinschen wrote:
>> >On Oct 31 12:34, Mikhail Usenko wrote:
>> >> Thanks for the comment. I've forgotten to test the script on 32-bit Windows.
>> >> Now it uses a bash-specific variable to determine the CPU type and should work OK.
>> >>
>> >> Also after some time of using I've completely rewritten it having added new
>> >> functionality and renamed it to 'cygcheck-dep'.
>> >>
>> >> setup.hint:
>> >> -----------
>> >> category: Utils
>> >> requires: bash coreutils sed wget bzip2
>> >> sdesc: "Show information on dependencies for installed Cygwin packages"
>> >> -----------
>> >
>> >Neat. I toyed a bit with your script and I like it. This could
>> >come in handy to isolate installation problems. I uploaded the
>> >package. Please send an announcement along the lines of the
>> >existing announcements to the cygwin-announce list.
>>
>> This needs to be in cygwin-pkg-maint
>
>Did so while uploading.
Ah, I was looking for cygcheck-leaves. Nevermind.
cgf
next prev parent reply other threads:[~2013-11-04 18:28 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-31 8:34 Mikhail Usenko
2013-11-04 12:39 ` Corinna Vinschen
2013-11-04 17:45 ` Christopher Faylor
2013-11-04 17:54 ` Corinna Vinschen
2013-11-04 18:28 ` Christopher Faylor [this message]
-- strict thread matches above, loose matches on Subject: below --
2013-10-05 19:03 Mikhail Usenko
2013-10-18 8:07 ` Corinna Vinschen
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=20131104182807.GD5526@ednor.casa.cgf.cx \
--to=cgf-use-the-mailinglist-please@cygwin.com \
--cc=cygwin-apps@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).