Patchwork minimal: add weak assigned DISTRO_FEED_CONFIGS variable

login
register
mail settings
Submitter Simon Busch
Date June 2, 2011, 2:44 p.m.
Message ID <1307025867-12077-1-git-send-email-morphis@gravedo.de>
Download mbox | patch
Permalink /patch/5321/
State New, archived
Headers show

Comments

Simon Busch - June 2, 2011, 2:44 p.m.
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.

Signed-off-by: Simon Busch <morphis@gravedo.de>
---
 conf/distro/minimal.conf |    4 +++-
 1 files changed, 3 insertions(+), 1 deletions(-)
Martin Jansa - June 2, 2011, 2:48 p.m.
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?

Regards,

> 
> Signed-off-by: Simon Busch <morphis@gravedo.de>
> ---
>  conf/distro/minimal.conf |    4 +++-
>  1 files changed, 3 insertions(+), 1 deletions(-)
> 
> diff --git a/conf/distro/minimal.conf b/conf/distro/minimal.conf
> index 18bcfae..edac24f 100644
> --- a/conf/distro/minimal.conf
> +++ b/conf/distro/minimal.conf
> @@ -53,6 +53,8 @@ INHERIT += "package_ipk"
>  IMAGE_FSTYPES ?= "tar.gz jffs2"
>  PREFERRED_PKG_FORMAT ?= "ipk"
>  
> +DISTRO_FEED_CONFIGS ?= "distro-feed-configs"
> +
>  # Put links to sources in deploy/sources to make it easier for people to be GPL compliant
>  INHERIT += "src_distribute_local"
>  SRC_DIST_LOCAL ?= "symlink"
> @@ -135,7 +137,7 @@ DISTRO_EXTRA_APPS += '${@base_conditional("DISTRO_TYPE", "release", "", "task-cl
>  # util-linux-ng-mount util-linux-ng-umount: busybox mount is broken
>  # angstrom-libc-fixup-hack: fixes an obscure bug with libc.so symlink
>  DISTRO_EXTRA_RDEPENDS += "\
> -  distro-feed-configs \
> +  ${DISTRO_FEED_CONFIGS} \
>    util-linux-ng-mount util-linux-ng-umount \
>    angstrom-libc-fixup-hack \
>    ${DISTRO_EXTRA_APPS} \
> -- 
> 1.7.4.1
> 
> 
> _______________________________________________
> Openembedded-devel mailing list
> Openembedded-devel@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
Simon Busch - June 3, 2011, 4:07 p.m.
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.

regards,
Simon
Koen Kooi - June 3, 2011, 4:17 p.m.
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

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.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Darwin)

iD8DBQFN6Qj9MkyGM64RGpERAn7nAKCJp18FRT3BK7dKsets7aTyBe5c0QCeOT88
oo1QgaUw8BQfYzfI+l/iNSY=
=D1oO
-----END PGP SIGNATURE-----
Simon Busch - June 3, 2011, 4:22 p.m.
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
Koen Kooi - June 3, 2011, 4:38 p.m.
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 03-06-11 18:22, Simon Busch wrote:
> 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?).

root@usrp-e1xx:~# ls /etc/opkg/
arch.conf  base-feed.conf  debug-feed.conf  gstreamer-feed.conf
noarch-feed.conf  opkg.conf  perl-feed.conf  python-feed.conf
sdk-feed.conf  usrp-e1xx-feed.conf

