From: Andrey Repin <anrdaemon@yandex.ru>
To: Bill Stewart <bstewart@iname.com>, cygwin@cygwin.com
Subject: Re: setup-x86_64.exe --quiet-mode issues using Management Tools
Date: Fri, 17 Apr 2020 13:02:59 +0300 [thread overview]
Message-ID: <1439408168.20200417130259@yandex.ru> (raw)
In-Reply-To: <CANV9t=Rhphf2B4WL2g4chv=xzYgZDD7NkJjFW1OV4eyWvV_e7Q@mail.gmail.com>
Greetings, Bill Stewart!
> On Thu, Apr 16, 2020 at 2:25 AM KAVALAGIOS Panagiotis (EEAS-EXT) wrote:
>> > From: Cygwin On Behalf Of Bill Stewart
>> > On Wed, Apr 15, 2020 at 9:03 AM KAVALAGIOS Panagiotis (EEAS-EXT) wrote:
>> >
>> > > I have already requested a feature to totally remove any GUI from
>> > > silent installation:
>> > >
>> > > https://www.mail-archive.com/cygwin@cygwin.com/msg162887.html
>> >
>> > Just curious: Why does it matter whether a GUI appears or not, as long as it
>> > doesn't block (stop for input)?
>>
>> Because the package can be sent to your machine when you are working
>> and we don't wish to disturb the users.
Since you install it as administrator, install it as a system application.
This way it is easier to integrate it with users' workflow AND your
infrastructure, and you could more easily control this integration as well as
protect it from accidental changes.
>> Everything is performed in the
>> background. Annoying popups are not welcomed. Silent installation is
>> supposed to be silent without any horns shouting in the foreground.
> If the install doesn't occur as the current user (and it shouldn't),
> the installation won't be visible anyway.
> I for one am against installers that run completely invisibly.
The problem is not the interface itself, the problem is that a user who see
a random program popped up on their screen could interrupt the installation,
intentionally or not.
--
With best regards,
Andrey Repin
Friday, April 17, 2020 12:59:54
Sorry for my terrible english...
next prev parent reply other threads:[~2020-04-17 10:05 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
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 [this message]
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=1439408168.20200417130259@yandex.ru \
--to=anrdaemon@yandex.ru \
--cc=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).