[racket-dev] A grab-bag of issues

From: Sam Tobin-Hochstadt (samth at ccs.neu.edu)
Date: Thu Jul 4 12:52:10 EDT 2013

All of these are about packages/the new repository organization.

0. I think we should have a new `#lang info` for info.rkt files --
`setup/infotab` seems pretty arbitrary.   I'll do this if no one

1. Builds treat too much as core. Specifically, `raco setup`
pre-builds some things single threaded, but too many:

raco setup: --- compiling collections ---
raco setup: making: <pkgs>/snip-lib/racket
raco setup: making: <pkgs>/sandbox-lib/racket
raco setup: making: <pkgs>/gui-lib/racket
raco setup: making: <pkgs>/draw-lib/racket
raco setup: making: <pkgs>/compatibility-lib/racket
raco setup: making: <collects>/racket
raco setup: --- parallel build using 8 processes ---

It can't really be the case that packages that aren't necessarily
installed need to be built first.

I think this can also happen with just building the core if other
packages are installed, but I haven't been able to reproduce that.

2. It's possible to get lots of undefined tags in the documentation
builds.  Should this be remedied with more build dependencies, or will
it be fixed with the online documentation server, or something else?

3. Rerunning `make` at the top-level loses the old set of PKGS
specified.  Should there be a `configure` setting for this to make it

4. The top-level build has no "cgc" targets.

5. GitHub recently introduced "Releases", which allow you to serve
arbitrary downloads. This might be useful for the "plt/libs"
repository.  More info here:
https://github.com/blog/1547-release-your-software . Even without
this, we might want to switch to downloading native packages as zip
files instead of requiring git to build from source.

6. Should the launchers for things like 'setup-plt' and 'mzc' move to

7. I think 'raco setup' should exit with a non-0 exit code when there
are dependency problems.

That's all for now.


Posted on the dev mailing list.