Use-cases for version ranges?

[cowwoc]

On 19/11/2011 5:51 AM, Nicolas Lalevée [via jigsaw-dev] wrote:
> A last note on the solution on overriding dependencies. This really 
> looks like a hack to me. The developer of a module A declare a 
> dependency on module B and we say, no, it's actually module C. For me 
> it it like changing the visibility of a method from private to public 
> via introspection.

     We aren't substituting module B for module C. We are substituting 
module B version 1.0 with module B version 1.1. So long as we substitute 
for a version which is compatible wiht version 1.0 why should the author 
care?

Gili


--
View this message in context: http://jigsaw-dev.1059479.n5.nabble.com/Use-cases-for-version-ranges-tp5002801p5007723.html
Sent from the jigsaw-dev mailing list archive at Nabble.com.