root@usrp-e1xx:~# grep arm /etc/opkg/*
/etc/opkg/arch.conf:arch arm 16
/etc/opkg/arch.conf:arch armv4 21
/etc/opkg/arch.conf:arch armv4t 26
/etc/opkg/arch.conf:arch armv5te 31
/etc/opkg/arch.conf:arch armv6 36
/etc/opkg/arch.conf:arch armv7 41
/etc/opkg/arch.conf:arch armv7a 46
/etc/opkg/base-feed.conf:src/gz base
http://feeds.angstrom-distribution.org/feeds/next/ipk/eglibc/armv7a/base
/etc/opkg/debug-feed.conf:src/gz debug
http://feeds.angstrom-distribution.org/feeds/next/ipk/eglibc/armv7a/debug
/etc/opkg/gstreamer-feed.conf:src/gz gstreamer
http://feeds.angstrom-distribution.org/feeds/next/ipk/eglibc/armv7a/gstreamer
/etc/opkg/perl-feed.conf:src/gz perl
http://feeds.angstrom-distribution.org/feeds/next/ipk/eglibc/armv7a/perl
/etc/opkg/python-feed.conf:src/gz python
http://feeds.angstrom-distribution.org/feeds/next/ipk/eglibc/armv7a/python
/etc/opkg/usrp-e1xx-feed.conf:src/gz usrp-e1xx
http://eu.feeds.angstrom-distribution.org/feeds/next/ipk/eglibc/armv7a/machine/usrp-e1xx
root@usrp-e1xx:~#

So only armv7a there, not armv6 and armv5te, armv4t, etc there.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Darwin)

iD8DBQFN6Q30MkyGM64RGpERAktPAKC8aMVuBcLNcnXtduRDBAmJXU9z0wCeINLn
O1A//kHxU1u7sLKvTZlzSi4=
=jjQK
-----END PGP SIGNATURE-----
Simon Busch - June 3, 2011, 4:41 p.m.
On 03.06.2011 18:38, Koen Kooi wrote:
> On 03-06-11 18:22, Simon Busch wrote:
>> 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?).
> 
> root@usrp-e1xx:~# ls /etc/opkg/
> arch.conf  base-feed.conf  debug-feed.conf  gstreamer-feed.conf
> noarch-feed.conf  opkg.conf  perl-feed.conf  python-feed.conf
> sdk-feed.conf  usrp-e1xx-feed.conf
> 
> root@usrp-e1xx:~# grep arm /etc/opkg/*
> /etc/opkg/arch.conf:arch arm 16
> /etc/opkg/arch.conf:arch armv4 21
> /etc/opkg/arch.conf:arch armv4t 26
> /etc/opkg/arch.conf:arch armv5te 31
> /etc/opkg/arch.conf:arch armv6 36
> /etc/opkg/arch.conf:arch armv7 41
> /etc/opkg/arch.conf:arch armv7a 46
> /etc/opkg/base-feed.conf:src/gz base
> http://feeds.angstrom-distribution.org/feeds/next/ipk/eglibc/armv7a/base
> /etc/opkg/debug-feed.conf:src/gz debug
> http://feeds.angstrom-distribution.org/feeds/next/ipk/eglibc/armv7a/debug
> /etc/opkg/gstreamer-feed.conf:src/gz gstreamer
> http://feeds.angstrom-distribution.org/feeds/next/ipk/eglibc/armv7a/gstreamer
> /etc/opkg/perl-feed.conf:src/gz perl
> http://feeds.angstrom-distribution.org/feeds/next/ipk/eglibc/armv7a/perl
> /etc/opkg/python-feed.conf:src/gz python
> http://feeds.angstrom-distribution.org/feeds/next/ipk/eglibc/armv7a/python
> /etc/opkg/usrp-e1xx-feed.conf:src/gz usrp-e1xx
> http://eu.feeds.angstrom-distribution.org/feeds/next/ipk/eglibc/armv7a/machine/usrp-e1xx
> root@usrp-e1xx:~#
> 
> So only armv7a there, not armv6 and armv5te, armv4t, etc there.

