> How does the universe knows OB is already in the image? Universe could easily find out if a newer version is loaded, but from what I know about Universe it deliberately doesn't do so. Universes is supposed to provide working sets of packages. If Universe would not insist on loading the older version, compatibility could not be guaranteed anymore. I think that behavior makes sense. Maybe a warning could be shown, that an older version will be loaded?
> As soon as Pharo switches to Sake and MC1.5, that will fix the problem > because everything uses PackageInfo to know what is installed. I don't > want to fix Universes knowing that a better system exists. Has this been decided yet? I hope there will be some discussion about this. I don't think Sake is better than Universe. It is just different. - Universes is declarative system, it declares the exact versions that are known to work together. No exceptions here, it loads the specified configuration with the specified dependencies. - Sake is an imperative system, it uses Installer to load versions. Installer either loads specific versions, or some version based on a query string. I agree that this is much more powerful, however there is no guarantee that all the packages that Installer thinks are the right versions also work together. In the end random versions of random packages from random repositories will be loaded in random order into your image. Does this solve the problem? I don't think so. Cheers, Lukas -- Lukas Renggli http://www.lukas-renggli.ch _______________________________________________ Pharo-project mailing list [email protected] http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
