On Sat, 7 Dec 2024 at 01:20, Mark Brown <broonie@xxxxxxxxxx> wrote: > > It doesn't remove existing barriers but it's also not obvious that this > isn't just a generic dependency mechanism that should be used for any > old dependency rather than things that would actually break the build, > and it's one config list for both build and runtime checks. If the > intention is that this should be infrequently used it probably needs to > be a bit clearer that that's the case. As things stand I'd expect there > to be some confusion about the interaction between this and the existing > system with specifying config fragments. I shall update the commit and documentation to make this more clear. Thank you for the feedback.