[plt-dev] Re: Generated files and co-existing copies of DrScheme

From: Carl Eastlund (cce at ccs.neu.edu)
Date: Fri Nov 20 09:14:59 EST 2009

On Fri, Nov 20, 2009 at 9:05 AM, Robby Findler
<robby at eecs.northwestern.edu> wrote:
> On Fri, Nov 20, 2009 at 7:50 AM, Carl Eastlund <cce at ccs.neu.edu> wrote:
>> Pardon my pre-morning-coffee thinking.  There were a few mistakes here:
>> On Fri, Nov 20, 2009 at 8:35 AM, Carl Eastlund <cce at ccs.neu.edu> wrote:
>>>> 3. IIUC, the only problem that this solves is using several different
>>>>   installations with the same version number, is this true?  Is that
>>>>   problem *so* common?  If so, then maybe have instead a way to use
>>>>   your own additional suffix to the version part that gets used in
>>>>   ~/.plt-scheme/<here>/ and ~/.plt-scheme/planet/300/<here>/ ?
>>> I run into this problem every single day when I update my PLT trunk
>>> checkout.  I either have to spend the duration of a complete build
>>> (including all documentation, installed planet packages, and recovery
>>> from any build errors) unable to run any PLT Scheme code of any
>>> variety -- essentially unable to work -- or I need some way to have
>>> two PLT Scheme installations of the same version that don't "share"
>>> compiled planet code.
>> The above describes the problem I run into in general, much of which
>> is alleviated by PLTPLANETDIR.  I still have the problem of clashing
>> docs, so I can't run Help Desk in the interim and I'm stuck with the
>> newest version afterword.  However I am able to run mzscheme,
>> drscheme, planet, setup-plt, etc.
> Not to be contrarian, but pre-relase docs are probably close enough
> usually, right?

Unfortunately, the new docs invariably lack planet packages (both
downloaded and development linked).  I spend a lot of time programming
with planet code, and looking up documentation for it, and without
up-to-date local documentation I wind up having to go to
planet.plt-scheme.org and lookup documentation by browsing specific
versions of each package, without the benefit of Help Desk's search


Posted on the dev mailing list.