Interesting!
On Thu, May 2, 2013 at 4:20 PM, Jay McCarthy <[email protected]> wrote: > On Thu, May 2, 2013 at 8:18 AM, Laurent <[email protected]> wrote: > > 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? > > If you put a test suite in your package and register it on our > catalog, and your package is ring 0, then it will be run. > > > And if some test fails, the package will not be updated for those who run > > `raco pkg update` ? > > No, you will be dropped to ring 1 or 2 and your package will have a > warning on it. I hope to modify our update routine to notify you when > such a thing happens so that users can decide not to upgrade/install > your package. > > Jay > > > > > > > > > On Thu, May 2, 2013 at 4:11 PM, Robby Findler < > [email protected]> > > wrote: > >> > >> 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). > >> > >> Robby > >> > >> > >> On Thu, May 2, 2013 at 9:01 AM, Jay McCarthy <[email protected]> > >> wrote: > >>> > >>> On Thu, May 2, 2013 at 7:29 AM, Matthew Flatt <[email protected]> > wrote: > >>> > [Jay will have to correct me if I have any part of this wrong...] > >>> > >>> Nope, it was beautiful. > >>> > >>> > At Thu, 2 May 2013 11:31:09 +0200, Laurent wrote: > >>> > As an aside, the `raco pkg update' action is not restricted to > packages > >>> > installed by package name; it also works with GutHub sources. If you > >>> > install via > >>> > > >>> > raco pkg install github://github.com/U/X/master > >>> > > >>> > then `raco pkg update' fetches the HEAD commit from GitHub. Again, > that > >>> > install or update doesn't interact with the catalog. But it doesn't > >>> > also > >>> > help if the repository's HEAD commit is buggy. > >>> > >>> One little note, the part of this URL 'master' can refer to any branch > >>> or tag. You could ask the developers to create a tag/branch for the > >>> correct commit. Or you could fork their repository and then revert the > >>> offending commit yourself (or create a tag, etc.) That's yet another > >>> solution to the problem. > >>> > >>> Jay > >>> > >>> -- > >>> Jay McCarthy <[email protected]> > >>> Assistant Professor / Brigham Young University > >>> http://faculty.cs.byu.edu/~jay > >>> > >>> "The glory of God is Intelligence" - D&C 93 > >>> ____________________ > >>> Racket Users list: > >>> http://lists.racket-lang.org/users > >> > >> > >> > >> ____________________ > >> Racket Users list: > >> http://lists.racket-lang.org/users > >> > > > > > > -- > Jay McCarthy <[email protected]> > Assistant Professor / Brigham Young University > http://faculty.cs.byu.edu/~jay > > "The glory of God is Intelligence" - D&C 93 >
____________________ Racket Users list: http://lists.racket-lang.org/users

