On Jul 6, Petey Aldous wrote: > That would be interesting and it would not be terribly difficult to > instrument setup-plt to do it.
There's no reason to do that -- the data is all there in the dep
files. It just needs to be trimmed for the collection name instead of
the full paths.
I'm attaching a file with a list of all toplevel collections and a has
table that maps collection names to what they depend on. I tried to
visualize this with graphviz in a number of ways -- and there was
nothing that producing a graph that would make sense. I then wrote
some code and there's two groups of collections -- one huge ball of
code that is all inter-dependent, and then a bunch of collections that
are nearly free of dependency problems. The only problem in the
latter group is teachpacks and deinprogramm which form a cycle.
So, the unproblematic set of collects is:
2htdp, afm, algol60, combinator-parser, datalog, defaults,
embedded-gui, eopl, frtime, gui-debugger, guibuilder, handin-client,
handin-server, hierlist, honu, lazy, macro-debugger, make, mysterx,
mzcom, plai, plot, preprocessor, racklog, redex, repo-time-stamp,
schemeunit, sgl, sirmail, slatex, srpersist, swindle,
test-box-recovery, tex2page, waterworld, games, tests, meta
it would work fine to install them one by one in this order, except
for {teachpack, deinprogramm} which are their own set.
The problematic set of collects is:
racket, at-exp, browser, compiler, config, drracket, drscheme,
dynext, errortrace, ffi, file, framework, graphics, help, htdp,
html, icons, lang, launcher, mred, mrlib, mzlib, mzscheme, net,
openssl, parser-tools, planet, profile, r5rs, r6rs, rackunit, raco,
reader, readline, rnrs, s-exp, scheme, scribble, scribblings,
scriblib, setup, slideshow, srfi, stepper, string-constants, syntax,
syntax-color, test-engine, texpict, trace, typed, typed-scheme,
unstable, version, web-server, wxme, xml
deps.rktd
Description: Binary data
--
((lambda (x) (x x)) (lambda (x) (x x))) Eli Barzilay:
http://barzilay.org/ Maze is Life!
_________________________________________________ For list-related administrative tasks: http://lists.racket-lang.org/listinfo/dev
