Hey guys,

On 09/26/2017 09:33 AM, Wold, Saul wrote:
On Tue, 2017-09-26 at 09:11 +0300, Jussi Laako wrote:
On 25.09.2017 10:00, Mikko Ylinen wrote:
On 23/09/17 01:03, Alejandro Hernandez wrote:
When using DISTRO=poky-tiny we dont need to have thermald
and also it brings about ~4MB of dependencies.
It's conceptually not right to have a distro dependency in the
BSP settings, IMO.

If your distro/image does not need something the BSP thinks is
necessary, the distro/image itself should deal with that.
This is problem to a bigger extent too. Many BSPs try to pull in all
kinds of extra things, such as gstreamer plugins, even if the image
being built doesn't need such things.

And Distro's don't know what a BSP might pull in, so they can't
directly _remove or exclude them somehow.
Yes, this seems wrong when you put it that way.

I think it is overall a bad idea to force BSP to pull in lot of high
level user space components by default that are not essential for
the
basic functionality (boot-to-init), be it thermald or gstreamer.
Generally agreed, I am not sure I would call thermald high-level, it is
targeted for Intel hardware, just as we pull in the microcode to ensure
that is updated for the hardware.

Maybe we should move thermald to RRECOMMENDS in the case of meta-intel
instead of RDEPENDS

This
doesn't apply only to poky-tiny, but to many other distros too. I
would
rather like to see those as optional extra that can be enabled
through a
variable.

Would RRECOMMENDS be sufficient?  What kind of variable something that
says the BSP can add stuff or not?

Sau!
I'm guessing RRECOMMENDS would be enough, at least in this case,
since poky-tiny should probably have NO_RECOMMENDATIONS or at least
BAD_RECOMMENDATIONS listed.

Alejandro

--
_______________________________________________
meta-intel mailing list
[email protected]
https://lists.yoctoproject.org/listinfo/meta-intel

Reply via email to