[racket-dev] The Clark XML tests licensing

2012-03-08 Thread Sam Tobin-Hochstadt
Summary: we are currently violating the license of James Clark's XML test suite, and should fix this. Currently, the `tests/xml' directory [1] contains a comprehensive collection tests for XML parsing from James Clark [2]. The readme.html file [3] in that directory states the license of that

Re: [racket-dev] The Clark XML tests licensing

2012-03-08 Thread Sam Tobin-Hochstadt
On Thu, Mar 8, 2012 at 11:52 AM, Robby Findler ro...@eecs.northwestern.edu wrote: Doesn't file/gunzip do that? From the documentation, that seems to be about files that use gzip, not zip. I didn't think they were the same, but I don't know much about this stuff. Trying it, it doesn't seem to

Re: [racket-dev] The Clark XML tests licensing

2012-03-08 Thread Robby Findler
I think you want 'inflate'. IIUC, .zip files contain 'pkzip'-format compressed stuff. Robby On Thu, Mar 8, 2012 at 11:26 AM, Sam Tobin-Hochstadt sa...@ccs.neu.edu wrote: On Thu, Mar 8, 2012 at 11:52 AM, Robby Findler ro...@eecs.northwestern.edu wrote: Doesn't file/gunzip do that? From the

Re: [racket-dev] The Clark XML tests licensing

2012-03-08 Thread Robby Findler
Oh, but I see that this doesn't actually create the files. Probably something needs to be added to the library. Sorry. Robby On Thu, Mar 8, 2012 at 11:29 AM, Robby Findler ro...@eecs.northwestern.edu wrote: I think you want 'inflate'. IIUC, .zip files contain 'pkzip'-format compressed stuff.

Re: [racket-dev] The Clark XML tests licensing

2012-03-08 Thread Jay McCarthy
I think we should just use the system 'unzip', since we currently on test on platforms that have it anyways. DrDr has unzip and my machines do (I maintain XML.) I am also at fault for this, so I can fix it. Jay On 3/8/12, Matthew Flatt mfl...@cs.utah.edu wrote: We have a `file/zip' library

Re: [racket-dev] submodules

2012-03-08 Thread Jay McCarthy
I've made a test collecting macro. https://gist.github.com/2003201 test.rkt gives you 'define-test' (define-test id e ...) will create a module named 'test' that can see you local bindings (like module* #f) at the end of the module that contains all the code in e In addition, you get the

Re: [racket-dev] submodules

2012-03-08 Thread Jay McCarthy
One more thing, I anticipate that the 'main' module in my test.rkt will be raco test and I would extend it to allow you to give a directory that it will require (if present) all the test modules. You could also have Test button in DrRacket. Jay On Thu, Mar 8, 2012 at 1:29 PM, Jay McCarthy

Re: [racket-dev] submodules

2012-03-08 Thread Asumu Takikawa
This sounds great! I haven't tried it out yet, but here are some preliminary comments. On 2012-03-07 10:14:35 -0700, Matthew Flatt wrote: Submodules declared with `module' are declared locally while expanding a module body, which means that the submodules can be `require'd afterward by the

Re: [racket-dev] submodules

2012-03-08 Thread Jay McCarthy
On Thu, Mar 8, 2012 at 1:41 PM, Asumu Takikawa as...@ccs.neu.edu wrote: Maybe a pattern that could avoid this is to have something like #lang racket/main  #:main driver.rkt  #:tests tests.rkt which would bring in the given modules (in the filesystem) as submodules.  That way you could

Re: [racket-dev] submodules

2012-03-08 Thread Matthew Flatt
At Thu, 8 Mar 2012 15:41:38 -0500, Asumu Takikawa wrote: This sounds great! I haven't tried it out yet, but here are some preliminary comments. On 2012-03-07 10:14:35 -0700, Matthew Flatt wrote: Submodules declared with `module' are declared locally while expanding a module body, which

Re: [racket-dev] The Clark XML tests licensing

2012-03-08 Thread Jay McCarthy
I just committed a fix to this. Jay On Thu, Mar 8, 2012 at 12:06 PM, Jay McCarthy jay.mccar...@gmail.com wrote: I think we should just use the system 'unzip', since we currently on test on platforms that have it anyways. DrDr has unzip and my machines do (I maintain XML.) I am also at fault

Re: [racket-dev] submodules

2012-03-08 Thread Matthias Felleisen
Nice -- just what I wished for last spring. -- Matthias On Mar 8, 2012, at 3:39 PM, Jay McCarthy wrote: One more thing, I anticipate that the 'main' module in my test.rkt will be raco test and I would extend it to allow you to give a directory that it will require (if present) all the test

[racket-dev] odd error message in race setup

2012-03-08 Thread Matthias Felleisen
I compiled Git head a couple of hours ago and in the middle of my race setup run I found these: raco setup: 1 running: readline/readline.scrbl raco setup: 1 running: redex/redex.scrbl raco setup: 0 running: scribblings/reference/reference.scrbl The authenticity of host 'localhost (::1)'

Re: [racket-dev] odd error message in race setup

2012-03-08 Thread Neil Van Dyke
Robby Findler wrote at 03/08/2012 05:45 PM: Looks like something is trying to ssh while building the docs? Can whoever figures this out let the list know, or email me privately? Thanks. If it turns out that a use of SSH made it into a *released* version of Racket source, I might have to

Re: [racket-dev] odd error message in race setup

2012-03-08 Thread Neil Van Dyke
Probably mere coincidence, but GitHub has disclosed a security vulnerability of their service, which was exploited to target Rails developers and unnamed others: https://github.com/blog/1068-public-key-security-vulnerability-and-mitigation Neil Van Dyke wrote at 03/08/2012 06:32 PM: Robby

Re: [racket-dev] odd error message in race setup

2012-03-08 Thread Robby Findler
I think that the issue probably does not predate Kevin's recent push (distributed places). If you'd like to audit the push security concerns, I'm sure that'd be welcome. Robby On Thu, Mar 8, 2012 at 5:32 PM, Neil Van Dyke n...@neilvandyke.org wrote: Robby Findler wrote at 03/08/2012 05:45 PM:

Re: [racket-dev] odd error message in race setup

2012-03-08 Thread Kevin Tew
Its an example from the distributed places docs. I'll remove it. Kevin On 03/08/2012 06:00 PM, Robby Findler wrote: I think that the issue probably does not predate Kevin's recent push (distributed places). If you'd like to audit the push security concerns, I'm sure that'd be welcome. Robby