public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Achim Gratz <Stromeko@nexgo.de>
To: cygwin@cygwin.com
Subject: Re: Cygwin Setup - Choose Best Mirror Automatically for Automated / Silent Installs
Date: Sat, 19 Nov 2016 00:15:00 -0000	[thread overview]
Message-ID: <871sy85yv3.fsf@Rainer.invalid> (raw)
In-Reply-To: <CAK0ZC5VuH+V31J5JBctEzoB3=sJWurmqcHRw3pBtEO-A1Xf6Uw@mail.gmail.com>	(OwN-3m-All's message of "Thu, 17 Nov 2016 21:06:05 -0700")

OwN-3m-All writes:
> That's really not a good solution.  I don't have control over the
> mirrors or would know why one isn't working.

The only way to thoroughly solve that problem is to provide your own
mirror (which by definition you have control over).

> I think a new command-line argument should be added that makes Cygwin
> setup pick one of the mirrors it knows is good from the list it
> downloads.

That really doesn't work without quite a bit of server-side
infrastructure that currently simply isn't in place.  Personally I'd
prefer MirrorBrain, but SHTDI and all that.

> A command-line argument is the way to go, but a text file with a list
> of known good mirrors that could be downloaded and parsed by a script
> would also be of great help.  Cygwin already checks the status of its
> mirros as far as I know.

If you think you know which mirror is currently working (best) for you,
that file can easily be downloaded.


Regards,
Achim.
-- 
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+

SD adaptation for Waldorf Blofeld V1.15B11:
http://Synth.Stromeko.net/Downloads.html#WaldorfSDada

--
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

  parent reply	other threads:[~2016-11-18 20:15 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-18  3:20 OwN-3m-All
2016-11-18  3:41 ` Andrey Repin
2016-11-18  6:04   ` OwN-3m-All
2016-11-18  6:11     ` Brian Inglis
2016-11-18  6:18       ` OwN-3m-All
2016-11-18  6:20         ` OwN-3m-All
2016-11-18  7:32           ` Andrey Repin
2016-11-18 12:59           ` Brian Inglis
2016-11-20 19:19           ` Achim Gratz
2016-11-21 13:40             ` OwN-3m-All
2016-11-21 16:17               ` Corinna Vinschen
2016-11-18  6:35         ` Andrey Repin
2016-11-18  7:13     ` Andrey Repin
2016-11-19  0:15     ` Achim Gratz [this message]
2016-11-19  2:08       ` OwN-3m-All
2016-11-19 13:42         ` OwN-3m-All
2016-11-19 14:41           ` Brian Inglis
2016-11-20 19:01           ` Jon Turney

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=871sy85yv3.fsf@Rainer.invalid \
    --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).