On Tue, Jul 27, 2010 at 7:06 PM, Robby Findler <ro...@eecs.northwestern.edu>wrote:
> > I guess the idea is that you'd eliminate the syntactic difference > between a planet-located library and one in the distribution and then > require on some external source to know where the package is located? > Something like that? How would that work? > Hi Robby - there are a lot of ways to go about doing this; Jay pointed to some ideas. Here's one KISS approach without major changes (assuming the syntax have been unified): Modify the module path resolver so that it does the following lookup for non-versioned require specs: 1. try lookup the package in COLLECTS 2. if #1 fails, lookup the package in planet cache 3. if #2 fails, lookup the package in planet repo For the versioned specs, you can skip the collects step above since it is currently not versioned. But of course you can also change collects to become versionable in the future if you wish to re-architect the system. Cheers, yc
_________________________________________________ For list-related administrative tasks: http://lists.racket-lang.org/listinfo/dev
