Ok, that is all the blessing needed :) I will start work on a first version of tools needed (there are not mutch at all) and I will upload a meta-package as soon as I have it working, to test it. On first stage, we will use a centralized repository on SqueakSource, and on second stage we can think on a more fashionable way to show the catalog :)
About the SqueakSource repository, the name I first proposed (PharoMetacelloRepository) is not admited for SqueakSource (too large), so I need variants... what do you think? I have this in mind: -ConfigurationOfPharo -MetaPharo -MetacelloRepository I like the first one most, because it uses the same convention as the metacello suggested convention. Cheers, Esteban On 2009-12-05 07:27:25 -0300, Stéphane Ducasse <[email protected]> said: > Hi lorenzo > > YES! we need a catalog in place of Universe package. I think that using mon > ticello as a way to store metacello config is the way to go. > We do not need to integrate metacello for now (even if the goal is to succe > ed to manage > Pharo with metacello). We could do Gofer loadMetacelloRepository or somethi > ng like that. > Then this is important because the testServer could also use this informati > on. > > > Stef > > > On Dec 4, 2009, at 7:32 PM, Esteban Lorenzano wrote: > >> Hi all, >> I’m begining to transfer all my projects to metacello (I think this is > >> the best package manager present today for pharo), and I have an idea I > >> want to share and discuss: >> > >> I think we need a metacello based centered repository. >> > >> The universe doesn’t fit with metacello and squeakmap even less. >> > >> So this is my idea (it is based on “ibiblio” for maven/java and apt-g > et > >> for ubuuntu): >> -we can create a project on squeaksource called > >> “PharoMetacelloRepository”, where people can put its public metacello > >> configuration packages (for example ConfigurationOfSeaside30, > >> ConfigurationOfDeimos, etc.). >> -we should integrate metacello to pharo core (like Gofer now) >> -we’ll need to create a new class “Loader” >> > >> What “Loader” does? it loads versions from “metacello repositories > ”, > >> for example: >> > >> Loader default latest: ‘Seaside30’. “This will load latest version > of > >> ConfigurationOfSeaside30’ >> > >> Loader class>>#default answers a loader pointing to > >> “PharoMetacelloRepository”, but you could define others (for your > >> private projects). >> > >> How Loader works? >> 1) validate loading a valid metacello configuration package (we’ll need > >> to define this later >> 2) load metacello package >> 3) do something like “MetacelloConfigurationClass project > >> loadLatestVersion” (for #latest), and the corresponding sends for > >> specific versions, etc. >> > >> I think this will solve any package management problem, by using > >> something already present (SqueakSource), and of course, we could think > >> on better repository places/formats later (but we will be “on the road > ”) >> > >> So, what do you think? >> > >> btw: If the community agree, I’m offering my self to implement this ide > a ;) >> > >> Cheers, >> Esteban >> > >> > >> > >> _______________________________________________ >> 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
