I had lots more here about managing feature dependencies in general,
but
ended up snipping it because it is a complex beast and I would need to
give
it more thought. In the meantime, I think the most important property
for
maintainability is to blacklist globally and whitelist per package;
blacklisting individual packages doesn't scale with the number of
dependencies.
Makes sense to me. I think it will be easier/more understandable to add
a suppress features configuration variable than a “-“ before it.
I’ll add a blacklist, with the ability to globally blacklist a
feature, and a whitelist. The whitelist will take precedence over the
blacklist.
It seems to me that these should only be specified at at the target or
application level, as digging through packages here seems insane in
terms of figuring out what’s going on, so I’ll restrict that —
unless people disagree?
Sterling
