On Thu, Nov 14, 2019 at 11:52 AM Neal Gompa <ngompa13(a)gmail.com> wrote:
> Similarly, from the perspective of dependent maintainers, there will
> no longer be anxiety about needing to move their package to a module
> if one or more of their dependencies drops their non-modular version
> in favor of a default stream. Their builds will continue to work as
> they do today.
>
This might be a dumb question (perhaps I missed the answer somewhere
in the thread), but how do we handle setting overrides for modular
content? Without that, it's going to be hard to do modular update to
fix non-modular builds...
Sorry, I don't understand what question you're asking here. Could you
try using an example to make it clearer?