All of lore.kernel.org
 help / color / mirror / Atom feed
From: Koen Kooi <koen@dominion.thruhere.net>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [PATCH] minimal: add weak assigned DISTRO_FEED_CONFIGS variable
Date: Fri, 03 Jun 2011 20:28:44 +0200	[thread overview]
Message-ID: <isb94s$svu$1@dough.gmane.org> (raw)
In-Reply-To: <4DE90EA6.3060703@gravedo.de>

-----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-----




      parent reply	other threads:[~2011-06-03 18:32 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-02 14:44 [PATCH] minimal: add weak assigned DISTRO_FEED_CONFIGS variable Simon Busch
2011-06-02 14:48 ` Martin Jansa
2011-06-03 16:07   ` Simon Busch
2011-06-03 16:17     ` Koen Kooi
2011-06-03 16:22       ` Simon Busch
2011-06-03 16:38         ` Koen Kooi
2011-06-03 16:41           ` Simon Busch
2011-06-03 17:18             ` [PATCH] distro-feed-configs: use ${FEED_ARCH} instead of ${PACKAGE_EXTRA_ARCHES} and bump PR Simon Busch
2011-06-03 18:28             ` Koen Kooi [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='isb94s$svu$1@dough.gmane.org' \
    --to=koen@dominion.thruhere.net \
    --cc=openembedded-devel@lists.openembedded.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.