<div dir="ltr"><div>Does this mean that if I include a test suite in my package and register it on PLaneT, the tests will be automatically run from your servers?<br></div>And if some test fails, the package will not be updated for those who run `raco pkg update` ?<br> <div class="gmail_extra"><br><br><div class="gmail_quote">On Thu, May 2, 2013 at 4:11 PM, Robby Findler <span dir="ltr"><<a href="mailto:robby@eecs.northwestern.edu" target="_blank">robby@eecs.northwestern.edu</a>></span> wrote:<br> <blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">One thing perhaps worth mentioning, tho, is that there will be a curated package source where we will make significant efforts to avoid "accidental" bugs like this, by automatically running test suites, etc. Something much like the process that we use for Racket's git (except that in the case of Racket's git, the commits go in and *then* the tests run, not the other way around).<span><font color="#888888"><div> <br></div><div>Robby</div></font></span></div><div class="gmail_extra"><br><br><div class="gmail_quote"><div><div>On Thu, May 2, 2013 at 9:01 AM, Jay McCarthy <span dir="ltr"><<a href="mailto:jay.mccarthy@gmail.com" target="_blank">jay.mccarthy@gmail.com</a>></span> wrote:<br> </div></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div><div><div>On Thu, May 2, 2013 at 7:29 AM, Matthew Flatt <<a href="mailto:mflatt@cs.utah.edu" target="_blank">mflatt@cs.utah.edu</a>> wrote:<br> > [Jay will have to correct me if I have any part of this wrong...]<br> <br> </div>Nope, it was beautiful.<br> <div><br> > At Thu, 2 May 2013 11:31:09 +0200, Laurent wrote:<br> </div><div>> As an aside, the `raco pkg update' action is not restricted to packages<br> > installed by package name; it also works with GutHub sources. If you<br> > install via<br> ><br> > raco pkg install github://<a href="http://github.com/U/X/master" target="_blank">github.com/U/X/master</a><br> ><br> > then `raco pkg update' fetches the HEAD commit from GitHub. Again, that<br> > install or update doesn't interact with the catalog. But it doesn't also<br> > help if the repository's HEAD commit is buggy.<br> <br> </div>One little note, the part of this URL 'master' can refer to any branch<br> or tag. You could ask the developers to create a tag/branch for the<br> correct commit. Or you could fork their repository and then revert the<br> offending commit yourself (or create a tag, etc.) That's yet another<br> solution to the problem.<br> <span><font color="#888888"><br> Jay<br> </font></span><div><br> --<br> Jay McCarthy <<a href="mailto:jay@cs.byu.edu" target="_blank">jay@cs.byu.edu</a>><br> Assistant Professor / Brigham Young University<br> <a href="http://faculty.cs.byu.edu/~jay" target="_blank">http://faculty.cs.byu.edu/~jay</a><br> <br> "The glory of God is Intelligence" - D&C 93<br> </div></div></div><div><div><div>____________________<br> Racket Users list:<br> <a href="http://lists.racket-lang.org/users" target="_blank">http://lists.racket-lang.org/users</a><br> </div></div></div></blockquote></div><br></div> <br>____________________<br> Racket Users list:<br> <a href="http://lists.racket-lang.org/users" target="_blank">http://lists.racket-lang.org/users</a><br> <br></blockquote></div><br></div></div>