[racket] info.rkt `deps` (was: Package fails to compile during 'make in-place' but not 'raco pkg install')

From: Sam Tobin-Hochstadt (samth at cs.indiana.edu)
Date: Fri Dec 20 16:08:43 EST 2013

On Fri, Dec 20, 2013 at 4:04 PM, Greg Hendershott
<greghendershott at gmail.com> wrote:
> On Fri, Dec 20, 2013 at 3:39 PM, Sam Tobin-Hochstadt
> <samth at cs.indiana.edu> wrote:
>> It's not collections that need to be specified, just packages. Here
>> are the missing dependencies for "markdown", for example, as printed
>> out by `raco setup`:
>> raco setup: undeclared dependency detected
>> raco setup:   for package: "markdown"
>> raco setup:   on packages:
>> raco setup:    "base"
>> raco setup:    "sandbox-lib"
>> raco setup:    "scribble-lib"
>> raco setup:    "srfi-lite-lib"
>> raco setup:   on packages for build:
>> raco setup:    "at-exp-lib"
>> raco setup:    "html-lib"
>> raco setup:    "rackunit-lib"
>> raco setup:    "redex-lib"
> Hmm. I don't see that output here:
> https://travis-ci.org/greghendershott/markdown/jobs/14812080
> Does `raco setup` not show this when run as part of `raco pkg install`?

Yes, in fact that difference is the topic of the message from Matthew
that you replied to when starting this sub-thread. ;)

On Fri, Dec 20, 2013 at 12:42 PM, Matthew Flatt <mflatt at cs.utah.edu> wrote:
> Dependency checking is currently implemented in a non-scalable way, so
> it only runs in global setup modes. Running `make in-place` ends with a
> global setup. When you install a package, in contrast, only the
> package's collections are set up (roughly), and dependency checking
> doesn't happen.


Posted on the users mailing list.