From: Adam Dinwoodie <adam@dinwoodie.org>
To: "cygwin@cygwin.com" <cygwin@cygwin.com>
Cc: "Fuchs, Thorsten" <Thorsten.Fuchs@brose.com>
Subject: Re: No cancel mode for setup.exe
Date: Tue, 30 Nov 2021 12:20:37 +0000 [thread overview]
Message-ID: <CA+kUOakzANiU74TY=PQuDCrSu0yA08_tQqRO-Q+8XUnJtE+YHA@mail.gmail.com> (raw)
In-Reply-To: <DB8PR08MB40112FA11CC8E0740925C3B594669@DB8PR08MB4011.eurprd08.prod.outlook.com>
On Mon, 29 Nov 2021 at 15:24, Fuchs, Thorsten via Cygwin
<cygwin@cygwin.com> wrote:
> We are using the setup-x86_64.exe within our deployment system to install Cygwin at the developer workstations. The setup run is triggered automatically and all developer workstation going to be install identically. However, when the setup window is open and the install is in progress it is possible for the user to cancel it.
> Sometimes developers interrupt the process. Would be good if this can be avoided. Is there an command line option for setup-x86_64.exe to prohibit the cancelation or can something like that implemented?
This is function that doesn't currently exist, and while you could
probably disable the "Cancel" button, I don't think you'd be able to
reliably prevent a determined user from breaking out of the
installation process.
If you're interested in adding it this function, the source code for
the installer is accessible via
https://sourceware.org/cygwin-apps/setup.html. Cygwin is an open
source project; two of the common phrases on this list are "Someone
has to do it" () and "Patches thoughtfully considered". If you or your
employer aren't willing to write and submit the patches yourselves, if
you ask on this list you might find other developers willing to do
work on a contracting basis. You *might* get lucky and find someone
who will do it without pay, but I don't imagine this is the sort of
thing that anyone would be interested in doing for free.
HTH
Adam
next prev parent reply other threads:[~2021-11-30 12:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-29 15:23 Fuchs, Thorsten
2021-11-30 12:20 ` Adam Dinwoodie [this message]
2021-11-30 15:12 ` 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='CA+kUOakzANiU74TY=PQuDCrSu0yA08_tQqRO-Q+8XUnJtE+YHA@mail.gmail.com' \
--to=adam@dinwoodie.org \
--cc=Thorsten.Fuchs@brose.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).