>Did you really read my mail about *testing* & eventually removing >thoses dependency non useful/problematic BR ?
I did. But how are we supposed to test as long we don't know what some of the dependencies are good for?!? >Or it is just the way you're used to talk without any consideration >for the packager? It's not the packager, it's the policy. Adding something just because upstream has provided an optional dependency... R-C
