[ANN] Update streams for SqueakMap packages
Tim Rowledge
tim at sumeru.stanford.edu
Fri May 23 19:41:51 UTC 2003
"Andreas Raab" <andreas.raab at gmx.de> wrote:
> > ... for some bizarre reason my ftp URI had to be
> > ftp://tim@sumeru.stanford.edu//home/tim/WWW/pooters/SqFiles/pa
> > ckages/VMMaker <- note the double slash between the server
> > name and the path.
>
> The login for ftp is your home - so you were probably in /home/tim already
> and then trying to navigate to home/tim/...
Yah, that did it. Ta very much.
> > Once I finally got the URIs correct this actually worked. However, so
> > far as I can tell you have to have a package _loaded_ to see
> > its update streams. This is perfectly reasonable but not obvious
> > from the description. It caught me out....
>
> Check out the implementors of #includeUnloadedCardManagers.
No argument with the logic, just the documentation; I'll update the
swiki page with your original email doc and perhaps you can update the
package registration to point to http://minnow.cc.gatech.edu/squeak/3208
for future reference.
>
> > > Step 9: Posting 'real' updates
> >
> > It also removes the original file! I'm not at all sure I like that.
>
> No, it renames it to the actual name of the update (e.g., including the
> numeric prefix).
So it does. Good idea but non-inutitive so I'll just fix it in pubs.
>
> > I'd like to suggest that update files get put in the same place as the
> > chosen package download directory.
>
> There's a preference called #updatesSaveFile or so. Turn it on.
Almost does what I'd like. That would build a tree of
{default}/updates/{package}, which is not an awful idea but I propose
that {downloaddir}/{package}/updates would be better since it would keep
related files together. At the moment I don't see an obvious way for the
download directory to be found from the SMCard kept by the update
manager though.
tim
--
Tim Rowledge, tim at sumeru.stanford.edu, http://sumeru.stanford.edu/tim
My Go this amn keyboar oesn't have any 's.
More information about the Squeak-dev
mailing list
|