From: "Hans-Bernhard Bröker" <HBBroeker@t-online.de>
To: cygwin@cygwin.com
Subject: Re: update with apt-cyg ?
Date: Mon, 7 Sep 2020 18:26:52 +0200 [thread overview]
Message-ID: <fac60bff-db6f-8bdd-93b3-e705f94b98ce@t-online.de> (raw)
In-Reply-To: <20200906230010.GD19595@tik.uni-stuttgart.de>
Am 07.09.2020 um 01:00 schrieb Ulli Horlacher:
> cygstart /setup-x86_64.exe --quiet-mode
That approach is essentially guaranteed to fail you in frustrating ways,
for two reasons:
1) (Minor) You do not want to have setup itself, much less its work and
data directory, inside the cygwin installation. I.e. that should never
be '/' as the path for setup, as seen from any Cygwin shell.
2) (Major) Updating a running cygwin installation from the inside is
highly unlikely to work correctly. Most importantly there is almost no
chance for it to update the core DLLs, because those will already be in
use by the shell you're running this from, so they cannot be changed.
I.e. if you're in a situation where using "cygstart" makes any sense,
that's a situation setup cannot update the DLLs.
In a nutshell, and to paraphrase a certain Mr. Ford, you can have your
special non-interactive Cygwin setup script in any language you like, as
long as it's effectively a _Windows_ batch file. Updating the branch
you're currently sitting on does not work any better than sawing it through.
next prev parent reply other threads:[~2020-09-07 16:27 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-06 22:11 Ulli Horlacher
2020-09-06 22:27 ` Brian Inglis
2020-09-06 23:00 ` Ulli Horlacher
2020-09-07 1:11 ` Brian Inglis
2020-09-07 8:18 ` Ulli Horlacher
2020-09-08 7:45 ` Ulli Horlacher
2020-09-07 16:26 ` Hans-Bernhard Bröker [this message]
2020-09-07 5:40 ` Achim Gratz
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=fac60bff-db6f-8bdd-93b3-e705f94b98ce@t-online.de \
--to=hbbroeker@t-online.de \
--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).