<div class="gmail_quote">On Wed, Nov 9, 2011 at 3:58 PM, Ryan Newton <span dir="ltr"><<a href="mailto:rrnewton@gmail.com">rrnewton@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
I don't know about you, but I personally haven't found the time to cast back in time for each of my package's dependencies to find a true lower bound version.<br><br>Do we have any tools that would do the following?<br>
<ul><li>ask Hackage for the available versions of package foo</li><li>use cabal-dev to build your package against foo-X.Y.Z forall {X,Y,Z} (but leaving other packages unconstrained)<br></li><li>report successes and failures, including last failure before the present version (and therefore lower bound, exclusive)</li>
</ul></blockquote><div>What about dependency interactions? If you depend on foo and bar there might be versions of foo and bar that don't build together that you might not discover by varying their versions independently.<br>
</div><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;"><ul>
</ul>Johan, would it make any sense to extend your Jenkins setup to do this?<span class="HOEnZb"><font color="#888888"><br></font></span></blockquote><div><br style="color: rgb(0, 0, 0);"><span class="HOEnZb"><font color="#888888"><span style="color: rgb(0, 0, 0);">If someone came up with a recipe, sure. It might be a bit CPU intensive for my little VPS though.</span><br style="color: rgb(0, 0, 0);">
<br>-- Johan<br><br>
</font></span></div></div>