[racket] need to control PLaneT versions

On Aug 23, 2011, at 10:15 AM, Neil Van Dyke wrote:

> PLaneT issue I've mentioned this in the past, and it just bit me again...
> 
> For production systems that use PLaneT packages, we need a way for an application programmer to control the versions of *all* PLaneT packages -- including the ones pulled in indirectly, by dependencies from packages that we explicitly "require".  This is in addition to mechanisms for authenticating versions and auditing that I've mentioned before.
> 
> I loaded up some code for a production system into DrScheme 4.2.5 (to investigate a possible regression unrelated to PLaneT packages.  I did not have PLaneT linkages and caches for 4.2.5 on this machine.  DrScheme crunched for 15+ minutes while it was installing a bunch of PlaneT packages.  In addition to the PLaneT packages I expected, I noticed it started pulling in many packages from the impressive-looking "bzlib/" set, which this application does not use explicitly and has not pulled in in the past.  (Eventually DrScheme 4.2.5 exhausted all my RAM and was thrashing this swap-less system, probably thrashing disk caches in and out.)

I know that I'm not answering your more general question, and I think you may already know what I'm about to say, but the culprit here is almost certainly the schemeunit packages. The new sxml2 exists entirely to avoid this requirement, as you know.

John

-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 4624 bytes
Desc: not available
URL: <http://lists.racket-lang.org/users/archive/attachments/20110901/3db399f9/attachment.p7s>