[oe] OpenEmbedded Core - Ready for extended users

[Anders Darander]

On Tue, May 17, 2011 at 08:38, Koen Kooi <koen at dominion.thruhere.net> wrote:
> On 17-05-11 08:23, Anders Darander wrote:
>> Yes, this is definitely needed. Which type of new
>> applications/libraries can get into meta-oe, and which are supposed to
>> be kept in higher layers...
>>
>> In what cases can additional versions of the recipe in oe-core be
>> added? E.g. dbus is built using 'EXTRA_OECONF = "--with-x"', which at
>> least on head-less systems seems to be overkill.
>
> Dbus is a really good example where the above knee-jerk reaction is
> misplaced :) The --with-x only turns on building dbus-launch, which is x
> specific, but that's the only bit that is. All the other dbus
> subpackages lack X dependencies.

Yes, from that point, Dbus was not the optimal example, I agree...

Though, that was only one example of a package that has either runtime
or only build-time dependencies on X in some form or another. Earlier,
in the 2011.03-releases, we had systemd depending on gtk+, which has
been removed in the lates updates. Thats just another example.

In some cases, removing direct or indirect dependencies like these,
would be something that we'd like to see integrated upstreams. Of
course, we are willing to supply patches for that, after a discussion
on how such things should be handled. Is it desired for package Y or
isn't it. This could sometimes be to reduce the image size, but in
cases like dbus, it might only be to reduce build time and
build-directory size.

In other cases, I assume that we're going to continue keeping our
patchsets local, as I guess that we probably have quite uncommon
desires to get a certain packet working without e.g. X or some other
dependency.

Regards,
Anders