[ANN] Metacello configurations for Pharo.

>
>
> (Sorry for the long email)
>
> Yes, after a couple of weeks, I have written most of the needed Metacello
> configurations for the Dev images 1.0. Forget 1.1 for a while. Now we are
> able to:
>
> 1) Load stable version of packages
> 2) Manage the dependencies automatically
> 3) Each developer can create its custom PharoDev image
> 4) Flexibility to load the packages you want
> 5) Choose the browser for example: OB or O2
> 6) Choose to load the tests or not
> 7) Load each package in a PharoCore image without having to install anything
> else (all the dependencies should be managed automatically)
> 8) You can take a PharoCore image and "transform" it to a Dev image, or even
> web.
> 9) Others...
>
> This is not completed yet. There are some things that we are discussing with
> Dale, but they are ok as a first step. I rather go step by step.
>
> What I did is to create all the infrastructure:
>
> a) The Configuration classes
> b) The dependencies
> c)  the groups,
>
> In summary, most of the "structure" and static information. However, I am
> not sure which version to load of each package. I will probable take care of
> building the Dev images, but I won't:
>
> - Merge anything. It will not be my task to merge OB, or RB or whatever.
> - Check every version of each package before doing a release to see if it is
> stable or not.
>
> So...what I REALLY (actually, WE) need is that each developer, each
> maintainer of the packages that we load of a PharoDev image, help us to
> create the stable versions. To create a new version for the Metacello
> configuration is VERY easy, The hard part is already done. You just have to
> create a method and say which versions (except you create or eliminate
> packages or dependencies). If you read the code, you will probably
> understand it. However, you can read the Metacello tutorial (no more than
> one hour), or ask me or even more in the Metacello mailing list.
> So...PLEASE, I need the help of the maintainers to create the versions. So
> far, I created the first version (1.0) with the latest version. But the idea
> is that then you create 1.1.1 or 1.2 or whatever you consider.
>
> All the configurations can be found in
> http://www.squeaksource.com/MetacelloRepository
>
> So far, I created:  ConfigurationOfNewInspector, ConfigurationOfOCompletion,
> ConfigurationOfOmniBrowser, ConfigurationOfPharoMorphicExtras,
> ConfigurationOfPharoSound, ConfigurationOfRefactoringBrowser,
> ConfigurationOfShout , and......ConfigurationOfPharo!!!
>
> To install them, just download that package and evaluate the load. Example:
>
> Gofer new
>     squeaksource: 'MetacelloRepository';
>     package: 'ConfigurationOfShout';
>     load.
>
> ((Smalltalk at: #ConfigurationOfShout) project version: '1.0') load.
>
> And then, you can also for exaple do:
>
> ((Smalltalk at: #ConfigurationOfShout) project version: '1.0') load: 'Core'
>
> this doesn't install the tests.
>
> Or for example:  (ConfigurationOfOmniBrowser project version: '1.0') load:
> 'Dev'
>
> etc...
>
> So, you can load any project and with the group you want. All of that can be
> (or should be hahahaha) perfectly loaded in a 1.0 Core image.
>
> What I would really appreciate is if each maintainer can look at the code,
> load the different groups and give me feedback on the dependencies or
> whatever.
>
> I really wait your feedback.
>
> Mariano
>
> ps:  I will release soon the first dev image using this :)
>
>
> (Sorry for the long email)<br><br>Yes, after a couple of weeks, I have writ=
> ten most of the needed Metacello configurations for the Dev images 1.0. For=
> get 1.1 for a while. Now we are able to:<br><br>1) Load stable version of p=
> ackages<br>
> 2) Manage the dependencies automatically<br>3) Each developer can create it=
> s custom PharoDev image<br>
> 4) Flexibility to load the packages you want<br>5) Choose the browser for e=
> xample: OB or O2<br>6) Choose to load the tests or not<br>7) Load each pack=
> age in a PharoCore image without having to install anything else (all the d=
> ependencies should be managed automatically)<br>
>
> 8) You can take a PharoCore image and &quot;transform&quot; it to a Dev ima=
> ge, or even web. <br>9) Others...<br><br>This is not completed yet. There a=
> re some things that we are discussing with Dale, but they are ok as a first=
>  step. I rather go step by step. <br>
> <br>What I did is to create all the infrastructure:<br><br>a) The Configura=
> tion classes<br>b) The dependencies <br>
> c)=A0 the groups,<br><br>In summary, most of the &quot;structure&quot; and =
> static information. However, I am not sure which version to load of each pa=
> ckage. I will probable take care of building the Dev images, but I won&#39;=
> t:<br>
>
> <br>- Merge anything. It will not be my task to merge OB, or RB or whatever=
> .<br>- Check every version of each package before doing a release to see if=
>  it is stable or not.<br><br>So...what I REALLY (actually, WE) need is that=
>  each developer, each maintainer of the packages that we load of a PharoDev=
>  image, help us to create the stable versions. To create a new version for =
> the Metacello configuration is VERY easy, The hard part is already done. Yo=
> u just have to create a method and say which versions (except you create or=
>  eliminate packages or dependencies). If you read the code, you will probab=
> ly understand it. However, you can read the Metacello tutorial (no more tha=
> n one hour), or ask me or even more in the Metacello mailing list. So...PLE=
> ASE, I need the help of the maintainers to create the versions. So far, I c=
> reated the first version (1.0) with the latest version. But the idea is tha=
> t then you create 1.1.1 or 1.2 or whatever you consider.<br>
> <br>All the configurations can be found in <a href=3D"http://www.squeaksour=
> ce.com/MetacelloRepository">http://www.squeaksource.com/MetacelloRepository=
> </a><br><br>So far, I created:=A0 ConfigurationOfNewInspector, Configuratio=
> nOfOCompletion, ConfigurationOfOmniBrowser, ConfigurationOfPharoMorphicExtr=
> as, ConfigurationOfPharoSound, ConfigurationOfRefactoringBrowser, Configura=
> tionOfShout , and......ConfigurationOfPharo!!!<br>
> <br>To install them, just download that package and evaluate the load. Exam=
> ple:<br><br>Gofer new<br>=A0=A0=A0 squeaksource: &#39;MetacelloRepository&#=
> 39;;<br>=A0=A0=A0 package: &#39;ConfigurationOfShout&#39;;<br>=A0=A0=A0 loa=
> d.<br><br>((Smalltalk at: #ConfigurationOfShout) project version: &#39;1.0&=
> #39;) load.<br>
> <br>And then, you can also for exaple do:=A0 <br><br>
> ((Smalltalk at: #ConfigurationOfShout) project version: &#39;1.0&#39;) load=
> : &#39;Core&#39;=A0 <br>this doesn&#39;t install the tests. <br><br>Or for =
> example:=A0 (ConfigurationOfOmniBrowser project version: &#39;1.0&#39;) loa=
> d: &#39;Dev&#39;<br>
> <br>etc...<br><br>So, you can load any project and with the group you want.=
>  All of that can be (or should be hahahaha) perfectly loaded in a 1.0 Core =
> image.<br><br>What I would really appreciate is if each maintainer can look=
>  at the code, load the different groups and give me feedback on the depende=
> ncies or whatever.<br>
> <br>I really wait your feedback. <br><br>Mariano<br><br>ps:=A0 I will relea=
> se soon the first dev image using this :)<br>
> <br>
>
>
>
>
> _______________________________________________
> Pharo-project mailing list
> [hidden email]
> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

> btw, ConfigurationOfPharo shouldn't be ConfigurationOfPharoDev?
>
> On 2010-01-07 17:54:27 -0300, Mariano Martinez Peck
> <[hidden email]> said:
>
>>
>>
>> (Sorry for the long email)
>>
>> Yes, after a couple of weeks, I have written most of the needed  
>> Metacello
>> configurations for the Dev images 1.0. Forget 1.1 for a while. Now  
>> we are
>> able to:
>>
>> 1) Load stable version of packages
>> 2) Manage the dependencies automatically
>> 3) Each developer can create its custom PharoDev image
>> 4) Flexibility to load the packages you want
>> 5) Choose the browser for example: OB or O2
>> 6) Choose to load the tests or not
>> 7) Load each package in a PharoCore image without having to install  
>> anything
>> else (all the dependencies should be managed automatically)
>> 8) You can take a PharoCore image and "transform" it to a Dev  
>> image, or even
>> web.
>> 9) Others...
>>
>> This is not completed yet. There are some things that we are  
>> discussing with
>> Dale, but they are ok as a first step. I rather go step by step.
>>
>> What I did is to create all the infrastructure:
>>
>> a) The Configuration classes
>> b) The dependencies
>> c)  the groups,
>>
>> In summary, most of the "structure" and static information.  
>> However, I am
>> not sure which version to load of each package. I will probable  
>> take care of
>> building the Dev images, but I won't:
>>
>> - Merge anything. It will not be my task to merge OB, or RB or  
>> whatever.
>> - Check every version of each package before doing a release to see  
>> if it is
>> stable or not.
>>
>> So...what I REALLY (actually, WE) need is that each developer, each
>> maintainer of the packages that we load of a PharoDev image, help  
>> us to
>> create the stable versions. To create a new version for the Metacello
>> configuration is VERY easy, The hard part is already done. You just  
>> have to
>> create a method and say which versions (except you create or  
>> eliminate
>> packages or dependencies). If you read the code, you will probably
>> understand it. However, you can read the Metacello tutorial (no  
>> more than
>> one hour), or ask me or even more in the Metacello mailing list.
>> So...PLEASE, I need the help of the maintainers to create the  
>> versions. So
>> far, I created the first version (1.0) with the latest version. But  
>> the idea
>> is that then you create 1.1.1 or 1.2 or whatever you consider.
>>
>> All the configurations can be found in
>> http://www.squeaksource.com/MetacelloRepository
>>
>> So far, I created:  ConfigurationOfNewInspector,  
>> ConfigurationOfOCompletion,
>> ConfigurationOfOmniBrowser, ConfigurationOfPharoMorphicExtras,
>> ConfigurationOfPharoSound, ConfigurationOfRefactoringBrowser,
>> ConfigurationOfShout , and......ConfigurationOfPharo!!!
>>
>> To install them, just download that package and evaluate the load.  
>> Example:
>>
>> Gofer new
>>    squeaksource: 'MetacelloRepository';
>>    package: 'ConfigurationOfShout';
>>    load.
>>
>> ((Smalltalk at: #ConfigurationOfShout) project version: '1.0') load.
>>
>> And then, you can also for exaple do:
>>
>> ((Smalltalk at: #ConfigurationOfShout) project version: '1.0')  
>> load: 'Core'
>>
>> this doesn't install the tests.
>>
>> Or for example:  (ConfigurationOfOmniBrowser project version:  
>> '1.0') load:
>> 'Dev'
>>
>> etc...
>>
>> So, you can load any project and with the group you want. All of  
>> that can be
>> (or should be hahahaha) perfectly loaded in a 1.0 Core image.
>>
>> What I would really appreciate is if each maintainer can look at  
>> the code,
>> load the different groups and give me feedback on the dependencies or
>> whatever.
>>
>> I really wait your feedback.
>>
>> Mariano
>>
>> ps:  I will release soon the first dev image using this :)
>>
>>
>> (Sorry for the long email)<br><br>Yes, after a couple of weeks, I  
>> have writ=
>> ten most of the needed Metacello configurations for the Dev images  
>> 1.0. For=
>> get 1.1 for a while. Now we are able to:<br><br>1) Load stable  
>> version of p=
>> ackages<br>
>> 2) Manage the dependencies automatically<br>3) Each developer can  
>> create it=
>> s custom PharoDev image<br>
>> 4) Flexibility to load the packages you want<br>5) Choose the  
>> browser for e=
>> xample: OB or O2<br>6) Choose to load the tests or not<br>7) Load  
>> each pack=
>> age in a PharoCore image without having to install anything else  
>> (all the d=
>> ependencies should be managed automatically)<br>
>>
>> 8) You can take a PharoCore image and &quot;transform&quot; it to a  
>> Dev ima=
>> ge, or even web. <br>9) Others...<br><br>This is not completed yet.  
>> There a=
>> re some things that we are discussing with Dale, but they are ok as  
>> a first=
>> step. I rather go step by step. <br>
>> <br>What I did is to create all the infrastructure:<br><br>a) The  
>> Configura=
>> tion classes<br>b) The dependencies <br>
>> c)=A0 the groups,<br><br>In summary, most of the  
>> &quot;structure&quot; and =
>> static information. However, I am not sure which version to load of  
>> each pa=
>> ckage. I will probable take care of building the Dev images, but I  
>> won&#39;=
>> t:<br>
>>
>> <br>- Merge anything. It will not be my task to merge OB, or RB or  
>> whatever=
>> .<br>- Check every version of each package before doing a release  
>> to see if=
>> it is stable or not.<br><br>So...what I REALLY (actually, WE) need  
>> is that=
>> each developer, each maintainer of the packages that we load of a  
>> PharoDev=
>> image, help us to create the stable versions. To create a new  
>> version for =
>> the Metacello configuration is VERY easy, The hard part is already  
>> done. Yo=
>> u just have to create a method and say which versions (except you  
>> create or=
>> eliminate packages or dependencies). If you read the code, you will  
>> probab=
>> ly understand it. However, you can read the Metacello tutorial (no  
>> more tha=
>> n one hour), or ask me or even more in the Metacello mailing list.  
>> So...PLE=
>> ASE, I need the help of the maintainers to create the versions. So  
>> far, I c=
>> reated the first version (1.0) with the latest version. But the  
>> idea is tha=
>> t then you create 1.1.1 or 1.2 or whatever you consider.<br>
>> <br>All the configurations can be found in <a href=3D"http://www.squeaksour 
>> =
>> ce.com/MetacelloRepository">http://www.squeaksource.com/MetacelloRepository=
>> </a><br><br>So far, I created:=A0 ConfigurationOfNewInspector,  
>> Configuratio=
>> nOfOCompletion, ConfigurationOfOmniBrowser,  
>> ConfigurationOfPharoMorphicExtr=
>> as, ConfigurationOfPharoSound, ConfigurationOfRefactoringBrowser,  
>> Configura=
>> tionOfShout , and......ConfigurationOfPharo!!!<br>
>> <br>To install them, just download that package and evaluate the  
>> load. Exam=
>> ple:<br><br>Gofer new<br>=A0=A0=A0 squeaksource:  
>> &#39;MetacelloRepository&#=
>> 39;;<br>=A0=A0=A0 package:  
>> &#39;ConfigurationOfShout&#39;;<br>=A0=A0=A0 loa=
>> d.<br><br>((Smalltalk at: #ConfigurationOfShout) project version:  
>> &#39;1.0&=
>> #39;) load.<br>
>> <br>And then, you can also for exaple do:=A0 <br><br>
>> ((Smalltalk at: #ConfigurationOfShout) project version:  
>> &#39;1.0&#39;) load=
>> : &#39;Core&#39;=A0 <br>this doesn&#39;t install the tests.  
>> <br><br>Or for =
>> example:=A0 (ConfigurationOfOmniBrowser project version:  
>> &#39;1.0&#39;) loa=
>> d: &#39;Dev&#39;<br>
>> <br>etc...<br><br>So, you can load any project and with the group  
>> you want.=
>> All of that can be (or should be hahahaha) perfectly loaded in a  
>> 1.0 Core =
>> image.<br><br>What I would really appreciate is if each maintainer  
>> can look=
>> at the code, load the different groups and give me feedback on the  
>> depende=
>> ncies or whatever.<br>
>> <br>I really wait your feedback. <br><br>Mariano<br><br>ps:=A0 I  
>> will relea=
>> se soon the first dev image using this :)<br>
>> <br>
>>
>>
>>
>>
>> _______________________________________________
>> 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

>>>
>> Yes, I agree. But don't worry. Esteban Lorenzano is working exatly  
>> in that.
>> You will be able to do:
>>
>> Loader load: 'Pharo' version: '1.0'    and wala!!
>>
>> (Esteban, correct me if I am wrong).
>>
>> However, this is yet in development and we are not even sure if this
>> architecture will be the choosen one. We are just trying to see  
>> what we can
>> doo.
>
> yep, that's true. Currently I'm alpha-testing it and writing some  
> tests
> and documentation, but now you can do things like:
>
> Loader new list. "Lists all available projects, scanning all  
> repositories"
> Loader new search: 'Blah'. "Looks for project Blah scanning all
> repositories. 'Blah' can be a segment, not just a full name"
> Loader new load: 'Blah'. "Load latest usable version of  
> ConfigurationOfBlah."
> Loader new load: 'Blah' version: '1.0'.  "Load '1.0' version of
> ConfigurationOfBlah."
> Loader new managed. "Answers a list of current managed projects."
> Loader new update. "Updates configurations for all managed projects."
> Loader new update: 'Blah'. "Updates ConfigurationOfBlah."
> Loader new upgrade. "Upgrades all managed project to a newest version
> (if present)".
> Loader new upgrade: 'Blah'. "Upgrades project 'Blah' to a newest
> version (if present)".
>
> You can specify permanent repositories by executing:
>
> Loader repository: 'http://myownrepo/project'.
> Loader repository: 'http://myownrepo/project' username: 'myself'
> password: 'secret'.
>
> (this acts as adding universes to apt-get of debian)
>
> And you can use "temporal" repositories:
> Loader new
> repository: 'http://myownrepo/project';
> load: 'Blah'.
>
> This repostories are dropped after use it, but any managed project
> keeps it for future managing.
>
> I hope this will solve all the loading issues. In the future, you  
> could
> do just:
>
> Loader new load: 'Pharo'. and get a full PharoDev image :)
>
> Cheers,
> Esteban
>
>
>
> _______________________________________________
> Pharo-project mailing list
> [hidden email]
> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
>

>
>
> On Fri, Jan 8, 2010 at 1:12 PM, Esteban Lorenzano
> <[hidden email]>wrote:
>
>> btw, ConfigurationOfPharo shouldn't be ConfigurationOfPharoDev?
>>
>>
> No. For that we have the groups. The same ConfigurationOfPharo will be used
> for differents stuff:
>
> ConfigurationOfPharo project version: 'xxx' load: 'StandardPharoDev'
>
> or
>
> ConfigurationOfPharo project version: 'xxx' load: 'StandardPharoWeb '   (if
> they came back)
>
> or
>
> ConfigurationOfPharo project version: 'xxx' load: 'SOMETHING'  (if they came
> back)
>
> Cheers
>
> Mariano
>
>
>
>> On 2010-01-07 17:54:27 -0300, Mariano Martinez Peck
>> <[hidden email]> said:
>>
>>>
>>>
>>> (Sorry for the long email)
>>>
>>> Yes, after a couple of weeks, I have written most of the needed Metacello
>>> configurations for the Dev images 1.0. Forget 1.1 for a while. Now we are
>>> able to:
>>>
>>> 1) Load stable version of packages
>>> 2) Manage the dependencies automatically
>>> 3) Each developer can create its custom PharoDev image
>>> 4) Flexibility to load the packages you want
>>> 5) Choose the browser for example: OB or O2
>>> 6) Choose to load the tests or not
>>> 7) Load each package in a PharoCore image without having to install
>> anything
>>> else (all the dependencies should be managed automatically)
>>> 8) You can take a PharoCore image and "transform" it to a Dev image, or
>> even
>>> web.
>>> 9) Others...
>>>
>>> This is not completed yet. There are some things that we are discussing
>> with
>>> Dale, but they are ok as a first step. I rather go step by step.
>>>
>>> What I did is to create all the infrastructure:
>>>
>>> a) The Configuration classes
>>> b) The dependencies
>>> c)  the groups,
>>>
>>> In summary, most of the "structure" and static information. However, I am
>>> not sure which version to load of each package. I will probable take care
>> of
>>> building the Dev images, but I won't:
>>>
>>> - Merge anything. It will not be my task to merge OB, or RB or whatever.
>>> - Check every version of each package before doing a release to see if it
>> is
>>> stable or not.
>>>
>>> So...what I REALLY (actually, WE) need is that each developer, each
>>> maintainer of the packages that we load of a PharoDev image, help us to
>>> create the stable versions. To create a new version for the Metacello
>>> configuration is VERY easy, The hard part is already done. You just have
>> to
>>> create a method and say which versions (except you create or eliminate
>>> packages or dependencies). If you read the code, you will probably
>>> understand it. However, you can read the Metacello tutorial (no more than
>>> one hour), or ask me or even more in the Metacello mailing list.
>>> So...PLEASE, I need the help of the maintainers to create the versions.
>> So
>>> far, I created the first version (1.0) with the latest version. But the
>> idea
>>> is that then you create 1.1.1 or 1.2 or whatever you consider.
>>>
>>> All the configurations can be found in
>>> http://www.squeaksource.com/MetacelloRepository
>>>
>>> So far, I created:  ConfigurationOfNewInspector,
>> ConfigurationOfOCompletion,
>>> ConfigurationOfOmniBrowser, ConfigurationOfPharoMorphicExtras,
>>> ConfigurationOfPharoSound, ConfigurationOfRefactoringBrowser,
>>> ConfigurationOfShout , and......ConfigurationOfPharo!!!
>>>
>>> To install them, just download that package and evaluate the load.
>> Example:
>>>
>>> Gofer new
>>> squeaksource: 'MetacelloRepository';
>>> package: 'ConfigurationOfShout';
>>> load.
>>>
>>> ((Smalltalk at: #ConfigurationOfShout) project version: '1.0') load.
>>>
>>> And then, you can also for exaple do:
>>>
>>> ((Smalltalk at: #ConfigurationOfShout) project version: '1.0') load:
>> 'Core'
>>>
>>> this doesn't install the tests.
>>>
>>> Or for example:  (ConfigurationOfOmniBrowser project version: '1.0')
>> load:
>>> 'Dev'
>>>
>>> etc...
>>>
>>> So, you can load any project and with the group you want. All of that can
>> be
>>> (or should be hahahaha) perfectly loaded in a 1.0 Core image.
>>>
>>> What I would really appreciate is if each maintainer can look at the
>> code,
>>> load the different groups and give me feedback on the dependencies or
>>> whatever.
>>>
>>> I really wait your feedback.
>>>
>>> Mariano
>>>
>>> ps:  I will release soon the first dev image using this :)
>>>
>>>
>>> (Sorry for the long email)<br><br>Yes, after a couple of weeks, I have
>> writ=
>>> ten most of the needed Metacello configurations for the Dev images 1.0.
>> For=
>>> get 1.1 for a while. Now we are able to:<br><br>1) Load stable version of
>> p=
>>> ackages<br>
>>> 2) Manage the dependencies automatically<br>3) Each developer can create
>> it=
>>> s custom PharoDev image<br>
>>> 4) Flexibility to load the packages you want<br>5) Choose the browser for
>> e=
>>> xample: OB or O2<br>6) Choose to load the tests or not<br>7) Load each
>> pack=
>>> age in a PharoCore image without having to install anything else (all the
>> d=
>>> ependencies should be managed automatically)<br>
>>>
>>> 8) You can take a PharoCore image and &quot;transform&quot; it to a Dev
>> ima=
>>> ge, or even web. <br>9) Others...<br><br>This is not completed yet. There
>> a=
>>> re some things that we are discussing with Dale, but they are ok as a
>> first=
>>> step. I rather go step by step. <br>
>>> <br>What I did is to create all the infrastructure:<br><br>a) The
>> Configura=
>>> tion classes<br>b) The dependencies <br>
>>> c)=A0 the groups,<br><br>In summary, most of the &quot;structure&quot;
>> and =
>>> static information. However, I am not sure which version to load of each
>> pa=
>>> ckage. I will probable take care of building the Dev images, but I
>> won&#39;=
>>> t:<br>
>>>
>>> <br>- Merge anything. It will not be my task to merge OB, or RB or
>> whatever=
>>> .<br>- Check every version of each package before doing a release to see
>> if=
>>> it is stable or not.<br><br>So...what I REALLY (actually, WE) need is
>> that=
>>> each developer, each maintainer of the packages that we load of a
>> PharoDev=
>>> image, help us to create the stable versions. To create a new version
>> for =
>>> the Metacello configuration is VERY easy, The hard part is already done.
>> Yo=
>>> u just have to create a method and say which versions (except you create
>> or=
>>> eliminate packages or dependencies). If you read the code, you will
>> probab=
>>> ly understand it. However, you can read the Metacello tutorial (no more
>> tha=
>>> n one hour), or ask me or even more in the Metacello mailing list.
>> So...PLE=
>>> ASE, I need the help of the maintainers to create the versions. So far, I
>> c=
>>> reated the first version (1.0) with the latest version. But the idea is
>> tha=
>>> t then you create 1.1.1 or 1.2 or whatever you consider.<br>
>>> <br>All the configurations can be found in <a href=3D"
>> http://www.squeaksour=
>>> ce.com/MetacelloRepository">
>> http://www.squeaksource.com/MetacelloRepository=
>>> </a><br><br>So far, I created:=A0 ConfigurationOfNewInspector,
>> Configuratio=
>>> nOfOCompletion, ConfigurationOfOmniBrowser,
>> ConfigurationOfPharoMorphicExtr=
>>> as, ConfigurationOfPharoSound, ConfigurationOfRefactoringBrowser,
>> Configura=
>>> tionOfShout , and......ConfigurationOfPharo!!!<br>
>>> <br>To install them, just download that package and evaluate the load.
>> Exam=
>>> ple:<br><br>Gofer new<br>=A0=A0=A0 squeaksource:
>> &#39;MetacelloRepository&#=
>>> 39;;<br>=A0=A0=A0 package: &#39;ConfigurationOfShout&#39;;<br>=A0=A0=A0
>> loa=
>>> d.<br><br>((Smalltalk at: #ConfigurationOfShout) project version:
>> &#39;1.0&=
>>> #39;) load.<br>
>>> <br>And then, you can also for exaple do:=A0 <br><br>
>>> ((Smalltalk at: #ConfigurationOfShout) project version: &#39;1.0&#39;)
>> load=
>>> : &#39;Core&#39;=A0 <br>this doesn&#39;t install the tests. <br><br>Or
>> for =
>>> example:=A0 (ConfigurationOfOmniBrowser project version: &#39;1.0&#39;)
>> loa=
>>> d: &#39;Dev&#39;<br>
>>> <br>etc...<br><br>So, you can load any project and with the group you
>> want.=
>>> All of that can be (or should be hahahaha) perfectly loaded in a 1.0
>> Core =
>>> image.<br><br>What I would really appreciate is if each maintainer can
>> look=
>>> at the code, load the different groups and give me feedback on the
>> depende=
>>> ncies or whatever.<br>
>>> <br>I really wait your feedback. <br><br>Mariano<br><br>ps:=A0 I will
>> relea=
>>> se soon the first dev image using this :)<br>
>>> <br>
>>>
>>>
>>>
>>>
>>> _______________________________________________
>>> 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 Fri, Jan 8, 2010 at 1:12 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;">
> btw, ConfigurationOfPharo shouldn&#39;t be ConfigurationOfPharoDev?<br>
> <br></blockquote><div><br>No. For that we have the groups. The same Configu=
> rationOfPharo will be used for differents stuff:<br><br>ConfigurationOfPhar=
> o project version: &#39;xxx&#39; load: &#39;StandardPharoDev&#39;<br><br>
> or<br><br>ConfigurationOfPharo project version: &#39;xxx&#39; load: &#39;St=
> andardPharoWeb &#39;=A0=A0 (if they came back)<br><br>or <br><br>Configurat=
> ionOfPharo project version: &#39;xxx&#39; load: &#39;SOMETHING&#39;=A0 (if =
> they came back)<br>
>
> <br>Cheers<br><br>Mariano<br>
> <br>=A0</div><blockquote class=3D"gmail_quote" style=3D"border-left: 1px so=
> lid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
> On 2010-01-07 17:54:27 -0300, Mariano Martinez Peck<br>
> <div><div></div><div class=3D"h5">&lt;<a href=3D"mailto:[hidden email]=
> om">[hidden email]</a>&gt; said:<br>
> <br>
> &gt;<br>
> &gt;<br>
> &gt; (Sorry for the long email)<br>
> &gt;<br>
> &gt; Yes, after a couple of weeks, I have written most of the needed Metace=
> llo<br>
> &gt; configurations for the Dev images 1.0. Forget 1.1 for a while. Now we =
> are<br>
> &gt; able to:<br>
> &gt;<br>
> &gt; 1) Load stable version of packages<br>
> &gt; 2) Manage the dependencies automatically<br>
> &gt; 3) Each developer can create its custom PharoDev image<br>
> &gt; 4) Flexibility to load the packages you want<br>
> &gt; 5) Choose the browser for example: OB or O2<br>
> &gt; 6) Choose to load the tests or not<br>
> &gt; 7) Load each package in a PharoCore image without having to install an=
> ything<br>
> &gt; else (all the dependencies should be managed automatically)<br>
> &gt; 8) You can take a PharoCore image and &quot;transform&quot; it to a De=
> v image, or even<br>
> &gt; web.<br>
> &gt; 9) Others...<br>
> &gt;<br>
> &gt; This is not completed yet. There are some things that we are discussin=
> g with<br>
> &gt; Dale, but they are ok as a first step. I rather go step by step.<br>
> &gt;<br>
> &gt; What I did is to create all the infrastructure:<br>
> &gt;<br>
> &gt; a) The Configuration classes<br>
> &gt; b) The dependencies<br>
> &gt; c) =A0the groups,<br>
> &gt;<br>
> &gt; In summary, most of the &quot;structure&quot; and static information. =
> However, I am<br>
> &gt; not sure which version to load of each package. I will probable take c=
> are of<br>
> &gt; building the Dev images, but I won&#39;t:<br>
> &gt;<br>
> &gt; - Merge anything. It will not be my task to merge OB, or RB or whateve=
> r.<br>
> &gt; - Check every version of each package before doing a release to see if=
>  it is<br>
> &gt; stable or not.<br>
> &gt;<br>
> &gt; So...what I REALLY (actually, WE) need is that each developer, each<br=
>>
> &gt; maintainer of the packages that we load of a PharoDev image, help us t=
> o<br>
> &gt; create the stable versions. To create a new version for the Metacello<=
> br>
> &gt; configuration is VERY easy, The hard part is already done. You just ha=
> ve to<br>
> &gt; create a method and say which versions (except you create or eliminate=
> <br>
> &gt; packages or dependencies). If you read the code, you will probably<br>
> &gt; understand it. However, you can read the Metacello tutorial (no more t=
> han<br>
> &gt; one hour), or ask me or even more in the Metacello mailing list.<br>
> &gt; So...PLEASE, I need the help of the maintainers to create the versions=
> . So<br>
> &gt; far, I created the first version (1.0) with the latest version. But th=
> e idea<br>
> &gt; is that then you create 1.1.1 or 1.2 or whatever you consider.<br>
> &gt;<br>
> &gt; All the configurations can be found in<br>
> &gt; <a href=3D"http://www.squeaksource.com/MetacelloRepository" target=3D"=
> _blank">http://www.squeaksource.com/MetacelloRepository</a><br>
> &gt;<br>
> &gt; So far, I created: =A0ConfigurationOfNewInspector, ConfigurationOfOCom=
> pletion,<br>
> &gt; ConfigurationOfOmniBrowser, ConfigurationOfPharoMorphicExtras,<br>
> &gt; ConfigurationOfPharoSound, ConfigurationOfRefactoringBrowser,<br>
> &gt; ConfigurationOfShout , and......ConfigurationOfPharo!!!<br>
> &gt;<br>
> &gt; To install them, just download that package and evaluate the load. Exa=
> mple:<br>
> &gt;<br>
> &gt; Gofer new<br>
> &gt; =A0 =A0 squeaksource: &#39;MetacelloRepository&#39;;<br>
> &gt; =A0 =A0 package: &#39;ConfigurationOfShout&#39;;<br>
> &gt; =A0 =A0 load.<br>
> &gt;<br>
> &gt; ((Smalltalk at: #ConfigurationOfShout) project version: &#39;1.0&#39;)=
>  load.<br>
> &gt;<br>
> &gt; And then, you can also for exaple do:<br>
> &gt;<br>
> &gt; ((Smalltalk at: #ConfigurationOfShout) project version: &#39;1.0&#39;)=
>  load: &#39;Core&#39;<br>
> &gt;<br>
> &gt; this doesn&#39;t install the tests.<br>
> &gt;<br>
> &gt; Or for example: =A0(ConfigurationOfOmniBrowser project version: &#39;1=
> .0&#39;) load:<br>
> &gt; &#39;Dev&#39;<br>
> &gt;<br>
> &gt; etc...<br>
> &gt;<br>
> &gt; So, you can load any project and with the group you want. All of that =
> can be<br>
> &gt; (or should be hahahaha) perfectly loaded in a 1.0 Core image.<br>
> &gt;<br>
> &gt; What I would really appreciate is if each maintainer can look at the c=
> ode,<br>
> &gt; load the different groups and give me feedback on the dependencies or<=
> br>
> &gt; whatever.<br>
> &gt;<br>
> &gt; I really wait your feedback.<br>
> &gt;<br>
> &gt; Mariano<br>
> &gt;<br>
> &gt; ps: =A0I will release soon the first dev image using this :)<br>
> &gt;<br>
> &gt;<br>
> </div></div>&gt; (Sorry for the long email)&lt;br&gt;&lt;br&gt;Yes, after a=
>  couple of weeks, I have writ=3D<br>
> &gt; ten most of the needed Metacello configurations for the Dev images 1.0=
> . For=3D<br>
> &gt; get 1.1 for a while. Now we are able to:&lt;br&gt;&lt;br&gt;1) Load st=
> able version of p=3D<br>
> &gt; ackages&lt;br&gt;<br>
> &gt; 2) Manage the dependencies automatically&lt;br&gt;3) Each developer ca=
> n create it=3D<br>
> &gt; s custom PharoDev image&lt;br&gt;<br>
> &gt; 4) Flexibility to load the packages you want&lt;br&gt;5) Choose the br=
> owser for e=3D<br>
> &gt; xample: OB or O2&lt;br&gt;6) Choose to load the tests or not&lt;br&gt;=
> 7) Load each pack=3D<br>
> &gt; age in a PharoCore image without having to install anything else (all =
> the d=3D<br>
> &gt; ependencies should be managed automatically)&lt;br&gt;<br>
> &gt;<br>
> &gt; 8) You can take a PharoCore image and &amp;quot;transform&amp;quot; it=
>  to a Dev ima=3D<br>
> &gt; ge, or even web. &lt;br&gt;9) Others...&lt;br&gt;&lt;br&gt;This is not=
>  completed yet. There a=3D<br>
> <div class=3D"im">&gt; re some things that we are discussing with Dale, but=
>  they are ok as a first=3D<br>
> </div>&gt; =A0step. I rather go step by step. &lt;br&gt;<br>
> &gt; &lt;br&gt;What I did is to create all the infrastructure:&lt;br&gt;&lt=
> ;br&gt;a) The Configura=3D<br>
> &gt; tion classes&lt;br&gt;b) The dependencies &lt;br&gt;<br>
> &gt; c)=3DA0 the groups,&lt;br&gt;&lt;br&gt;In summary, most of the &amp;qu=
> ot;structure&amp;quot; and =3D<br>
> &gt; static information. However, I am not sure which version to load of ea=
> ch pa=3D<br>
> &gt; ckage. I will probable take care of building the Dev images, but I won=
> &amp;#39;=3D<br>
> &gt; t:&lt;br&gt;<br>
> &gt;<br>
> &gt; &lt;br&gt;- Merge anything. It will not be my task to merge OB, or RB =
> or whatever=3D<br>
> &gt; .&lt;br&gt;- Check every version of each package before doing a releas=
> e to see if=3D<br>
> &gt; =A0it is stable or not.&lt;br&gt;&lt;br&gt;So...what I REALLY (actuall=
> y, WE) need is that=3D<br>
> <div class=3D"im">&gt; =A0each developer, each maintainer of the packages t=
> hat we load of a PharoDev=3D<br>
> &gt; =A0image, help us to create the stable versions. To create a new versi=
> on for =3D<br>
> </div>&gt; the Metacello configuration is VERY easy, The hard part is alrea=
> dy done. Yo=3D<br>
> <div class=3D"im">&gt; u just have to create a method and say which version=
> s (except you create or=3D<br>
> </div>&gt; =A0eliminate packages or dependencies). If you read the code, yo=
> u will probab=3D<br>
> &gt; ly understand it. However, you can read the Metacello tutorial (no mor=
> e tha=3D<br>
> &gt; n one hour), or ask me or even more in the Metacello mailing list. So.=
> ..PLE=3D<br>
> &gt; ASE, I need the help of the maintainers to create the versions. So far=
> , I c=3D<br>
> &gt; reated the first version (1.0) with the latest version. But the idea i=
> s tha=3D<br>
> &gt; t then you create 1.1.1 or 1.2 or whatever you consider.&lt;br&gt;<br>
> &gt; &lt;br&gt;All the configurations can be found in &lt;a href=3D3D&quot;=
> <a href=3D"http://www.squeaksour" target=3D"_blank">http://www.squeaksour</=
> a>=3D<br>
> &gt; <a href=3D"http://ce.com/MetacelloRepository" target=3D"_blank">ce.com=
> /MetacelloRepository</a>&quot;&gt;<a href=3D"http://www.squeaksource.com/Me=
> tacelloRepository=3D" target=3D"_blank">http://www.squeaksource.com/Metacel=
> loRepository=3D</a><br>
>
> &gt; &lt;/a&gt;&lt;br&gt;&lt;br&gt;So far, I created:=3DA0 ConfigurationOfN=
> ewInspector, Configuratio=3D<br>
> &gt; nOfOCompletion, ConfigurationOfOmniBrowser, ConfigurationOfPharoMorphi=
> cExtr=3D<br>
> &gt; as, ConfigurationOfPharoSound, ConfigurationOfRefactoringBrowser, Conf=
> igura=3D<br>
> &gt; tionOfShout , and......ConfigurationOfPharo!!!&lt;br&gt;<br>
> &gt; &lt;br&gt;To install them, just download that package and evaluate the=
>  load. Exam=3D<br>
> &gt; ple:&lt;br&gt;&lt;br&gt;Gofer new&lt;br&gt;=3DA0=3DA0=3DA0 squeaksourc=
> e: &amp;#39;MetacelloRepository&amp;#=3D<br>
> &gt; 39;;&lt;br&gt;=3DA0=3DA0=3DA0 package: &amp;#39;ConfigurationOfShout&a=
> mp;#39;;&lt;br&gt;=3DA0=3DA0=3DA0 loa=3D<br>
> &gt; d.&lt;br&gt;&lt;br&gt;((Smalltalk at: #ConfigurationOfShout) project v=
> ersion: &amp;#39;1.0&amp;=3D<br>
> &gt; #39;) load.&lt;br&gt;<br>
> &gt; &lt;br&gt;And then, you can also for exaple do:=3DA0 &lt;br&gt;&lt;br&=
> gt;<br>
> &gt; ((Smalltalk at: #ConfigurationOfShout) project version: &amp;#39;1.0&a=
> mp;#39;) load=3D<br>
> &gt; : &amp;#39;Core&amp;#39;=3DA0 &lt;br&gt;this doesn&amp;#39;t install t=
> he tests. &lt;br&gt;&lt;br&gt;Or for =3D<br>
> &gt; example:=3DA0 (ConfigurationOfOmniBrowser project version: &amp;#39;1.=
> 0&amp;#39;) loa=3D<br>
> &gt; d: &amp;#39;Dev&amp;#39;&lt;br&gt;<br>
> &gt; &lt;br&gt;etc...&lt;br&gt;&lt;br&gt;So, you can load any project and w=
> ith the group you want.=3D<br>
> <div class=3D"im">&gt; =A0All of that can be (or should be hahahaha) perfec=
> tly loaded in a 1.0 Core =3D<br>
> </div>&gt; image.&lt;br&gt;&lt;br&gt;What I would really appreciate is if e=
> ach maintainer can look=3D<br>
> &gt; =A0at the code, load the different groups and give me feedback on the =
> depende=3D<br>
> &gt; ncies or whatever.&lt;br&gt;<br>
> &gt; &lt;br&gt;I really wait your feedback. &lt;br&gt;&lt;br&gt;Mariano&lt;=
> br&gt;&lt;br&gt;ps:=3DA0 I will relea=3D<br>
> &gt; se soon the first dev image using this :)&lt;br&gt;<br>
> &gt; &lt;br&gt;<br>
> <div><div></div><div class=3D"h5">&gt;<br>
> &gt;<br>
> &gt;<br>
> &gt;<br>
> &gt; _______________________________________________<br>
> &gt; Pharo-project mailing list<br>
> &gt; <a
> href=3D"mailto:[hidden email]">Pharo-project@l=

>
> <a href=3D"http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo=
> -project" target=3D"_blank">http://lists.gforge.inria.fr/cgi-bin/mailman/li=
> stinfo/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><br>
> </div></div></blockquote></div><br>
>
>
>
>
> _______________________________________________
> Pharo-project mailing list
> [hidden email]
> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

>
> I whipped together some extension methods for Gofer that adds support for the above to Gofer:
>
> Gofer new
>   gemsource: 'metacello';
>   package: 'Metacello-Gofer-Extensions';
>   load.
>
> If there is no leading ConfigurationOf in the configuration name, 'ConfigurationOf' is tacked on. If no version is specified (or is nil) the latest version of the configuration is loaded. If no explicit load list is supplied (or is nil), then the default load list is loaded. In all cases it is expected that the configuration will be found in the MetacelloRepository on SqueakSource...
>
> Dale
>
> _______________________________________________
> Pharo-project mailing list
> [hidden email]
> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

> Hi,
> And what info do you think it should answer?
>
> On 2010-01-08 09:39:31 -0300, Alexandre Bergel
> <[hidden email]> said:
>
>> Esteban, this is excellent!!
>> It would be cool to have
>>
>> Loader new infoAbout:
>
>
>
>
> _______________________________________________
> Pharo-project mailing list
> [hidden email]
> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
>

> A description that could be obtained from the last commit comment for
> example. Or/and the squeaksource description.
>
> Cheers,
> Alexandre
>
>
> On 8 Jan 2010, at 10:20, Esteban Lorenzano wrote:
>
>> Hi,
>> And what info do you think it should answer?
>>
>> On 2010-01-08 09:39:31 -0300, Alexandre Bergel
>> <[hidden email]> said:
>>
>>> Esteban, this is excellent!!
>>> It would be cool to have
>>>
>>> Loader new infoAbout:
>>
>>
>>
>>
>> _______________________________________________
>> Pharo-project mailing list
>> [hidden email]
>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

>
> On 2010-01-08 10:26:06 -0300, Alexandre Bergel
> <[hidden email]> said:
>
>> A description that could be obtained from the last commit comment for
>> example. Or/and the squeaksource description.
>>
>> Cheers,
>> Alexandre
>>
>>
>> On 8 Jan 2010, at 10:20, Esteban Lorenzano wrote:
>>
>>> Hi,
>>> And what info do you think it should answer?
>>>
>>> On 2010-01-08 09:39:31 -0300, Alexandre Bergel
>>> <[hidden email]> said:
>>>
>>>> Esteban, this is excellent!!
>>>> It would be cool to have
>>>>
>>>> Loader new infoAbout:
>>>
>>>
>>>
>>>
>>> _______________________________________________
>>> 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
>

>>>
>> Yes, I agree. But don't worry. Esteban Lorenzano is working exatly in that.
>> You will be able to do:
>>
>> Loader load: 'Pharo' version: '1.0'    and wala!!
>>
>> (Esteban, correct me if I am wrong).
>>
>> However, this is yet in development and we are not even sure if this
>> architecture will be the choosen one. We are just trying to see what we can
>> doo.
>
> yep, that's true. Currently I'm alpha-testing it and writing some tests
> and documentation, but now you can do things like:
>
> Loader new list. "Lists all available projects, scanning all repositories"
> Loader new search: 'Blah'. "Looks for project Blah scanning all
> repositories. 'Blah' can be a segment, not just a full name"
> Loader new load: 'Blah'. "Load latest usable version of ConfigurationOfBlah."
> Loader new load: 'Blah' version: '1.0'.  "Load '1.0' version of
> ConfigurationOfBlah."
> Loader new managed. "Answers a list of current managed projects."
> Loader new update. "Updates configurations for all managed projects."
> Loader new update: 'Blah'. "Updates ConfigurationOfBlah."
> Loader new upgrade. "Upgrades all managed project to a newest version
> (if present)".
> Loader new upgrade: 'Blah'. "Upgrades project 'Blah' to a newest
> version (if present)".
>
> You can specify permanent repositories by executing:
>
> Loader repository: 'http://myownrepo/project'.
> Loader repository: 'http://myownrepo/project' username: 'myself'
> password: 'secret'.
>
> (this acts as adding universes to apt-get of debian)
>
> And you can use "temporal" repositories:
> Loader new
> repository: 'http://myownrepo/project';
> load: 'Blah'.
>
> This repostories are dropped after use it, but any managed project
> keeps it for future managing.
>
> I hope this will solve all the loading issues. In the future, you could
> do just:
>
> Loader new load: 'Pharo'. and get a full PharoDev image :)
>
> Cheers,
> Esteban
>
>
>
> _______________________________________________
> Pharo-project mailing list
> [hidden email]
> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

> Esteban
>
> From a vocabulary point of view could loader be an extension of Gofer?
> Because we have Gofer, metacello, and keeping the list to the minimum
> would be cool.
>
> Gofer configuration list
> GoferConfigurationLoader list
>
> ??
>
> Stef
>
>>>>
>>> Yes, I agree. But don't worry. Esteban Lorenzano is working exatly in that.
>>> You will be able to do:
>>>
>>> Loader load: 'Pharo' version: '1.0'    and wala!!
>>>
>>> (Esteban, correct me if I am wrong).
>>>
>>> However, this is yet in development and we are not even sure if this
>>> architecture will be the choosen one. We are just trying to see what we can
>>> doo.
>>
>> yep, that's true. Currently I'm alpha-testing it and writing some tests
>> and documentation, but now you can do things like:
>>
>> Loader new list. "Lists all available projects, scanning all repositories"
>> Loader new search: 'Blah'. "Looks for project Blah scanning all
>> repositories. 'Blah' can be a segment, not just a full name"
>> Loader new load: 'Blah'. "Load latest usable version of ConfigurationOfBlah."
>> Loader new load: 'Blah' version: '1.0'.  "Load '1.0' version of
>> ConfigurationOfBlah."
>> Loader new managed. "Answers a list of current managed projects."
>> Loader new update. "Updates configurations for all managed projects."
>> Loader new update: 'Blah'. "Updates ConfigurationOfBlah."
>> Loader new upgrade. "Upgrades all managed project to a newest version
>> (if present)".
>> Loader new upgrade: 'Blah'. "Upgrades project 'Blah' to a newest
>> version (if present)".
>>
>> You can specify permanent repositories by executing:
>>
>> Loader repository: 'http://myownrepo/project'.
>> Loader repository: 'http://myownrepo/project' username: 'myself'
>> password: 'secret'.
>>
>> (this acts as adding universes to apt-get of debian)
>>
>> And you can use "temporal" repositories:
>> Loader new
>> repository: 'http://myownrepo/project';
>> load: 'Blah'.
>>
>> This repostories are dropped after use it, but any managed project
>> keeps it for future managing.
>>
>> I hope this will solve all the loading issues. In the future, you could
>> do just:
>>
>> Loader new load: 'Pharo'. and get a full PharoDev image :)
>>
>> Cheers,
>> Esteban
>>
>>
>>
>> _______________________________________________
>> Pharo-project mailing list
>> [hidden email]
>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

>
> On 2010-01-08 12:56:09 -0300, Stéphane Ducasse
> <[hidden email]> said:
>
>> Esteban
>>
>> From a vocabulary point of view could loader be an extension of  
>> Gofer?
>> Because we have Gofer, metacello, and keeping the list to the minimum
>> would be cool.
>>
>> Gofer configuration list
>> GoferConfigurationLoader list
>>
>> ??
>>
>> Stef
>>
>>>>>
>>>> Yes, I agree. But don't worry. Esteban Lorenzano is working  
>>>> exatly in that.
>>>> You will be able to do:
>>>>
>>>> Loader load: 'Pharo' version: '1.0'    and wala!!
>>>>
>>>> (Esteban, correct me if I am wrong).
>>>>
>>>> However, this is yet in development and we are not even sure if  
>>>> this
>>>> architecture will be the choosen one. We are just trying to see  
>>>> what we can
>>>> doo.
>>>
>>> yep, that's true. Currently I'm alpha-testing it and writing some  
>>> tests
>>> and documentation, but now you can do things like:
>>>
>>> Loader new list. "Lists all available projects, scanning all  
>>> repositories"
>>> Loader new search: 'Blah'. "Looks for project Blah scanning all
>>> repositories. 'Blah' can be a segment, not just a full name"
>>> Loader new load: 'Blah'. "Load latest usable version of  
>>> ConfigurationOfBlah."
>>> Loader new load: 'Blah' version: '1.0'.  "Load '1.0' version of
>>> ConfigurationOfBlah."
>>> Loader new managed. "Answers a list of current managed projects."
>>> Loader new update. "Updates configurations for all managed  
>>> projects."
>>> Loader new update: 'Blah'. "Updates ConfigurationOfBlah."
>>> Loader new upgrade. "Upgrades all managed project to a newest  
>>> version
>>> (if present)".
>>> Loader new upgrade: 'Blah'. "Upgrades project 'Blah' to a newest
>>> version (if present)".
>>>
>>> You can specify permanent repositories by executing:
>>>
>>> Loader repository: 'http://myownrepo/project'.
>>> Loader repository: 'http://myownrepo/project' username: 'myself'
>>> password: 'secret'.
>>>
>>> (this acts as adding universes to apt-get of debian)
>>>
>>> And you can use "temporal" repositories:
>>> Loader new
>>> repository: 'http://myownrepo/project';
>>> load: 'Blah'.
>>>
>>> This repostories are dropped after use it, but any managed project
>>> keeps it for future managing.
>>>
>>> I hope this will solve all the loading issues. In the future, you  
>>> could
>>> do just:
>>>
>>> Loader new load: 'Pharo'. and get a full PharoDev image :)
>>>
>>> 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
>