public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Backwoods BC <completely.and.totally.trash@gmail.com>
Cc: "cygwin@cygwin.com" <cygwin@cygwin.com>
Subject: Re: Setup not working
Date: Tue, 28 Feb 2023 14:10:47 -0800	[thread overview]
Message-ID: <CAKwdsS_H+vDpBhoaCY7vo4KcYAA8o2Uj3RS7+e5Qbp9tDmryRA@mail.gmail.com> (raw)
In-Reply-To: <SI2PR04MB5821FFCA493280A37CDB9E58FEAC9@SI2PR04MB5821.apcprd04.prod.outlook.com>

On Tue, Feb 28, 2023 at 1:16 PM Brian Cowan via Cygwin
<cygwin@cygwin.com> wrote:
>
> There is a set of messages from last year or the year before talking about how the Cygwin setup program is compressed with "upx." When I had this issue, I had to download UPX on a Linuux host, copy the setup program to that host, and use upx to uncompress the executable. Why? Because my corporate-mandates security software blocked the UPX extractor from executing. If you have a Windows host where you can shut down the security software, that could work too.

I understand the desirability of compressing everything that travels
over the 'Net, but the days of there being any reason to keep an
executable compressed in order to save storage space have long passed
for the vast majority of users.

Therefore I suggest that a version of 'setup' be made available that
is compressed using one of the standard versions of 'ZIP' that Windows
File Explorer recognizes. People who have any issues getting setup to
run can download the ZIP version and use Windows File Explorer to
extract the uncompressed executable.

I suspect that even using a less than optimum ZIP process will still
be size-competitive with the self-extracting version because of not
having to include the overhead of the self-extractor.

  reply	other threads:[~2023-02-28 22:10 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-28 12:23 Albert Cornelius
2023-02-28 21:15 ` Brian Cowan
2023-02-28 22:10   ` Backwoods BC [this message]
2023-02-28 23:02     ` Backwoods BC

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=CAKwdsS_H+vDpBhoaCY7vo4KcYAA8o2Uj3RS7+e5Qbp9tDmryRA@mail.gmail.com \
    --to=completely.and.totally.trash@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).