From: Rolf Leggewie <no2spam@nospam.arcornews.de>
To: openembedded-devel@openembedded.org
Subject: RFC: encourage switch away from heanet.sf.net
Date: Fri, 08 Dec 2006 14:15:27 +0100 [thread overview]
Message-ID: <elbohi$a8k$1@sea.gmane.org> (raw)
Hi,
it occurred to me today that Sourceforge is not using that intermediate
page anymore where it lists all the mirrors for a file to be downloaded.
It used to be necessary that you click on one of the mirrors there
to actually start the download from the browser. Instead they
automatically 302 you now.
Mirrors are there for a reason. Unfortunately, sf.net forced us in the
past to use heanet.sourceforge.net for download since it was the only
complete mirror. This is not the case any more, we can use
downloads.sf.net but still be sure to get the files we need (assuming
that sf.net will only redirect us to mirrors that *do* have the file).
I therefore suggest to change bitbake.conf in the following way and
request your comments on the matter (especially from hrw since RP
suggested you are the most knowledgeable about sf.net and the
associated, past problems). This would set the IMHO sane default from
which users can still deviate via local.conf and site.conf
- SOURCEFORGE_MIRROR = "http://heanet.dl.sourceforge.net/sourceforge"
+ SOURCEFORGE_MIRROR = "http://downloads.sf.net"
For what it is worth, I for one have switched (via site.conf so far).
Regards
Rolf
next reply other threads:[~2006-12-08 13:17 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-08 13:15 Rolf Leggewie [this message]
2006-12-08 13:19 ` RFC: encourage switch away from heanet.sf.net Michael 'Mickey' Lauer
2006-12-09 10:35 ` Rolf Leggewie
2006-12-10 22:30 ` Richard Purdie
2006-12-11 20:44 ` Marcin Juszkiewicz
2006-12-12 12:14 ` Rolf Leggewie
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='elbohi$a8k$1@sea.gmane.org' \
--to=no2spam@nospam.arcornews.de \
--cc=openembedded-devel@lists.openembedded.org \
--cc=openembedded-devel@openembedded.org \
/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.