[oe] [PATCH] minimal: add weak assigned DISTRO_FEED_CONFIGS variable

[Simon Busch]

On 03.06.2011 18:17, Koen Kooi wrote:
> On 03-06-11 18:07, Simon Busch wrote:
>> On 02.06.2011 16:48, Martin Jansa wrote:
>>> On Thu, Jun 02, 2011 at 04:44:27PM +0200, Simon Busch wrote:
>>>> Some distros are based on the minimal distro but want to supply another feed configuration.
>>>> As minimal uses DISTRO_EXTRA_RDEPENDS to pull distro-feed-configs into the builded image
>>>> the new weak assigned variable DISTRO_FEED_CONFIGS makes it possible to specify another
>>>> feed configuration.
>>>
>>> isn't
>>> DISTRO_FEED_PREFIX
>>> DISTRO_FEED_URI
>>> in
>>> recipes/meta/distro-feed-configs.bb
>>> enought to modify default distro-feed-configs?
>>>
>>> and if not cannot we change distro-feed-configs.bb to allow such
>>> modifications?
> 
>> Maybe you are right and it is the better solution to stay with
>> distro-feed-configs.bb as general solution. The details why I did an own
>> feed configuration is I don't want all PACKAGE_EXTRA_ARCHS as additional
>> feed configs. Why should a image which is flashed to a armv4 device pull
>> the feed configs for a armv7a?
> 
>> When I have a armv7a device it only needs to get the armv7 +
>> MACHINE_ARCH + all feed configs from the remote host for an update and
>> nothing more.
> 
>> The best solution to archive this is as far as I see to make
>> distro-feed-configs machine specific and don't add PACKAGE_EXTRA_ARCHS
>> as feed configuration anymore. For poky-feed-config-opkg in oe-core it's
>> already the case.
> 
> It's also the case for angstrom-feed-configs, which got used as template
> for the distro-feed-configs recipe.

Damn it, I missed the PACKAGE_ARCH line within the distro-feed-configs
recipe. But the issue with PACKAGE_EXTRA_ARCHS is still remaining ...

As I see angstrom-feed-configs uses PACKAGE_ARCHS which includes
PACKAGE_ARCHS, but why should I update the feed on my machine for an
architecture I am not running on? So I would propose to only add feeds
for all, ${MACHINE_ARCH} and ${TARGET_ARCH} (whats with noarch, any as
they are listed in bitbake.conf? they are only relicts from old times?).

regards,
Simon