On Tue, 2021-06-15 at 11:42 +0000, Quentin Schulz wrote:
Well, it seems like an ok thing for a BSP to do to me. There are probably
other ways it could be done, sure.
Resetting IMAGE_FSTYPES_collie to INITRAMFS_FSTYPES should be enoughNo, I don't see how that helps.
The issue in the email is an example of a general problem where it isThe questions areI'm not sure the issue explained in this mail is enough to warrant a new
effectively impossible to undo certain operations. That general issue bothers
me more than this specific case.
We can argue the BSP is broken. The BSP is arguing bitbake is broken.
Failing that, there is an argument the initramfs recipes are broken. I
can see the different sides but there is a general problem here we've
pondered over for a while.
I can already see vendors abusing this by always using this new operatorWe could ban the operator from conf files (enforced)?
This would be even less fun to support on IRC or mailing lists.Maybe, maybe not. It depends how it gets used and if "abuse" occurs.
Also... As opposed to other operators, what would happen if you use theThankfully that is quite clear and would clear any overrides set against
Except that half the behaviour of := doesn't apply (the expansion). :=b) if so, which form?Totally unbiased. The last two 😁
is immediate expansion *and* immediate assignment.