Hi Damien, Let me try to understand your suggestion. You would use Sacke-Packages instead of a Universe. As far as I see, a Sacke-Package models the same information as one in a Universe (that is, name, description, dependencies, source location, etc.), right? Hence, the main difference is that this information can be managed with MC instead of a XML. Furthermore, as you suggest, we could share package definitions between different Pharo versions and even between Pharo and Squeak.
Questions: - Is there a GUI frontend for Sack-Packages like for Universes? I think some way is needed to allow people more easily browser the provided packages. If it didn't exist, which I expect, I assume it would not be hard to build one. - How do users that already have installed Sacke-Packages (I guess we would pre-install it in the Pharo distro), get the most recent version of the package definitions? Obviously, they should always automatically get the most recent one. - How would you manage the differences between Squeak and Pharo universes? I think it is extremely important that the Pharo-1.0 universe contains only stable and working packages that do not conflict. I don't want to see unstable packages or packages that in some combinations do not load. Therefore, I don't think that managing a separate universe for Pharo is that much more work since the main work is to make sure that the packages that are added conform to our high standards. Cheers, Adrian BTW, when I try to install Seaside in Pharo using Packages I get the following error: PackageInfo>>doesNotUnderstand: #propertyAt:put: On Dec 22, 2008, at 10:35 , Damien Cassou wrote: > On Sat, Dec 20, 2008 at 11:16 AM, Adrian Lienhard <[email protected]> > wrote: >> In a recent discussion with Marcus and Lukas we came to the >> conclusion >> that a package universe for Pharo 1.0 would be the best solution. > > As the main maintainer of the dev Universe for Squeak 3.9-3.10 and > Pharo, I have to disagree. Having a separate Universe for Pharo will > be a pain. For each new version of a package, I will have to publish > it to both the dev Universe and the Pharo universe. I advise you to > use Packages instead for which subclassing is possible between > distributions. That way, I could update one class and the other is > automatically updated. Packages loads very easily inside Pharo and > does not require overrides. > > Installer install: 'Packages' > > Have a look at the script here: http://installer.pbwiki.com/Packages-Pharo0:1 > > -- > Damien Cassou > http://damiencassou.seasidehosting.st > > _______________________________________________ > Pharo-project mailing list > [email protected] > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project _______________________________________________ Pharo-project mailing list [email protected] http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
