public inbox for crossgcc@sourceware.org
 help / color / mirror / Atom feed
From: ANDY KENNEDY <ANDY.KENNEDY@adtran.com>
To: "Yann E. MORIN" <yann.morin.1998@anciens.enib.fr>,
	"crossgcc@sourceware.org" <crossgcc@sourceware.org>
Subject: RE: CT_PREFER_MIRROR working?
Date: Tue, 02 Aug 2011 21:26:00 -0000	[thread overview]
Message-ID: <F9C551623D2CBB4C9488801D14F864C604BCA9@ex-mb1.corp.adtran.com> (raw)
In-Reply-To: <201108022239.12156.yann.morin.1998@anciens.enib.fr>

Yann, All,

> Currently, either downloads are allowed, in which case CT_Get*
> behave so:
>  - first, try from local tqarballs dir
>  - then try from the mirror (which svn, cvs and git do not honor so
> far)
>  - then try from upstream locations
>  - finally fail if not found
> 
> The mirror option is labelled the "LAN mirror", but really nothing
> prevents
> it from being any where on the network, local or not. I already
> provide a
> mirror for a few tarballs (eg. uClibc snapshots, or a few mpfr
> versions as
> upstream is sometime unreachable). It is even suggested to use that
> mirror
> in the CT_USE_MIRROR option.
> 
> So how would one differentiate between:
>  - I don't want to call to the internet, but still use the mirror
> and:
>  - I don't want to call to the internet at all
> when there is no way to know whether the mirror is on the LAN or
> not?
> 
> But anyway, here's what I was planning:
>  - if downloads are forbidden, and no mirror is set
>    - just look in local tarballs dir (if set)
>  - if downloads are forbidden, and a mirror has been set
>    - look in local tarballs dir (if set)
>    - then try the mirror
>  - if downloads are allowed
>    - look in local tarballs dir (if set)
>    - then try the mirror (if set)
>    - then try provided URLs
> 
> Selecting the mirror would be de-correlated from the
> FORBID_DOWNLOAD option,
> so it is always available.
> 

Great explanation, that helped.

> Would that match your use-case? That's what I was intending to do.
> ;-)

Yes, that gets me.

> 
> I believe that's about all we should support. FORBID_DOWNLOAD is
> just here
> as a fast-path when roaming, and network is not available. But
> nothing
> prevents you to be connection-less and still attempt downloads;
> it's just
> that it will take some time before the failure occurs.
> FORBID_DOWNLOAD
> merely makes it happen sooner.

Okay, BUT, there is one problem that I didn't see you mention:

./configure looks for svn, and fails if it is not there.  That
was what I meant by --mirror-dl-only.  A switch for the configure
script to NOT check to see that we have svn installed.

Did you already account for that in the above?  If so, sorry, I
missed it.

Andy

--
For unsubscribe information see http://sourceware.org/lists.html#faq

  reply	other threads:[~2011-08-02 21:26 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-01 15:21 ANDY KENNEDY
2011-08-01 17:08 ` Yann E. MORIN
     [not found]   ` <F9C551623D2CBB4C9488801D14F864C604B493@ex-mb1.corp.adtran.com>
2011-08-01 18:37     ` Yann E. MORIN
2011-08-01 19:24       ` ANDY KENNEDY
2011-08-01 19:44         ` Yann E. MORIN
2011-08-02 17:35           ` ANDY KENNEDY
2011-08-02 18:43             ` Yann E. MORIN
2011-08-02 18:51               ` ANDY KENNEDY
2011-08-02 20:39                 ` Yann E. MORIN
2011-08-02 21:26                   ` ANDY KENNEDY [this message]
2011-08-02 21:20                     ` Yann E. MORIN

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=F9C551623D2CBB4C9488801D14F864C604BCA9@ex-mb1.corp.adtran.com \
    --to=andy.kennedy@adtran.com \
    --cc=crossgcc@sourceware.org \
    --cc=yann.morin.1998@anciens.enib.fr \
    /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).