[squeak-dev] [Packages] Packages Team and List rejuvenated!
Keith Hodges
keith_hodges at yahoo.co.uk
Fri May 16 00:14:26 UTC 2008
Germán Arduino wrote:
> I'm asking again....then.....if I'm a user of SqueakMap, all will
> continue working?
Definitely.
> If I'm a user of Universes, all will continue working?
Yes
> If I don't have plans to use Sake/Install/etc.....can deatch of them?
Installer is designed to be the first dependency in a kernel image that
can be used to load everything else. So I would like to promote it's
inclusion in as many base images as possible. However it is purposefully
implemented as ONE class in order to make it very easy to remove.
Sake/Packages is also designed to be very easy to remove if it is
loaded. It is deigned to be able to load , use AND discard if you like
your images really lean.
> If I'm a Squeaker with not much time to be aware of all the news all
> the time, because must work on projects to pay the bills, I've option
> of ignoring this several ways of installations and packages?
of course, ignore away!
> If I develop my own software in the form of traditional Monticello
> .mcz packages, I can continue at this way?
Sake/Packages, SqueakMap, Installer and Universes all use Monticello so
yes you keep using Monticello as normal.
The easiest way to understand Sake/Packages is to think of it as the
same as Universes for loading and unloading Monticello packages that
have dependencies upon other packages. I believe that Sake/Packages is
better than Universes in many ways, but then I am totally biased since I
wrote it.
The significant difference between sake/packages and universes is that
the former is open to all, whereas universes can be updated only by
package maintainers. This means that sake/packages is likely to be more
agile, and up to date.
Currently there is an automatic task which updates Sake/Packages from
Universes and from SqueakMap. There is nothing preventing someone from
writing a task to go the other way in order to keep everything in sync.
(except of course Universes would have to be globally writable by the
person performing the update).
> Sorry if a lot of questions, but I'm a bit confused with all these new
> things related to packages.
>
no worries
Keith
More information about the Squeak-dev
mailing list
|