-----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----- _______________________________________________ Openembedded-devel mailing list Openembedded-devel@lists.openembedded.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
