> Probably that is the easiest solution. > Most of the time we did not rely on the dependencies because I'm not sure that the order can be specified. I think that in the future we will use metacello to resolve this ordering.
> I'm just a bit lost in what is the preferred way of expressing package > dependencies and loading process. I see Monticello's package > dependencies but I also see specifically created load scripts and > things like Flair and Gofer. Flair was a parallel track to get a kind of metacello system. It will disappear. Gofer is a simple interface to replace Installer and metacello will use it to load and script loading of packages. > I'm rediscovering development in Pharo-Squeak (I have been mostly > working in Visualworks the last 5 years). So perhaps I'm asking a > silly question that does not make sense? ;-) No the problem is that we are also inventing new ways of managing our artefacts. Stef _______________________________________________ Pharo-project mailing list [email protected] http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
