On Sat, 2025-11-29 at 10:59 +0100, Alexander Kanavin via lists.openembedded.org wrote: > On Sat, 29 Nov 2025 at 08:25, Gyorgy Sarvari <[email protected]> wrote: > > > This allows disabling classes of fragments without knowing their full > > > names, e.g. > > > instead of > > > > > > $ bitbake-config-build disable-fragment machine/qemuarm > > > > > > one can issue > > > > > > $ bitbake-config-build disable-fragment machine > > > > > > to match and disable everything that starts with 'machine'. > > > > > > Add an --exact option to preserve exact maching (e.g. when > > > theres some/feature and some/feature-with-foobar both enabled > > > and only the first needs to be disabled). > > > > Why not add a --wildcard option instead, and keep the default behavior > > backwards compatible? > > I considered this, but I tohught most people would prefer prefix > matching to be the default, it's just more convenient. Fragments are > still very new, and situations where --exact is necessary are rare. > > This will be discussed in patch review. If preserving behaviour is the > outcome, I wouldn't add an option (that no one would know about), it > would be a separate command: disable-by-prefix.
Perhaps the compromise is to support: bitbake-config-build disable-fragment machine/ i.e. the prefix matching only triggers if the / is at the end? That is perhaps relatively explicit/intuitive enough? Cheers, Richard
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#226933): https://lists.openembedded.org/g/openembedded-core/message/226933 Mute This Topic: https://lists.openembedded.org/mt/116517046/21656 Group Owner: [email protected] Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [[email protected]] -=-=-=-=-=-=-=-=-=-=-=-
