public inbox for cygwin-apps@cygwin.com
 help / color / mirror / Atom feed
From: Corinna Vinschen <corinna-cygwin@cygwin.com>
To: cygwin-apps@cygwin.com
Subject: Re: [ITP] cygcheck-leaves - a script to list installed packages not required by any
Date: Fri, 18 Oct 2013 08:07:00 -0000	[thread overview]
Message-ID: <20131018080720.GE23477@calimero.vinschen.de> (raw)
In-Reply-To: <5d065c8706cc3765b4ddba203c9b006a0f4cd208@mail.qip.ru>

[-- Attachment #1: Type: text/plain, Size: 2421 bytes --]

Hi Mikhail,

On Oct  5 23:03, Mikhail wrote:
> As soon as setup.exe hasn't got an option to uninstall a package along with its requirements which have become unused after uninstalling that package, and cygcheck utility also does not provide any information on package dependencies I have written a bash script to list installed Cygwin packages which are not required by any other installed packages (that is package leaves in the dependency tree).
> 
> Developers usually have many lib*-devel packages installed on their system, these packages and others are required only as build dependencies so I think this script will be useful primarily for ordinary users who experiment with software and want to keep their Cygwin installation clean. They will be able to check the list of installed packages for unneeded ones.
> 
> I would like to propose this script as a Cygwin package if you appreciate it. The name of the script can be changed according to Cygwin policy on the use of cyg- prefix for such a type of programs.
> 
> setup.hint:
> 
> category: Utils
> requires: bash coreutils sed wget bzip2
> sdesc: "List installed Cygwin packages which are not required by any other installed packages"

I like the idea, but your script doesn't work as expected:

$ ./cygcheck-leaves -v
--2013-10-18 09:54:19--  ftp://sourceware.org/pub/cygwin/x86_64-cygwin/setup.bz2
           => `/var/cache/cygcheck-leaves/x86_64-cygwin/.listing'
Resolving sourceware.org... 209.132.180.131
Connecting to sourceware.org|209.132.180.131|:21... connected.
Logging in as anonymous ... Logged in!
==> SYST ... done.    ==> PWD ... done.
==> TYPE I ... done.  ==> CWD (1) /pub/cygwin/x86_64-cygwin ...
No such directory `pub/cygwin/x86_64-cygwin'.

That should be x86_64, not x86_64-cygwin.  The reason is that HOSTTYPE
has been already set by tcsh, and tcsh has another idea of that
variable than bash.

There's also the problem that, even under bash, the HOSTTYPE for 32 bit
is i686, but the directory on sourceware is called x86.

I guess what you want is something along the lines of

  targetdir=$(uname -m)
  [ "${targetdir}" = "i686" ] && machine='x86'
  setup_bz2_url="ftp://sourceware.org/pub/cygwin/${targetdir}/setup.bz2"


Thanks,
Corinna

-- 
Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Maintainer                 cygwin AT cygwin DOT com
Red Hat

[-- Attachment #2: Type: application/pgp-signature, Size: 836 bytes --]

  reply	other threads:[~2013-10-18  8:07 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-05 19:03 Mikhail Usenko
2013-10-18  8:07 ` Corinna Vinschen [this message]
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

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=20131018080720.GE23477@calimero.vinschen.de \
    --to=corinna-cygwin@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).