From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [autobuild.buildroot.net] Build results for 2015-07-19
Date: Mon, 20 Jul 2015 15:10:44 +0200 [thread overview]
Message-ID: <20150720151044.1b5cd445@free-electrons.com> (raw)
In-Reply-To: <CA+BsyQ7zi_ni7qV4X5m07YYJ=eF3YdmQghX+GBcZcZAUtdeUGA@mail.gmail.com>
Dear Brendan Heading,
On Mon, 20 Jul 2015 13:49:14 +0100, Brendan Heading wrote:
> I noticed there are around 200 packages that download from sourceforge. I
> didn't do an exhaustive investigation but noticed that zlib is fetched from
> there. Might it be better to fetch this (and other packages) from their
> authoritative site, where one exists ? (in zlib's case,
> http://zlib.net/zlib-1.2.8.tar.gz ?)
>
> [sourceforge has been in the news for other reasons lately .. I get the
> general feeling that it is a resource that is not long for this world .. ]
Yes, generally speaking identifying all our packages that are still
hosted on SourceForge or Google Code, and finding if there is an
alternate download location would be very good. Patches going in this
direction are welcome. However, beware that the new location should be
somewhat "official": we don't want to use some random Github fork as a
replacement for a Sourceforge / Google Code download.
Thanks!
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2015-07-20 13:10 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-20 6:30 [Buildroot] [autobuild.buildroot.net] Build results for 2015-07-19 Thomas Petazzoni
2015-07-20 12:30 ` Brendan Heading
2015-07-20 12:39 ` Thomas Petazzoni
2015-07-20 12:44 ` Baruch Siach
2015-07-20 12:49 ` Brendan Heading
2015-07-20 13:10 ` Thomas Petazzoni [this message]
2015-07-20 13:54 ` Brendan Heading
2015-07-20 19:55 ` Jörg Krause
2015-07-20 20:38 ` Thomas Petazzoni
2015-07-20 20:48 ` Jörg Krause
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=20150720151044.1b5cd445@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox