On Fri, 2019-01-25 at 09:37 -0600, Joshua Watt wrote: > On Fri, 2019-01-25 at 13:13 +0100, Alexander Kanavin wrote: > > There is a similar issue in multilib for target packages (a warning > > because qemu usermode support is missing): > > https://autobuilder.yoctoproject.org/typhoon/#/builders/44/builds/214/steps/7/logs/warnings > > > > I'm as well not sure how to handle this: > > 1. Keep these two warnings as warnings so users see them in their > > local builds, but > > add some kind of string pattern to AB so it excludes missing qemu > > support and missing wine support warnings. > > > > 2. Turn them into notes, which means they will go to the logs only, > > and users are not going to see them ever. On the other hand, the > > postinsts tend to > > create things like font caches and similar, which should not > > generally > > be needed at compile time (which is what SDKs are for). > > > > I'm leaning towards option two. > > I was leaning toward keeping them warnings and then suppressing them in > the cases where we know they don't work and are unnecessary (perhaps > with a variable like POSTINST_INTERCEPT_${PN} = "0" ?) > > That way if a user enables a package where it's not going to run and we > haven't previously evaluated it to be OK, they will at least see the > warning. I naively think this might help reduce the number of bugs > filed, or at least make them easier to triage :)
I think this may be safer... Cheers, Richard -- _______________________________________________ Openembedded-core mailing list [email protected] http://lists.openembedded.org/mailman/listinfo/openembedded-core
