yeah. it matches all crates that are the transitive dependency of a build script. In case of crates which are included in both, we'd need to figure out what to do here (likely use the build script override in both cases)
That is, I think it’s probably ok to add implementation level hacks for obscure edge cases to make common case easier.
I think this isn't going to work well in the long run as more keys get added 
. It also stops us from adding other functionality to profiles easily. Nesting tables under profile.foo.overrides seems ok. We can have profile.foo.build_override for the special build script case; weird syntax will probably be more confusing than informative