> For example, the resolver might use it as an optimization to avoid having > to resolve even more dependencies.
Ah. > I'm not sure I totally understand. I assume you are saying, you have a > bundle on which a lot of other resolved bundles have optional dependencies, > but they weren't wired to it because it didn't exist at the time they were > resolved, right? > Yes. Yeah, there isn't anything you can do here, other than re-resolve them all. > Technically, it would be possible to write a command that looks at the > exported packages of an installed bundle and checks to see if any other > bundles optionally import those packages and if so refresh them. So, if this > is a common use case for you, I'd recommend writing such a command...it > wouldn't be too difficult. I understand. I don't know yet if this is going to be a common use case or not, but I agree it shouldn't be too hard to implement. Thanks, Rich
