On 3/10/17 5:24 AM, Alexander Kanavin wrote: > It's a machine-specific script, which is causing conflicts > when multiple versions of bash are installed in multilib setting, > and it also does not really make sense for embedded systems anyway.
Out of curiosity what is machine specific here? (The bashbug shouldn't be part of the main recipe, no disagreement.) But in the past we had a single bashbug that would not conflict in multilibs -- that must have broken at some point. --Mark > Signed-off-by: Alexander Kanavin <[email protected]> > --- > meta/recipes-extended/bash/bash.inc | 4 ++++ > 1 file changed, 4 insertions(+) > > diff --git a/meta/recipes-extended/bash/bash.inc > b/meta/recipes-extended/bash/bash.inc > index a05b987b87b..3e9c6625693 100644 > --- a/meta/recipes-extended/bash/bash.inc > +++ b/meta/recipes-extended/bash/bash.inc > @@ -65,3 +65,7 @@ pkg_postinst_${PN} () { > pkg_postrm_${PN} () { > printf "$(grep -v "^${base_bindir}/bash$" $D${sysconfdir}/shells)\n" > > $D${sysconfdir}/shells > } > + > +PACKAGES += "${PN}-bashbug" > +FILES_${PN} = "${bindir}/bash ${base_bindir}/bash.bash" > +FILES_${PN}-bashbug = "${bindir}/bashbug" > -- _______________________________________________ Openembedded-core mailing list [email protected] http://lists.openembedded.org/mailman/listinfo/openembedded-core
