[OE-core] [PATCH 1/1] default-distrovars.inc, task-core-boot.bb: Create distro overridable varibales

Koen Kooi koen at dominion.thruhere.net
Wed May 18 18:15:03 UTC 2011


Op 18 mei 2011, om 20:07 heeft Khem Raj het volgende geschreven:

> On Wed, May 18, 2011 at 10:52 AM, Leon Woestenberg
> <leon.woestenberg at gmail.com> wrote:
>> Hello,
>> 
>> On Wed, May 18, 2011 at 7:29 PM, Koen Kooi <koen at dominion.thruhere.net> wrote:
>>> 
>>> Op 18 mei 2011, om 19:08 heeft Phil Blundell het volgende geschreven:
>>> 
>>>> On Wed, 2011-05-18 at 09:40 -0700, Khem Raj wrote:
>>>>> Problem I have is, I dont want udev in RDEPENDS which is added by
>>>>> task-core-boot
>>>>> and task-core-boot is added to DISTRO_EXTRA_RDEPENDS through
>>>>> default-distrovars.inc -> defaultsetup.conf -> bitbake.conf
>>>>> 
>>>>> and my distro adds DISTRO_EXTRA_RDEPENDS to its RDEPENDS
>>>>> as I think the variable is meant for distro's to define some extra
>>>>> stuff if needed.
>>>>> 
>>>>> How should I solve this problem ?
>>>> 
>>>> Well, what I did in micro-base-image was simply to not use
>>>> task-core-boot at all.  But in your case I was thinking that you could
>>>> overlay that recipe with from your distro's layer and make it do
>>>> whatever you wanted.
>>> 
>>> The fact that we have layers does not mean we need to follow the silo mentality you seem to prefer. If task-base in oe-core stops being usefull we should fix it, now play around in our own little sandboxes.
>>> 
>> If task-base is getting less useful, removing it altogether (I found
>> the  reasons mentioned by Phil convincing)  should be at least
>> considered as an alternative.
>> 
>> I am not sure why we should keep task-base as something generic --all
>> distro's have their own specific requirements and configurations, even
>> for task-base, so why not move this functionality into the distro and
>> out of oe-core?
>> 
>> I never quite saw what task-base gained us on a netto basis, but I
>> think I am biased towards small tweaked images, so these are just my
>> two cents.
>> 
> 
> there are certain common parts that can be abstracted
> and can be maintained in oe-core so everyone benefits
> from it and certain image specific parts can be done in
> distros. So keeping common parts in core would still
> be better IMO

And in OE .dev we split task-boot from task-base to be able to get the benefits from task base without forcing task-boot. OE-core had the same till it got forcefully added to the extra depends last week.

regards,

Koen



More information about the Openembedded-core mailing list