[Buildroot] wget download: 'scheme missing' results in empty output file
Peter Korsgaard
peter at korsgaard.com
Thu Feb 25 16:34:14 UTC 2016
>>>>> "Thomas" == Thomas De Schampheleire <patrickdepinguin at gmail.com> writes:
Hi,
>> Shouldn't we simply be checking in the package infrastructure that
>> FOO_SITE is not empty?
> When a PRIMARY_MIRROR is set and there is a 'guarantee' or expectation
> that each file is present on that mirror, FOO_SITE is not really used
> and could be empty for proprietary packages, since there is no actual
> proper value. Sure one could fill in a bogus value, but it's not very
> nice.
You could set _SITE to your PRIMARY_MIRROR, which is really where those
tarballs (should be) are located.
> Also, for packages where the source is included with buildroot, like
> makedevs, FOO_SITE is empty too.
.. but those also don't define _SOURCE / _VERSION, so wget isn't called
;)
--
Bye, Peter Korsgaard
More information about the buildroot
mailing list