[Buildroot] Different site methods for the main package and patches
rjbarnet at rockwellcollins.com
rjbarnet at rockwellcollins.com
Wed Mar 26 23:00:36 UTC 2014
Peter/Thomas/Yann,
Peter Korsgaard <jacmet at uclibc.org> wrote on 03/26/2014 05:42:20 PM:
> >>>>> "Thomas" == Thomas Petazzoni <thomas.petazzoni at free-electrons.com>
writes:
>
> Hi,
>
> > Generally speaking, I'm a bit unhappy about how things work on the
> > download front:
>
> > *) I don't really understand why we have a separation between _SITE
> > and _SOURCE, and why our infra assumes that _PATCH is relative to
> > _SITE. Why don't we simply make _SOURCE and _PATCH full URLs
> > instead? This way _PATCH can list multiple patches coming from
> > different locations, not necessarily the upstream location of the
> > package.
>
> Some of it is historical, but it also makes it easier to support
> the primary/backup site features.
The primary/backup site feature is useful when using Buildroot on build
machines behind a firewall. You are able to create and host a local mirror
of http://sources.buildroot.net/ which makes managing firewall rules much
easier. Any modification to the download infrastructure would need to
support this feature (preferably by still defining BR2_PRIMARY_SITE).
Thanks,
-Ryan
More information about the buildroot
mailing list