public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Steven Penny <svnpenn@gmail.com>
To: cygwin@cygwin.com
Cc: 10walls@gmail.com, yselkowitz@cygwin.com
Subject: Re: [ANNOUNCEMENT] Updated: binutils-2.34+1git.de9c1b7cfe-1 (x86/x86_64)
Date: Wed, 18 Mar 2020 19:25:29 -0500	[thread overview]
Message-ID: <CAAXzdLWXD09FkgTmo2FY0kH4NmyYeAu9gnQaarkwYxKjYjOx3Q@mail.gmail.com> (raw)

> The following packages have been uploaded to the Cygwin distribution:
>
> * binutils-2.34+1git.de9c1b7cfe
>
> This release should fix libtool shared library builds on 32bit Cygwin.

Below are the current "non Base" dependencies (and transitive dependencies) of
current "python3". As can be seen, "binutils" is now larger than all the other
dependencies combined.

Can we please, please address whatever exploded "binutils" size? Or perhaps once
and for all remove "binutils" as a dependency for "python3"? "binutils" is not
a runtime requirement for Python, only in the case where someone is utilizing
"ctypes", which one could argue is not a large enough percentage of users to
justify this.

25,016,180 binutils
     4,132 libcom_err2
    92,524 libcrypt2
    55,100 libexpat1
     3,964 libgdbm_compat4
    21,896 libgdbm6
   102,828 libgssapi_krb5_2
    73,344 libk5crypto3
   236,076 libkrb5_3
    14,424 libkrb5support0
    40,052 libnsl2
    19,432 libpkgconf3
   470,540 libsqlite3_0
    68,708 libtirpc3
     7,004 libtirpc-common
    16,848 libuuid-devel
    25,124 pkgconf
     5,972 pkg-config
       316 python3
 5,750,152 python36
 1,269,060 python-pip-wheel
   467,804 python-setuptools-wheel

             reply	other threads:[~2020-03-19  0:25 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-19  0:25 Steven Penny [this message]
2020-03-19  5:25 ` Marco Atzeri
2020-03-19 23:18   ` Brian Inglis
2020-03-20 19:24     ` Hans-Bernhard Bröker
2020-03-21  4:55       ` Marco Atzeri
2020-03-21  6:40         ` Marco Atzeri
2020-03-22 20:19           ` Yaakov Selkowitz
2020-03-22 23:05             ` Marco Atzeri
2020-04-01 11:33 ` Jan Nijtmans
2020-04-06 10:07   ` Problem in mingw64-i686-binutils [Was: Updated: binutils-2.34+1git.de9c1b7cfe-1 (x86/x86_64)] Jan Nijtmans
2020-04-06 23:55     ` JonY
2020-04-07  0:57       ` Yaakov Selkowitz
2020-04-07 10:29         ` JonY
  -- strict thread matches above, loose matches on Subject: below --
2020-03-15 10:33 [ANNOUNCEMENT] Updated: binutils-2.34+1git.de9c1b7cfe-1 (x86/x86_64) JonY via Cygwin-announce

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=CAAXzdLWXD09FkgTmo2FY0kH4NmyYeAu9gnQaarkwYxKjYjOx3Q@mail.gmail.com \
    --to=svnpenn@gmail.com \
    --cc=10walls@gmail.com \
    --cc=cygwin@cygwin.com \
    --cc=yselkowitz@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).