From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from gravedo.de ([85.214.79.159]) by linuxtogo.org with esmtp (Exim 4.72) (envelope-from ) id 1QSXU0-000634-0j for openembedded-devel@lists.openembedded.org; Fri, 03 Jun 2011 18:44:24 +0200 Received: by gravedo.de (Postfix, from userid 5001) id 59387799012; Fri, 3 Jun 2011 18:41:13 +0200 (CEST) X-Spam-Checker-Version: SpamAssassin 3.2.5 (2008-06-10) on h1108419.serverkompetenz.net X-Spam-Level: X-Spam-Status: No, score=-4.0 required=6.0 tests=ALL_TRUSTED,AWL,BAYES_00 autolearn=ham version=3.2.5 Received: from [192.168.1.37] (p5B3E652D.dip.t-dialin.net [91.62.101.45]) by gravedo.de (Postfix) with ESMTPSA id 76D4E798D74 for ; Fri, 3 Jun 2011 18:41:12 +0200 (CEST) Message-ID: <4DE90EA6.3060703@gravedo.de> Date: Fri, 03 Jun 2011 18:41:10 +0200 From: Simon Busch User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.17) Gecko/20110422 Lightning/1.0b2 Shredder/3.1.11pre MIME-Version: 1.0 To: openembedded-devel@lists.openembedded.org References: <1307025867-12077-1-git-send-email-morphis@gravedo.de> <20110602144829.GI3281@jama.jama.net> <4DE906D9.8000708@gravedo.de> <4DE90A55.7020107@gravedo.de> In-Reply-To: Subject: Re: [PATCH] minimal: add weak assigned DISTRO_FEED_CONFIGS variable X-BeenThere: openembedded-devel@lists.openembedded.org X-Mailman-Version: 2.1.11 Precedence: list Reply-To: openembedded-devel@lists.openembedded.org List-Id: Using the OpenEmbedded metadata to build Distributions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 03 Jun 2011 16:44:24 -0000 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit 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 ...