808bd1b897
Make `raco setup` propagate the original value of `use-compiled-file-paths` in case it's reset to avoid loading bytecode files. Then, `--clean` mode can remove bytecode relevant to that setting, instead of always clearing "compiled" subdirectories. There's no external way to initialize `use-compiled-file-paths` right now, other than forcing it to `null` with the `-c` flag at the `racket` level, but the current "racket7" implementation uses different `use-compiled-file-paths` settings for different build modes, and it seems to make sense in general. Also, make `--clean` sensitive to `-D` and `-d`, so that it's easy to clean just bytecode.
17 lines
330 B
Racket
17 lines
330 B
Racket
#lang info
|
|
|
|
(define collection 'multi)
|
|
|
|
(define deps '(["base" #:version "6.5.0.2"]
|
|
"scheme-lib"
|
|
"rackunit-lib"
|
|
"zo-lib"))
|
|
|
|
(define implies '("zo-lib"))
|
|
|
|
(define pkg-desc "implementation (no documentation) part of \"compiler\"")
|
|
|
|
(define pkg-authors '(mflatt))
|
|
|
|
(define version "1.7")
|