My best understanding is that the problem is that path->pkg is used by "raco setup" to tell whether unstated dependencies are present. If files from collects/ are in a package, then everything needs to depend on "base" (which is inconvenient) including other files in collects/ but the files in collects/ aren't part of a package that has dependencies and "base" isn't actually considered installed (at least during the collects/ part.)
As mentioned, I also tried "racket" as the package, but that had a very similar (but slightly different) crash. Jay On Wed, Sep 3, 2014 at 6:22 PM, Sam Tobin-Hochstadt <sa...@cs.indiana.edu> wrote: > On Wed, Sep 3, 2014 at 10:53 AM, Jay McCarthy <j...@racket-lang.org> wrote: >> I need to revert this because it horribly breaks the bootstrapping >> phase. It may be possible to make the core have a package in the >> future, but it's not an easy change. > > Is this because code expects #f instead of "base"? Or for some other reason? > > Sam -- Jay McCarthy http://jeapostrophe.github.io "Wherefore, be not weary in well-doing, for ye are laying the foundation of a great work. And out of small things proceedeth that which is great." - D&C 64:33 _________________________ Racket Developers list: http://lists.racket-lang.org/dev
