From: Bill Stewart <bstewart@iname.com>
To: cygwin@cygwin.com
Subject: Re: setup-x86_64.exe --quiet-mode issues using Management Tools
Date: Fri, 17 Apr 2020 07:41:37 -0600 [thread overview]
Message-ID: <CANV9t=SeR8X25_z9N=WJrY-x9gnQkDUunVPGi3zs_zL8xUNV7w@mail.gmail.com> (raw)
In-Reply-To: <f59e75f46c2b407fa37bcf74b3bc0232@BELBRU-EXMP101.eeas.europa.eu>
On Fri, Apr 17, 2020 at 1:01 AM KAVALAGIOS Panagiotis (EEAS-EXT) wrote:
> This is the way that we are pushing the packages currently to
> end users is through software managers with silent
> installation.
My point is that "silent" doesn't mean "no visible GUI." It generally
means "the installer doesn't block" (i.e., the installation completes
without user input).
For example, the popular Inno Setup install builder
(https://www.jrsoftware.org/isinfo.php) has a "/SILENT" command line
parameter, which (if the installer is designed correctly) causes the
created installer to install the package without user input. If run in
the user's session, a GUI is still visible; it just doesn't stop to
ask for any input. If you install using a software management tool,
this usually installs in a separate session, so it doesn't matter if
there's a GUI as long as no input is required.
Bill
next prev parent reply other threads:[~2020-04-17 13:42 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-15 14:33 Paul Isaacson
2020-04-15 15:02 ` KAVALAGIOS Panagiotis (EEAS-EXT)
2020-04-15 15:13 ` Bill Stewart
2020-04-16 8:25 ` KAVALAGIOS Panagiotis (EEAS-EXT)
2020-04-16 14:57 ` Bill Stewart
2020-04-17 7:01 ` KAVALAGIOS Panagiotis (EEAS-EXT)
2020-04-17 13:41 ` Bill Stewart [this message]
2020-04-21 8:08 ` KAVALAGIOS Panagiotis (EEAS-EXT)
2020-04-21 13:44 ` Bill Stewart
2020-04-21 13:56 ` KAVALAGIOS Panagiotis (EEAS-EXT)
2020-04-21 14:17 ` Bill Stewart
2020-04-21 20:32 ` Brian Inglis
2020-04-17 10:02 ` Andrey Repin
2020-04-18 14:58 ` Jon Turney
2020-04-21 8:14 ` KAVALAGIOS Panagiotis (EEAS-EXT)
2020-04-21 18:34 ` Brian Inglis
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='CANV9t=SeR8X25_z9N=WJrY-x9gnQkDUunVPGi3zs_zL8xUNV7w@mail.gmail.com' \
--to=bstewart@iname.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).