I've recently come across a problem, which has apparently been around for a long time, and yet has somehow remained unnoticed.
Facts: - bash and busybox recipes conditionally (based on usrmerge in the DISTRO_FEATURES) declare some RPROVIDES - what they declare in RPROVIDES are actually file paths - e.g. '/bin/sh', '/bin/ash' or '/bin/bash' - resulting entries in their packagedata are "correct" - i.e. 'RPROVIDES = /bin/sh /bin/bash' - resulting entries in their buildhistory are mangled - i.e. 'RPROVIDES = bib bin bash sh' Thesis: - such entries in RPROVIDES (or any other package namespace related variable) are an error (at least looking at what insane.bbclass deems an acceptable package name) - buildhistory should be consistent in its processing of package names with packagedata I'd like to ask for your comments as to what would be the best way to approach this. My view would be to fix the recipes, the buildhistory.bbclass but also make sure that all package related variables are guarded in equal degree in all relevant stages (e.g. in the insane.bbclass). Thanks, Adam
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#2210): https://lists.openembedded.org/g/openembedded-architecture/message/2210 Mute This Topic: https://lists.openembedded.org/mt/116779688/21656 Group Owner: [email protected] Unsubscribe: https://lists.openembedded.org/g/openembedded-architecture/unsub [[email protected]] -=-=-=-=-=-=-=-=-=-=-=-
