Am 06/12/16 um 15:40 schrieb Robert Scholte: >> >> Why? >> > > Let me quote myself: > "I've been talking about this change with a couple of fellow committers at > FOSDEM and it convinced me that you never ever want to manage optional. > They have too much effect on the dependencies using it. For dependencies > which are expected to be non-optional (default) it suddenly will be.
If you say so, yes. That's the point. It's you managing that flag. So that's not a "suddenly" that's an "intentional because you say so". There are quite some use cases you would want to manage the optional flag. Only drawback is projects having used the optional flag in dependency management not noticing that this is ignored before 3.4. That's the only issue I am seeing with this. --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
