[plt-scheme] require planet packages, latest version?

From: Hans Oesterholt-Dijkema (hdnews at gawab.com)
Date: Mon Apr 30 17:29:13 EDT 2007

Yes, that worked. Thanks!
--Hans

Jacob Matthews schreef:
> Hi ---
>
> The PLaneT client keeps two caches: an per-mzscheme-minor-version
> "installed packages cache" that contains unpacked, compiled versions
> of your code, and a single "uninstalled packages cache" that contains
> raw .plt files. The idea was that planet would have a backup .plt file
> to unpack and compile in case you upgraded your mzscheme (say, from
> SVN update) and then tried to use planet packages on the train or a
> flight or something where you didn't have internet access. When I
> initially implemented this, the search order was (1) installed
> packages cache (2) uninstalled packages cache (3) internet. This meant
> you only went online when necessary, but in practice it seemed that
> people would rather have planet check online by default and only fall
> back to the uninstalled packages cache as a last resort. So, I changed
> it to behave that way, but I suspect I hadn't yet done so in version
> 360.
>
> In any event, you'll get the behavior you expect if you remove the
> package from your uninstalled packages cache; the command-line utility
> planet -e will do that for you.
>
> -jacob
>
>
> On 4/30/07, Hans Oesterholt-Dijkema <hdnews at gawab.com> wrote:
>> Yes, for instance.
>>
>>  >(require (planet "roos.scm" ("oesterholt" "roos.plt" 1 0)))
>>
>> planet -p
>> oesterholt roos.plt 1 5
>>
>> I must explicitly do:
>>
>>  >(require (planet "roos.scm" ("oesterholt" "roos.plt" 1 6)))
>>
>> to get the latest version.
>>
>> --hans
>>
>>
>>
>>
>> Robby Findler schreef:
>> > I think the timing of the uploading shouldn't factor into it. The
>> > latest version available (that matches the major version specified) is
>> > what the file gets locked into.
>> >
>> > Are you seeing different behavior?
>> >
>> > Robby
>> >
>> > On 4/30/07, Hans Oesterholt-Dijkema <hdnews at gawab.com> wrote:
>> >> Yes, I know,
>> >>
>> >> But, if I delete the package cache (or do something linke planet -u),
>> >> still package versions are loaded from planet. What should I expect
>> >> right after uploading a new version?
>> >>
>> >> --hans
>> >>
>> >>
>> >> Robby Findler schreef:
>> >> > No, it doesn't quite work like that. PLaneT gives you the latest
>> >> > package UNLESS you've already loaded an earlier verion with a
>> >> > particular file, in which case it will leave things along. The 
>> idea:
>> >> > no magic upgrades (which are bad idea). You have to ask 
>> specifically.
>> >> > To get the new version, change the require line to 1 1 (or clear 
>> the
>> >> > linkage table).
>> >> >
>> >> > See also the planet docs or the scheme workshop paper for more
>> >> > information.
>> >> >
>> >> > Robby
>> >> >
>> >> > On 4/30/07, Hans Oesterholt-Dijkema <hdnews at gawab.com> wrote:
>> >> >> L.S.,
>> >> >>
>> >> >> When I require planet packages, I see that I don't get the
>> >> >> last updated version of certain packages, while requiring them:
>> >> >>
>> >> >> (require (planet "sutil.scm" ("oesterholt" "ho-utils.plt" 1 0)))
>> >> >>
>> >> >> delivers version 1 0 instead of the last upload: 1 1
>> >> >>
>> >> >> I thought planet would download latest package?!
>> >> >>
>> >> >> --Hans
>> >> >>
>> >> >> _________________________________________________
>> >> >>   For list-related administrative tasks:
>> >> >>   http://list.cs.brown.edu/mailman/listinfo/plt-scheme
>> >> >>
>> >> >
>> >> >
>> >>
>> >>
>> >
>> >
>>
>> _________________________________________________
>>   For list-related administrative tasks:
>>   http://list.cs.brown.edu/mailman/listinfo/plt-scheme
>>
>
>



Posted on the users mailing list.