From: Brian Inglis <Brian.Inglis@Shaw.ca>
To: cygwin@cygwin.com
Subject: Re: cygwin does not run quietly if --quiet-mode given on commandline
Date: Thu, 30 Mar 2023 10:24:20 -0600 [thread overview]
Message-ID: <e9470a95-cdab-a5b3-cd35-b493adb85079@Shaw.ca> (raw)
In-Reply-To: <28016a52-6354-3513-8253-20c8e3cef1e7@bfs.de>
On 2023-03-30 08:23, Thomas Schweikle via Cygwin wrote:
> starting cygwin setup-x86_64.exe with parameters:
> setup-x86_64.exe ^
> --verbose ^
> --delete-orphans ^
> --local-package-dir "C:\WINDOWS\ccmcache\4r\installdata" ^
> --no-desktop ^
> --proxy "<proxy-host:proxy-port>" ^
> --root "C:\cygwin" ^
> --upgrade-also ^
> --quiet-mode ^
> --wait
> It does not matter if "--quiet-mode" is given or not: in all cases cygwin setup
> opens a window showing setup progress and the real bad thing: allows the user on
> whom desktop the window is shown to stop the upgrade!
> I need a really unattended upgrade with some log written what setup had done.
> And is it a bug? As far as I could find "--quiet-mode" means no window, no
> messages at all - am I wrong and all those interpreting it the same way?
Might want to try dropping:
> --verbose ^
> --delete-orphans ^
> --wait
and add -O|--only-site -s|--site /url/ -s|--site ... closest/fastest mirrors as
long as it is/they are active in https://cygwin.com/mirrors.lst - probably best
if they are different protocols at the same mirror (handles cert expiry) and/or
reliable backup.
--
Take care. Thanks, Brian Inglis Calgary, Alberta, Canada
La perfection est atteinte Perfection is achieved
non pas lorsqu'il n'y a plus rien à ajouter not when there is no more to add
mais lorsqu'il n'y a plus rien à retirer but when there is no more to cut
-- Antoine de Saint-Exupéry
next prev parent reply other threads:[~2023-03-30 16:24 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-30 14:23 Thomas Schweikle
2023-03-30 16:24 ` Brian Inglis [this message]
2023-03-30 19:00 ` Thomas Schweikle
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=e9470a95-cdab-a5b3-cd35-b493adb85079@Shaw.ca \
--to=brian.inglis@shaw.ca \
--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).