On Tue, Jun 15, 2021 at 11:29:01AM +0100, Richard Purdie wrote: > a) is another assignment operator a good idea?
I'm not terribly convinced it is. If the problem is that there's no way to clear the OVERRIDES, maybe we should just have a new verb to do that specifically rather than a new assignment operator that ignores them. Ultimately though this particular example just seems like a case where it's possible for a carelessly-written BSP to make life difficult for its users. I don't think this is the only such, and I'm not sure a new assignment operator would necessarily solve the general case. Adding more and more special operators that defeat each other seems like it's just going to result in a perpetual arms race. If we add a new !=! operator then, BSP authors being as ingenious as they are, they'll start using that all over the place and you suddenly won't be able to override anything any more. Then we'll need a new and even more powerful OVERRRRIDES that can't be suppressed, and we'll be back where we started :-) p.
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#1229): https://lists.openembedded.org/g/openembedded-architecture/message/1229 Mute This Topic: https://lists.openembedded.org/mt/83552628/21656 Group Owner: [email protected] Unsubscribe: https://lists.openembedded.org/g/openembedded-architecture/unsub [[email protected]] -=-=-=-=-=-=-=-=-=-=-=-
