A centralized repository (Going a step forward Gofer and Metacello)

> 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-get
> 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 idea ;)
>
> Cheers,
> Esteban
>
>
>
> _______________________________________________
> Pharo-project mailing list
> [hidden email]
> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

> 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
>> [hidden email]
>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

> 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

>
> 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
> <[hidden email]> 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
>>> [hidden email]
>>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
>
>
>
>
> _______________________________________________
> Pharo-project mailing list
> [hidden email]
> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

>
>
> On Mon, Dec 7, 2009 at 1:57 PM, Esteban Lorenzano
> <[hidden email]>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
>> <[hidden email]> 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
>>>> [hidden email]
>>>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
>>
>>
>>
>>
>> _______________________________________________
>> Pharo-project mailing list
>> [hidden email]
>> 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">&lt;<a
> href=3D"mailto:[hidden email]">este=
> [hidden email]</a>&gt;</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&#39;t know if I like to put &quot;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">&lt;<a href=3D"mailto:stephane.ducasse@in=
> ria.fr">[hidden email]</a>&gt; said:<br>
> <br>
> &gt; Hi lorenzo<br>
> &gt;<br>
> &gt; YES! we need a catalog in place of Universe package. I think that usin=
> g mon<br>
> &gt; ticello as a way to store metacello config is the way to go.<br>
> &gt; We do not need to integrate metacello for now (even if the goal is to =
> succe<br>
> &gt; ed to manage<br>
> &gt; Pharo with metacello). We could do Gofer loadMetacelloRepository or so=
> methi<br>
> &gt; ng like that.<br>
> &gt; Then this is important because the testServer could also use this info=
> rmati<br>
> &gt; on.<br>
> &gt;<br>
> &gt;<br>
> &gt; Stef<br>
> &gt;<br>
> &gt;<br>
> &gt; On Dec 4, 2009, at 7:32 PM, Esteban Lorenzano wrote:<br>
> &gt;<br>
> &gt;&gt; Hi all,<br>
> &gt;&gt; I=92m begining to transfer all my projects to metacello (I think t=
> his is<br>
> &gt;<br>
> &gt;&gt; the best package manager present today for pharo), and I have an i=
> dea I<br>
> &gt;<br>
> &gt;&gt; want to share and discuss:<br>
> &gt;&gt;<br>
> &gt;<br>
> &gt;&gt; I think we need a metacello based centered repository.<br>
> &gt;&gt;<br>
> &gt;<br>
> &gt;&gt; The universe doesn=92t fit with metacello and squeakmap even less.=
> <br>
> &gt;&gt;<br>
> &gt;<br>
> &gt;&gt; So this is my idea (it is based on =93ibiblio=94 for maven/java an=
> d apt-g<br>
> &gt; et<br>
> &gt;<br>
> &gt;&gt; for ubuuntu):<br>
> &gt;&gt; -we can create a project on squeaksource called<br>
> &gt;<br>
> &gt;&gt; =93PharoMetacelloRepository=94, where people can put its public me=
> tacello<br>
> &gt;<br>
> &gt;&gt; configuration packages (for example ConfigurationOfSeaside30,<br>
> &gt;<br>
> &gt;&gt; ConfigurationOfDeimos, etc.).<br>
> &gt;&gt; -we should integrate metacello to pharo core (like Gofer now)<br>
> &gt;&gt; -we=92ll need to create a new class =93Loader=94<br>
> &gt;&gt;<br>
> &gt;<br>
> &gt;&gt; What =93Loader=94 does? it loads versions from =93metacello reposi=
> tories<br>
> &gt; =94,<br>
> &gt;<br>
> &gt;&gt; for example:<br>
> &gt;&gt;<br>
> &gt;<br>
> &gt;&gt; Loader default latest: =91Seaside30=92. =93This will load latest v=
> ersion<br>
> &gt; of<br>
> &gt;<br>
> &gt;&gt; ConfigurationOfSeaside30=92<br>
> &gt;&gt;<br>
> &gt;<br>
> &gt;&gt; Loader class&gt;&gt;#default answers a loader pointing to<br>
> &gt;<br>
> &gt;&gt; =93PharoMetacelloRepository=94, but you could define others (for y=
> our<br>
> &gt;<br>
> &gt;&gt; private projects).<br>
> &gt;&gt;<br>
> &gt;<br>
> &gt;&gt; How Loader works?<br>
> &gt;&gt; 1) validate loading a valid metacello configuration package (we=92=
> ll need<br>
> &gt;<br>
> &gt;&gt; to define this later<br>
> &gt;&gt; 2) load metacello package<br>
> &gt;&gt; 3) do something like =93MetacelloConfigurationClass project<br>
> &gt;<br>
> &gt;&gt; loadLatestVersion=94 (for #latest), and the corresponding sends fo=
> r<br>
> &gt;<br>
> &gt;&gt; specific versions, etc.<br>
> &gt;&gt;<br>
> &gt;<br>
> &gt;&gt; I think this will solve any package management problem, by using<b=
> r>
> &gt;<br>
> &gt;&gt; something already present (SqueakSource), and of course, we could =
> think<br>
> &gt;<br>
> &gt;&gt; on better repository places/formats later (but we will be =93on th=
> e road<br>
> &gt; =94)<br>
> &gt;&gt;<br>
> &gt;<br>
> &gt;&gt; So, what do you think?<br>
> &gt;&gt;<br>
> &gt;<br>
> &gt;&gt; btw: If the community agree, I=92m offering my self to implement t=
> his ide<br>
> &gt; a ;)<br>
> &gt;&gt;<br>
> &gt;<br>
> &gt;&gt; Cheers,<br>
> &gt;&gt; Esteban<br>
> &gt;&gt;<br>
> &gt;<br>
> &gt;&gt;<br>
> &gt;<br>
> &gt;&gt;<br>
> &gt;<br>
> &gt;&gt; _______________________________________________<br>
> &gt;&gt; Pharo-project mailing list<br>
> &gt;&gt; <a
> href=3D"mailto:[hidden email]">Pharo-proje=

>
> <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:[hidden email]">Pharo-project@lists.=

>
> 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
> [hidden email]
> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

> 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
> <[hidden email]> 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
> >> [hidden email]
> >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
>
>
>
>
> _______________________________________________
> Pharo-project mailing list
> [hidden email]
> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

>
>
> On Mon, Dec 7, 2009 at 1:57 PM, Esteban Lorenzano <[hidden email]> wrote:
> 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 want 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éphane Ducasse
> <[hidden email]> 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
> >> [hidden email]
> >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
>
>
>
>
> _______________________________________________
> Pharo-project mailing list
> [hidden email]
> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
>
> _______________________________________________
> Pharo-project mailing list
> [hidden email]
> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project