From: "KAVALAGIOS Panagiotis (EEAS-EXT)" <Panagiotis.KAVALAGIOS@ext.eeas.europa.eu>
To: Bill Stewart <bstewart@iname.com>,
"cygwin@cygwin.com" <cygwin@cygwin.com>
Subject: RE: setup-x86_64.exe --quiet-mode issues using Management Tools
Date: Fri, 17 Apr 2020 07:01:27 +0000 [thread overview]
Message-ID: <f59e75f46c2b407fa37bcf74b3bc0232@BELBRU-EXMP101.eeas.europa.eu> (raw)
In-Reply-To: <CANV9t=Rhphf2B4WL2g4chv=xzYgZDD7NkJjFW1OV4eyWvV_e7Q@mail.gmail.com>
> -----Original Message-----
> From: Cygwin <cygwin-bounces@cygwin.com> On Behalf Of Bill Stewart
>
> On Thu, Apr 16, 2020 at 2:25 AM KAVALAGIOS Panagiotis (EEAS-EXT) wrote:
>
> > Because the package can be sent to your machine when you are working
> > and we don't wish to disturb the users. 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.
I personally don't like stealth modifications to my system either. We are describing a different scenario and different needs. The users don't have admin rights in their machines and they have asked Cygwin to be included in the list of their development software. All the provided developer software so far includes silent installation apart from Cygwin, which you cannot call it 100% silent. We could also use a zip distribution for Cygwin, in fact that was our old deployment method, but half of the programs were able to run due to broken links. I know that there is a script to fix the links, but I would trust the setup itself better to avoid any possible issues on the users' machines.
This is the way that we are pushing the packages currently to end users is through software managers with silent installation. Of course, it would be far better to set up something like Windows Store, where the user can select Cygwin, launch its installation and have full control over it.
Kind regards,
Panos Kavalagios
Application Architect
CONSULIAT (under contract with the EEAS)
BA.BS.3.IS
_____________________________________
Office: EEAS B100 Floor 5 Area 048
Rue Belliard 100, 1000 Brussels
Phone: +32 2 584 6017
next prev parent reply other threads:[~2020-04-17 7:01 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) [this message]
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
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=f59e75f46c2b407fa37bcf74b3bc0232@BELBRU-EXMP101.eeas.europa.eu \
--to=panagiotis.kavalagios@ext.eeas.europa.eu \
--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).