Yeah, thats the case for angstrom-feed-configs but not
distro-feed-configs ...
Koen Kooi - June 3, 2011, 6:28 p.m.
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 03-06-11 18:41, Simon Busch wrote:
> On 03.06.2011 18:38, Koen Kooi wrote:
>> On 03-06-11 18:22, Simon Busch wrote:
>>> 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?).
>>
>> root@usrp-e1xx:~# ls /etc/opkg/
>> arch.conf  base-feed.conf  debug-feed.conf  gstreamer-feed.conf
>> noarch-feed.conf  opkg.conf  perl-feed.conf  python-feed.conf
>> sdk-feed.conf  usrp-e1xx-feed.conf
>>
>> root@usrp-e1xx:~# grep arm /etc/opkg/*
>> /etc/opkg/arch.conf:arch arm 16
>> /etc/opkg/arch.conf:arch armv4 21
>> /etc/opkg/arch.conf:arch armv4t 26
>> /etc/opkg/arch.conf:arch armv5te 31
>> /etc/opkg/arch.conf:arch armv6 36
>> /etc/opkg/arch.conf:arch armv7 41
>> /etc/opkg/arch.conf:arch armv7a 46
>> /etc/opkg/base-feed.conf:src/gz base
>> http://feeds.angstrom-distribution.org/feeds/next/ipk/eglibc/armv7a/base
>> /etc/opkg/debug-feed.conf:src/gz debug
>> http://feeds.angstrom-distribution.org/feeds/next/ipk/eglibc/armv7a/debug
>> /etc/opkg/gstreamer-feed.conf:src/gz gstreamer
>> http://feeds.angstrom-distribution.org/feeds/next/ipk/eglibc/armv7a/gstreamer
>> /etc/opkg/perl-feed.conf:src/gz perl
>> http://feeds.angstrom-distribution.org/feeds/next/ipk/eglibc/armv7a/perl
>> /etc/opkg/python-feed.conf:src/gz python
>> http://feeds.angstrom-distribution.org/feeds/next/ipk/eglibc/armv7a/python
>> /etc/opkg/usrp-e1xx-feed.conf:src/gz usrp-e1xx
>> http://eu.feeds.angstrom-distribution.org/feeds/next/ipk/eglibc/armv7a/machine/usrp-e1xx
>> root@usrp-e1xx:~#
>>
>> So only armv7a there, not armv6 and armv5te, armv4t, etc there.
> 
> Yeah, thats the case for angstrom-feed-configs but not
> distro-feed-configs ...

Yes, that's what I said in my email.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Darwin)

iD8DBQFN6SfcMkyGM64RGpERAhdLAJ0dadfJRZvJFUlvCQz41CnJbf1mbgCgpfQW
MtmNJrvRKRxTwDPJc0CfJdM=
=/+Se
-----END PGP SIGNATURE-----

Patch

diff --git a/conf/distro/minimal.conf b/conf/distro/minimal.conf
index 18bcfae..edac24f 100644
--- a/conf/distro/minimal.conf
+++ b/conf/distro/minimal.conf
@@ -53,6 +53,8 @@  INHERIT += "package_ipk"
 IMAGE_FSTYPES ?= "tar.gz jffs2"
 PREFERRED_PKG_FORMAT ?= "ipk"
 
+DISTRO_FEED_CONFIGS ?= "distro-feed-configs"
+
 # Put links to sources in deploy/sources to make it easier for people to be GPL compliant
 INHERIT += "src_distribute_local"
 SRC_DIST_LOCAL ?= "symlink"
@@ -135,7 +137,7 @@  DISTRO_EXTRA_APPS += '${@base_conditional("DISTRO_TYPE", "release", "", "task-cl
 # util-linux-ng-mount util-linux-ng-umount: busybox mount is broken
 # angstrom-libc-fixup-hack: fixes an obscure bug with libc.so symlink
 DISTRO_EXTRA_RDEPENDS += "\
-  distro-feed-configs \
+  ${DISTRO_FEED_CONFIGS} \
   util-linux-ng-mount util-linux-ng-umount \
   angstrom-libc-fixup-hack \
   ${DISTRO_EXTRA_APPS} \