public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Achim Gratz <Stromeko@NexGo.DE>
To: cygwin@cygwin.com
Subject: Re: Updated: setup.exe (Release 2.872)
Date: Tue, 13 Oct 2015 07:13:00 -0000	[thread overview]
Message-ID: <loom.20151013T084949-103@post.gmane.org> (raw)
In-Reply-To: <000501d10580$62e56a90$28b03fb0$@bonhard.uklinux.net>

Fergus <fergus <at> bonhard.uklinux.net> writes:
> I always install / update Cygwin from a x86/release/ directory located on my
> hard drive, and kept up to date.

So you use a local mirror?

> The new setup-x86.exe requires setup.ini.sig located in x86/ as well as
> setup.ini.
> Easy to manage, but is this additional requirement intentional?

Yes, if the directory you install from looks like a local mirror then
setup.ini should be found in the correct place and the signature should
check OK to ensure the file and everything you install later on, through the
SHA-512 checksums, hasn't been tampered with.  You can skip the signature
check with '-X / --no-verify', but unless you modify setup.ini I suggest to
just download the .sig file as well.  You might want to add '-m /
--mirror-mode' as well to ensure that setup doesn't switch into ad-hoc
install mode inadvertently.

If you want to use the ad-hoc install method w/o setup.ini (which requires
that setup searches the disk for package files, which is quite inefficient
for a full install), then rename the directory so it doesn't look like a
local mirror or start setup from a deeper level in the directory tree.


Regards,
Achim.


--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

  reply	other threads:[~2015-10-13  7:13 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-13  6:28 Fergus
2015-10-13  7:13 ` Achim Gratz [this message]
2015-10-18 18:33 ` 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=loom.20151013T084949-103@post.gmane.org \
    --to=stromeko@nexgo.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).