All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] pcre: Change download location
Date: Tue, 7 Mar 2017 14:02:53 +0100	[thread overview]
Message-ID: <20170307140253.60681b57@free-electrons.com> (raw)
In-Reply-To: <87d1dtdzim.fsf@dell.be.48ers.dk>

Hello,

On Tue, 07 Mar 2017 13:47:45 +0100, Peter Korsgaard wrote:

> I'm a bit confused about the description. To me it sounds like a local
> firewall issue with ftp access instead, but OK - Others might have a
> similar setup.

If you look at Buildroot 2015.11, as point out in the commit log, it
contains:

PCRE_VERSION = 8.38
PCRE_SITE = ftp://ftp.csx.cam.ac.uk/pub/software/programming/pcre

However, the 8.38 version is no longer available at
ftp://ftp.csx.cam.ac.uk/pub/software/programming/pcre, the oldest
available version from this site is 8.39.

Hence, the fact that we have been using
ftp://ftp.csx.cam.ac.uk/pub/software/programming/pcre in older
Buildroot versions means that these older versions are now "broken" and
have to fallback on sources.buildroot.net.

So, no: it's not a local issue due to a firewall.

By using the https://ftp.pcre.org/pub/pcre/ location, which contains
all previous versions, we increase our chances that 2017.02 will not be
"broken" in 2 years.

We could have also said that pcre.org looks a bit more
official/upstream, and indeed https:// is better than ftp://.

Best regards,

Thomas
-- 
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com

  reply	other threads:[~2017-03-07 13:02 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-06  0:02 [Buildroot] [PATCH 1/1] pcre: Change download location Oleg Kitain
2017-03-06 20:20 ` Thomas Petazzoni
2017-03-07 12:47   ` Peter Korsgaard
2017-03-07 13:02     ` Thomas Petazzoni [this message]
2017-03-07 14:03       ` Peter Korsgaard
2017-03-07 14:11         ` Thomas Petazzoni
2017-03-07 12:44 ` Peter Korsgaard

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=20170307140253.60681b57@free-electrons.com \
    --to=thomas.petazzoni@free-electrons.com \
    --cc=buildroot@busybox.net \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.