On Fri, Sep 26, 2008 at 8:38 AM, Lukas Renggli <renggli@gmail.com> wrote:
One problem I see with Sake/Packages is that these tools depend on a lot of other packages, that I don't necessarily want to have loaded in my images: Logging, Rio, Installer, Sake, Packages ...
I guess one could argue the same with XML and Universe.
This is the only argument against Sake/Packages I guess. Keith, could you please give us more information on that? - what mcz do we need to load exactly to have universes features using Sake/Packages? - is LPF necessary?
You can define a package with non-specific versions, i.e. to load the latest seaside when keeping up with the bleeding edge.
This sounds very suspicious. That can't reliably work with standard Monticello, all projects I know use multiple branches at some point.
Keith does not mean you *must* use it :-). This is a feature that can be useful for some small packages.
I agree that Universes is not the ultimate solution, but at least it seems to work reasonably well. I like the declarative way to specifying package dependencies.
Sake/Packages is just about that: a declarative way to specify packages. Nothing more. And there is a script which converts a Universe to a set of tasks. It works very well and Keith uses it often to update Packages from Universes. An example for PierBlog: PackagesSqueak310U>>PierBlog self name: 'Pier-Blog'. self version: '1.0.16.73'. info category: 'Web Development'. info description: 'Pier blog plugin.'. info maintainer: 'Lukas Renggli <renggli@gmail.com>'. info homepage: 'http://www.lukas-renggli.ch/smalltalk/pier'. info squeakMapID: ''. info url: 'http://mc.lukas-renggli.ch/pier/Pier-Blog-lr.73.mcz'. self provides: #(). self dependsOn: #('Pier-Seaside' 'RSRSS2'). self load: [ Installer installUrl:'http://mc.lukas-renggli.ch/pier/Pier-Blog-lr.73.mcz'. ]. self unload: [ Installer mc unload: 'Pier-Blog'. ]. -- Damien Cassou Peter von der Ahé: «I'm beginning to see why Gilad wished us good luck». (http://blogs.sun.com/ahe/entry/override_snafu)