|author||Thomas De Schampheleire <firstname.lastname@example.org>||2012-06-22 07:37:03 +0200|
|committer||Thomas Petazzoni <email@example.com>||2012-07-22 18:29:33 +0200|
Package downloads: allow restricting to primary site only
This patch adds a new config option BR2_PRIMARY_SITE_ONLY that, when set, restricts package downloads to the specified BR2_PRIMARY_SITE. If the package is not present on the primary site, the download fails. This is useful for project developers who want to ensure that the project can be built even if the upstream tarball locations disappear. [firstname.lastname@example.org: Extend config option help message with more details coming from the commit log. Added a dependency on the fact that a primary site has been defined. Without any primary site (the default configuration), this new option does not make any sense.] Signed-off-by: Thomas De Schampheleire <email@example.com> Acked-by: Arnout Vandecappelle (Essensium/Mind) <firstname.lastname@example.org> Signed-off-by: Thomas Petazzoni <email@example.com>
Diffstat (limited to 'Config.in')
1 files changed, 18 insertions, 0 deletions
@@ -123,6 +123,22 @@ config BR2_PRIMARY_SITE
NOTE: This works for all packages using the central package
infrastructure (generic, autotools, cmake, ...)
+ bool "Only allow downloads from primary download site"
+ depends on BR2_PRIMARY_SITE != ""
+ If this option is enabled, downloads will only be attempted
+ from the primary download site. Other locations, like the
+ package's official download location or the backup download
+ site, will not be considered. Therefore, if the package is
+ not present on the primary site, the download fails.
+ This is useful for project developers who want to ensure
+ that the project can be built even if the upstream tarball
+ locations disappear.
string "Backup download site"
@@ -179,6 +195,8 @@ config BR2_DEBIAN_MIRROR
Usually, just add your country code like XX here: