Re: [racket-dev] raco pkg dependency checks and exit code

2013-10-03 Thread Asumu Takikawa
On 2013-10-03 06:45:12 -0600, Jay McCarthy wrote: > In the first case, you are forgetting to do it and we warn to tell you > what you should put. In the second case, you put them in but are wrong > and should be CAUGHT and PUNISHED. I think that's the logic behind it. That seems fair, but then in

Re: [racket-dev] raco pkg dependency checks and exit code

2013-10-03 Thread Matthew Flatt
At Thu, 3 Oct 2013 06:45:12 -0600, Jay McCarthy wrote: > On Wed, Oct 2, 2013 at 3:54 PM, Asumu Takikawa wrote: > > Hi all, > > > > I noticed that if you don't specify any dependencies for a package, then > > `raco` will warn you about that. However, the exit code is 0 and it's > > not an "error".

Re: [racket-dev] raco pkg dependency checks and exit code

2013-10-03 Thread Jay McCarthy
On Wed, Oct 2, 2013 at 3:54 PM, Asumu Takikawa wrote: > Hi all, > > I noticed that if you don't specify any dependencies for a package, then > `raco` will warn you about that. However, the exit code is 0 and it's > not an "error". > > Comparatively, if you supply a dependencies field of `empty`,

[racket-dev] raco pkg dependency checks and exit code

2013-10-02 Thread Asumu Takikawa
Hi all, I noticed that if you don't specify any dependencies for a package, then `raco` will warn you about that. However, the exit code is 0 and it's not an "error". Comparatively, if you supply a dependencies field of `empty`, then you will get a bunch of errors about undeclared dependencies a