Done. It is named "MetacelloRepository" :) On 2009-12-07 10:28:05 -0300, Mariano Martinez Peck <[email protected]> said:
> > > On Mon, Dec 7, 2009 at 1:57 PM, Esteban Lorenzano > <[email protected]>wrot= > e: > >> 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. >> >> > I don't know if I like to put "Pharo" in the name. The idea of Metacello is > also to be able to easily port form one dialect to other. So, suppose I wan= > t > to create the ConfigurationOfFFI, maybe I will have something for #squeak > and something for #pharo or even for gemstone. > > So, I rather a name, not hardcoded to pharo, so that the configurations > there should have the conditions. > > I like MetacelloRepository. > > Best, > > Mariano > > Cheers, >> Esteban >> >> On 2009-12-05 07:27:25 -0300, St=E9phane 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=92m 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=92t fit with metacello and squeakmap even less. >>>> >>> >>>> So this is my idea (it is based on =93ibiblio=94 for maven/java and ap= > t-g >>> et >>> >>>> for ubuuntu): >>>> -we can create a project on squeaksource called >>> >>>> =93PharoMetacelloRepository=94, where people can put its public metace= > llo >>> >>>> configuration packages (for example ConfigurationOfSeaside30, >>> >>>> ConfigurationOfDeimos, etc.). >>>> -we should integrate metacello to pharo core (like Gofer now) >>>> -we=92ll need to create a new class =93Loader=94 >>>> >>> >>>> What =93Loader=94 does? it loads versions from =93metacello repositori= > es >>> =94, >>> >>>> for example: >>>> >>> >>>> Loader default latest: =91Seaside30=92. =93This will load latest versi= > on >>> of >>> >>>> ConfigurationOfSeaside30=92 >>>> >>> >>>> Loader class>>#default answers a loader pointing to >>> >>>> =93PharoMetacelloRepository=94, but you could define others (for your >>> >>>> private projects). >>>> >>> >>>> How Loader works? >>>> 1) validate loading a valid metacello configuration package (we=92ll n= > eed >>> >>>> to define this later >>>> 2) load metacello package >>>> 3) do something like =93MetacelloConfigurationClass project >>> >>>> loadLatestVersion=94 (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 thin= > k >>> >>>> on better repository places/formats later (but we will be =93on the ro= > ad >>> =94) >>>> >>> >>>> So, what do you think? >>>> >>> >>>> btw: If the community agree, I=92m 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 >> > > > <br><br><div class=3D"gmail_quote">On Mon, Dec 7, 2009 at 1:57 PM, Esteban = > Lorenzano <span dir=3D"ltr"><<a > href=3D"mailto:[email protected]";>este= > [email protected]</a>></span> > wrote:<br><blockquote class=3D"gmail_quote" = > style=3D"border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8= > ex; padding-left: 1ex;"> > Ok, that is all the blessing needed =A0:)<br> > I will start work on a first version of tools needed (there are not<br> > mutch at all) and I will upload a meta-package as soon as I have it<br> > working, to test it.<br> > On first stage, we will use a centralized repository on SqueakSource,<br> > and on second stage we can think on a more fashionable way to show the<br> > catalog :)<br> > <br> > About the SqueakSource repository, the name I first proposed<br> > (PharoMetacelloRepository) is not admited for SqueakSource (too large),<br> > so I need variants... what do you think?<br> > I have this in mind:<br> > <br> > -ConfigurationOfPharo<br> > -MetaPharo<br> > -MetacelloRepository<br> > <br> > I like the first one most, because it uses the same convention as the<br> > metacello suggested convention.<br> > <br></blockquote><div><br>I don't know if I like to put "Pharo&quo= > t; in the name. The idea of Metacello is also to be able to easily port for= > m one dialect to other. So, suppose I want to create the ConfigurationOfFFI= > , maybe I will have something for #squeak and something for #pharo or even = > for gemstone. <br> > <br>So, I rather a name, not hardcoded=A0 to pharo, so that the configurati= > ons there should have the conditions. <br><br>I like MetacelloRepository. <= > br><br>Best,<br><br>Mariano <br><br></div><blockquote class=3D"gmail_quote"= > style=3D"border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.= > 8ex; padding-left: 1ex;"> > > Cheers,<br> > Esteban<br> > <br> > On 2009-12-05 07:27:25 -0300, St=E9phane Ducasse<br> > <div><div></div><div class=3D"h5"><<a href=3D"mailto:stephane.duca...@in= > ria.fr">[email protected]</a>> said:<br> > <br> > > Hi lorenzo<br> > ><br> > > YES! we need a catalog in place of Universe package. I think that usin= > g mon<br> > > ticello as a way to store metacello config is the way to go.<br> > > We do not need to integrate metacello for now (even if the goal is to = > succe<br> > > ed to manage<br> > > Pharo with metacello). We could do Gofer loadMetacelloRepository or so= > methi<br> > > ng like that.<br> > > Then this is important because the testServer could also use this info= > rmati<br> > > on.<br> > ><br> > ><br> > > Stef<br> > ><br> > ><br> > > On Dec 4, 2009, at 7:32 PM, Esteban Lorenzano wrote:<br> > ><br> > >> Hi all,<br> > >> I=92m begining to transfer all my projects to metacello (I think t= > his is<br> > ><br> > >> the best package manager present today for pharo), and I have an i= > dea I<br> > ><br> > >> want to share and discuss:<br> > >><br> > ><br> > >> I think we need a metacello based centered repository.<br> > >><br> > ><br> > >> The universe doesn=92t fit with metacello and squeakmap even less.= > <br> > >><br> > ><br> > >> So this is my idea (it is based on =93ibiblio=94 for maven/java an= > d apt-g<br> > > et<br> > ><br> > >> for ubuuntu):<br> > >> -we can create a project on squeaksource called<br> > ><br> > >> =93PharoMetacelloRepository=94, where people can put its public me= > tacello<br> > ><br> > >> configuration packages (for example ConfigurationOfSeaside30,<br> > ><br> > >> ConfigurationOfDeimos, etc.).<br> > >> -we should integrate metacello to pharo core (like Gofer now)<br> > >> -we=92ll need to create a new class =93Loader=94<br> > >><br> > ><br> > >> What =93Loader=94 does? it loads versions from =93metacello reposi= > tories<br> > > =94,<br> > ><br> > >> for example:<br> > >><br> > ><br> > >> Loader default latest: =91Seaside30=92. =93This will load latest v= > ersion<br> > > of<br> > ><br> > >> ConfigurationOfSeaside30=92<br> > >><br> > ><br> > >> Loader class>>#default answers a loader pointing to<br> > ><br> > >> =93PharoMetacelloRepository=94, but you could define others (for y= > our<br> > ><br> > >> private projects).<br> > >><br> > ><br> > >> How Loader works?<br> > >> 1) validate loading a valid metacello configuration package (we=92= > ll need<br> > ><br> > >> to define this later<br> > >> 2) load metacello package<br> > >> 3) do something like =93MetacelloConfigurationClass project<br> > ><br> > >> loadLatestVersion=94 (for #latest), and the corresponding sends fo= > r<br> > ><br> > >> specific versions, etc.<br> > >><br> > ><br> > >> I think this will solve any package management problem, by using<b= > r> > ><br> > >> something already present (SqueakSource), and of course, we could = > think<br> > ><br> > >> on better repository places/formats later (but we will be =93on th= > e road<br> > > =94)<br> > >><br> > ><br> > >> So, what do you think?<br> > >><br> > ><br> > >> btw: If the community agree, I=92m offering my self to implement t= > his ide<br> > > a ;)<br> > >><br> > ><br> > >> Cheers,<br> > >> Esteban<br> > >><br> > ><br> > >><br> > ><br> > >><br> > ><br> > >> _______________________________________________<br> > >> Pharo-project mailing list<br> > >> <a > href=3D"mailto:[email protected]";>Pharo-proje= [email protected]</a><br> >> > > <a href=3D"http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/p= > haro-project" target=3D"_blank">http://lists.gforge.inria.fr/cgi-bin/mailma= > n/listinfo/pharo-project</a><br> > <br> > <br> > <br> > <br> > _______________________________________________<br> > Pharo-project mailing list<br> > <a > href=3D"mailto:[email protected]";>pharo-proj...@lists.= gforge.inria.fr</a><br> <a > > href=3D"http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-proj= > ect" target=3D"_blank">http://lists.gforge.inria.fr/cgi-bin/mailman/listinf= > o/pharo-project</a></div></div></blockquote></div><br> > > > > > _______________________________________________ > 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
