Dear List,
The package management in Pharo is getting more centralized. I moved ConfigurationOfMoose, ConfigurationOfCAnalyzer, ConfigurationOfMondrian in the SqueakSource package MetacelloRepository. It would be great if you follow this convention.
I load the tools I need using the script:
-=-=-=-=-=-=-=-=-= #('Mondrian' 'CAnalyzer' 'Spy') do: [:t | | name | name := 'ConfigurationOf', t. Gofer new squeaksource: 'MetacelloRepository'; package: name; load. (Smalltalk at: name asSymbol) perform: #loadDefault ]. -=-=-=-=-=-=-=-=-=
Cheers, Alexandre
On 8 janv. 2010, at 21:44, Alexandre Bergel wrote:
Dear List,
The package management in Pharo is getting more centralized. I moved ConfigurationOfMoose, ConfigurationOfCAnalyzer, ConfigurationOfMondrian in the SqueakSource package MetacelloRepository. It would be great if you follow this convention.
I am not sure this is a good move. This special repository is great for projects with high visibility and external to the Pharo sphere, like the packages for the dev image.
Besides, we are using Metacello configurations in some strange ways and continue to bend Metacello. I understand that this repository is mostly to track stable configurations, while we will soon starting to track our branches and development with Configurations. For our own projects, I prefer we keep them in our repository (I dont have the rights on Metacello repository).
I load the tools I need using the script:
-=-=-=-=-=-=-=-=-= #('Mondrian' 'CAnalyzer' 'Spy') do: [:t | | name | name := 'ConfigurationOf', t. Gofer new squeaksource: 'MetacelloRepository'; package: name; load. (Smalltalk at: name asSymbol) perform: #loadDefault ]. -=-=-=-=-=-=-=-=-=
Cheers, Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
-- Simon
The package management in Pharo is getting more centralized. I moved ConfigurationOfMoose, ConfigurationOfCAnalyzer, ConfigurationOfMondrian in the SqueakSource package MetacelloRepository. It would be great if you follow this convention.
I am not sure this is a good move. This special repository is great for projects with high visibility and external to the Pharo sphere, like the packages for the dev image.
I asked a number of times already, and apparently all metacello configurations must be in MetacelloRepository. I cannot find an argument why ConfigurationOfMoose should not be in. Esteban is working on a kind of apt-get mechanism based on this repository. It is not clear so far that we have something to gain by remaining outside. Especially since this will not change our habits at all.
MetacelloRepository contains configurations for applications that are not part of PharoDev (e.g., Seaside, Glorp, Pier, ...)
Besides, we are using Metacello configurations in some strange ways and continue to bend Metacello. I understand that this repository is mostly to track stable configurations, while we will soon starting to track our branches and development with Configurations. For our own projects, I prefer we keep them in our repository (I dont have the rights on Metacello repository).
MetacelloRepository has a global read and write.
Alexandre
I load the tools I need using the script:
-=-=-=-=-=-=-=-=-= #('Mondrian' 'CAnalyzer' 'Spy') do: [:t | | name | name := 'ConfigurationOf', t. Gofer new squeaksource: 'MetacelloRepository'; package: name; load. (Smalltalk at: name asSymbol) perform: #loadDefault ]. -=-=-=-=-=-=-=-=-=
Cheers, Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
-- Simon
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
On 8 janv. 2010, at 22:16, Alexandre Bergel wrote:
The package management in Pharo is getting more centralized. I moved ConfigurationOfMoose, ConfigurationOfCAnalyzer, ConfigurationOfMondrian in the SqueakSource package MetacelloRepository. It would be great if you follow this convention.
I am not sure this is a good move. This special repository is great for projects with high visibility and external to the Pharo sphere, like the packages for the dev image.
I asked a number of times already, and apparently all metacello configurations must be in MetacelloRepository. I cannot find an argument why ConfigurationOfMoose should not be in. Esteban is working on a kind of apt-get mechanism based on this repository. It is not clear so far that we have something to gain by remaining outside. Especially since this will not change our habits at all.
We still have to figure out some usage of Metacello within Moose, and I think we will a very specific usage concerned with tracking development changes. Until we have this figured out and until Esteban has figured its own project, I dont feel the urge to put both together.
MetacelloRepository contains configurations for applications that are not part of PharoDev (e.g., Seaside, Glorp, Pier, ...)
Besides, we are using Metacello configurations in some strange ways and continue to bend Metacello. I understand that this repository is mostly to track stable configurations, while we will soon starting to track our branches and development with Configurations. For our own projects, I prefer we keep them in our repository (I dont have the rights on Metacello repository).
MetacelloRepository has a global read and write.
I was talking about admin rights :)
Alexandre
I load the tools I need using the script:
-=-=-=-=-=-=-=-=-= #('Mondrian' 'CAnalyzer' 'Spy') do: [:t | | name | name := 'ConfigurationOf', t. Gofer new squeaksource: 'MetacelloRepository'; package: name; load. (Smalltalk at: name asSymbol) perform: #loadDefault ]. -=-=-=-=-=-=-=-=-=
Cheers, Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
-- Simon
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
-- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
-- Simon
We can copy configuration there but we should not move them. Each project should still have its own local copy. Having a global entry is good but it is not incompatible with the notion of locality
Stef
On Jan 8, 2010, at 9:44 PM, Alexandre Bergel wrote:
Dear List,
The package management in Pharo is getting more centralized. I moved ConfigurationOfMoose, ConfigurationOfCAnalyzer, ConfigurationOfMondrian in the SqueakSource package MetacelloRepository. It would be great if you follow this convention.
I load the tools I need using the script:
-=-=-=-=-=-=-=-=-= #('Mondrian' 'CAnalyzer' 'Spy') do: [:t | | name | name := 'ConfigurationOf', t. Gofer new squeaksource: 'MetacelloRepository'; package: name; load. (Smalltalk at: name asSymbol) perform: #loadDefault ]. -=-=-=-=-=-=-=-=-=
Cheers, Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
On 9 janv. 2010, at 09:19, Stéphane Ducasse wrote:
We can copy configuration there but we should not move them. Each project should still have its own local copy. Having a global entry is good but it is not incompatible with the notion of locality
Yep, we can make a copy whenever a new stable/beta is released.
Stef
On Jan 8, 2010, at 9:44 PM, Alexandre Bergel wrote:
Dear List,
The package management in Pharo is getting more centralized. I moved ConfigurationOfMoose, ConfigurationOfCAnalyzer, ConfigurationOfMondrian in the SqueakSource package MetacelloRepository. It would be great if you follow this convention.
I load the tools I need using the script:
-=-=-=-=-=-=-=-=-= #('Mondrian' 'CAnalyzer' 'Spy') do: [:t | | name | name := 'ConfigurationOf', t. Gofer new squeaksource: 'MetacelloRepository'; package: name; load. (Smalltalk at: name asSymbol) perform: #loadDefault ]. -=-=-=-=-=-=-=-=-=
Cheers, Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
-- Simon
I was thinking too about the MetacelloRepository. The problem is that a configuration without being completely up to date is not of much use.
So, let's try as Simon suggests to continue to work on the project repository and copy them when a release is done.
Cheers, Doru
On 9 Jan 2010, at 18:03, Simon Denier wrote:
On 9 janv. 2010, at 09:19, Stéphane Ducasse wrote:
We can copy configuration there but we should not move them. Each project should still have its own local copy. Having a global entry is good but it is not incompatible with the notion of locality
Yep, we can make a copy whenever a new stable/beta is released.
Stef
On Jan 8, 2010, at 9:44 PM, Alexandre Bergel wrote:
Dear List,
The package management in Pharo is getting more centralized. I moved ConfigurationOfMoose, ConfigurationOfCAnalyzer, ConfigurationOfMondrian in the SqueakSource package MetacelloRepository. It would be great if you follow this convention.
I load the tools I need using the script:
-=-=-=-=-=-=-=-=-= #('Mondrian' 'CAnalyzer' 'Spy') do: [:t | | name | name := 'ConfigurationOf', t. Gofer new squeaksource: 'MetacelloRepository'; package: name; load. (Smalltalk at: name asSymbol) perform: #loadDefault ]. -=-=-=-=-=-=-=-=-=
Cheers, Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
-- Simon
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
-- www.tudorgirba.com
"Live like you mean it."
I think that this should be the pattern for all the projects else the repository will be a big mess
Stef
On Jan 10, 2010, at 2:42 PM, Tudor Girba wrote:
I was thinking too about the MetacelloRepository. The problem is that a configuration without being completely up to date is not of much use.
So, let's try as Simon suggests to continue to work on the project repository and copy them when a release is done.
Cheers, Doru
On 9 Jan 2010, at 18:03, Simon Denier wrote:
On 9 janv. 2010, at 09:19, Stéphane Ducasse wrote:
We can copy configuration there but we should not move them. Each project should still have its own local copy. Having a global entry is good but it is not incompatible with the notion of locality
Yep, we can make a copy whenever a new stable/beta is released.
Stef
On Jan 8, 2010, at 9:44 PM, Alexandre Bergel wrote:
Dear List,
The package management in Pharo is getting more centralized. I moved ConfigurationOfMoose, ConfigurationOfCAnalyzer, ConfigurationOfMondrian in the SqueakSource package MetacelloRepository. It would be great if you follow this convention.
I load the tools I need using the script:
-=-=-=-=-=-=-=-=-= #('Mondrian' 'CAnalyzer' 'Spy') do: [:t | | name | name := 'ConfigurationOf', t. Gofer new squeaksource: 'MetacelloRepository'; package: name; load. (Smalltalk at: name asSymbol) perform: #loadDefault ]. -=-=-=-=-=-=-=-=-=
Cheers, Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
-- Simon
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
-- www.tudorgirba.com
"Live like you mean it."
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
The problem is that you cannot just copy them. You need to change reference from Moose to MetacelloRepository when loading dependent ConfigurationOfYYY.
Cheers, Alexandre
On 10 Jan 2010, at 10:42, Tudor Girba wrote:
I was thinking too about the MetacelloRepository. The problem is that a configuration without being completely up to date is not of much use.
So, let's try as Simon suggests to continue to work on the project repository and copy them when a release is done.
Cheers, Doru
On 9 Jan 2010, at 18:03, Simon Denier wrote:
On 9 janv. 2010, at 09:19, Stéphane Ducasse wrote:
We can copy configuration there but we should not move them. Each project should still have its own local copy. Having a global entry is good but it is not incompatible with the notion of locality
Yep, we can make a copy whenever a new stable/beta is released.
Stef
On Jan 8, 2010, at 9:44 PM, Alexandre Bergel wrote:
Dear List,
The package management in Pharo is getting more centralized. I moved ConfigurationOfMoose, ConfigurationOfCAnalyzer, ConfigurationOfMondrian in the SqueakSource package MetacelloRepository. It would be great if you follow this convention.
I load the tools I need using the script:
-=-=-=-=-=-=-=-=-= #('Mondrian' 'CAnalyzer' 'Spy') do: [:t | | name | name := 'ConfigurationOf', t. Gofer new squeaksource: 'MetacelloRepository'; package: name; load. (Smalltalk at: name asSymbol) perform: #loadDefault ]. -=-=-=-=-=-=-=-=-=
Cheers, Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
-- Simon
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
-- www.tudorgirba.com
"Live like you mean it."
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
On Jan 11, 2010, at 1:56 PM, Alexandre Bergel wrote:
The problem is that you cannot just copy them. You need to change reference from Moose to MetacelloRepository when loading dependent ConfigurationOfYYY.
why? you click on the MC package and copy to another repository
Cheers, Alexandre
On 10 Jan 2010, at 10:42, Tudor Girba wrote:
I was thinking too about the MetacelloRepository. The problem is that a configuration without being completely up to date is not of much use.
So, let's try as Simon suggests to continue to work on the project repository and copy them when a release is done.
Cheers, Doru
On 9 Jan 2010, at 18:03, Simon Denier wrote:
On 9 janv. 2010, at 09:19, Stéphane Ducasse wrote:
We can copy configuration there but we should not move them. Each project should still have its own local copy. Having a global entry is good but it is not incompatible with the notion of locality
Yep, we can make a copy whenever a new stable/beta is released.
Stef
On Jan 8, 2010, at 9:44 PM, Alexandre Bergel wrote:
Dear List,
The package management in Pharo is getting more centralized. I moved ConfigurationOfMoose, ConfigurationOfCAnalyzer, ConfigurationOfMondrian in the SqueakSource package MetacelloRepository. It would be great if you follow this convention.
I load the tools I need using the script:
-=-=-=-=-=-=-=-=-= #('Mondrian' 'CAnalyzer' 'Spy') do: [:t | | name | name := 'ConfigurationOf', t. Gofer new squeaksource: 'MetacelloRepository'; package: name; load. (Smalltalk at: name asSymbol) perform: #loadDefault ]. -=-=-=-=-=-=-=-=-=
Cheers, Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
-- Simon
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
-- www.tudorgirba.com
"Live like you mean it."
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
-- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
I meant that the loading script has to be updated with the new repository (Moose -> MetacelloRepository). In the long method ConfigurationOfMoose>>baseline40beta3:, I had to change spec project: 'Mondrian for Moose' with: [ spec className: 'ConfigurationOfMondrian'; file: 'ConfigurationOfMondrian'; version: 'default'; repository: 'http://www.squeaksource.com/Mondrian' ].
into spec project: 'Mondrian for Moose' with: [ spec className: 'ConfigurationOfMondrian'; file: 'ConfigurationOfMondrian'; version: 'default'; repository: 'http://www.squeaksource.com/MetacelloRepository' ].
Alexandre
On 11 Jan 2010, at 10:46, Stéphane Ducasse wrote:
On Jan 11, 2010, at 1:56 PM, Alexandre Bergel wrote:
The problem is that you cannot just copy them. You need to change reference from Moose to MetacelloRepository when loading dependent ConfigurationOfYYY.
why? you click on the MC package and copy to another repository
Cheers, Alexandre
On 10 Jan 2010, at 10:42, Tudor Girba wrote:
I was thinking too about the MetacelloRepository. The problem is that a configuration without being completely up to date is not of much use.
So, let's try as Simon suggests to continue to work on the project repository and copy them when a release is done.
Cheers, Doru
On 9 Jan 2010, at 18:03, Simon Denier wrote:
On 9 janv. 2010, at 09:19, Stéphane Ducasse wrote:
We can copy configuration there but we should not move them. Each project should still have its own local copy. Having a global entry is good but it is not incompatible with the notion of locality
Yep, we can make a copy whenever a new stable/beta is released.
Stef
On Jan 8, 2010, at 9:44 PM, Alexandre Bergel wrote:
Dear List,
The package management in Pharo is getting more centralized. I moved ConfigurationOfMoose, ConfigurationOfCAnalyzer, ConfigurationOfMondrian in the SqueakSource package MetacelloRepository. It would be great if you follow this convention.
I load the tools I need using the script:
-=-=-=-=-=-=-=-=-= #('Mondrian' 'CAnalyzer' 'Spy') do: [:t | | name | name := 'ConfigurationOf', t. Gofer new squeaksource: 'MetacelloRepository'; package: name; load. (Smalltalk at: name asSymbol) perform: #loadDefault ]. -=-=-=-=-=-=-=-=-=
Cheers, Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
-- Simon
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
-- www.tudorgirba.com
"Live like you mean it."
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
-- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Hi Alex,
As the main script will remain in the Moose repository, you do not have to change anything. It will work just as it is.
Cheers, Doru
On 11 Jan 2010, at 14:57, Alexandre Bergel wrote:
I meant that the loading script has to be updated with the new repository (Moose -> MetacelloRepository). In the long method ConfigurationOfMoose>>baseline40beta3:, I had to change spec project: 'Mondrian for Moose' with: [ spec className: 'ConfigurationOfMondrian'; file: 'ConfigurationOfMondrian'; version: 'default'; repository: 'http://www.squeaksource.com/Mondrian' ].
into spec project: 'Mondrian for Moose' with: [ spec className: 'ConfigurationOfMondrian'; file: 'ConfigurationOfMondrian'; version: 'default'; repository: 'http://www.squeaksource.com/MetacelloRepository' ].
Alexandre
On 11 Jan 2010, at 10:46, Stéphane Ducasse wrote:
On Jan 11, 2010, at 1:56 PM, Alexandre Bergel wrote:
The problem is that you cannot just copy them. You need to change reference from Moose to MetacelloRepository when loading dependent ConfigurationOfYYY.
why? you click on the MC package and copy to another repository
Cheers, Alexandre
On 10 Jan 2010, at 10:42, Tudor Girba wrote:
I was thinking too about the MetacelloRepository. The problem is that a configuration without being completely up to date is not of much use.
So, let's try as Simon suggests to continue to work on the project repository and copy them when a release is done.
Cheers, Doru
On 9 Jan 2010, at 18:03, Simon Denier wrote:
On 9 janv. 2010, at 09:19, Stéphane Ducasse wrote:
We can copy configuration there but we should not move them. Each project should still have its own local copy. Having a global entry is good but it is not incompatible with the notion of locality
Yep, we can make a copy whenever a new stable/beta is released.
Stef
On Jan 8, 2010, at 9:44 PM, Alexandre Bergel wrote:
> Dear List, > > The package management in Pharo is getting more centralized. > I moved ConfigurationOfMoose, ConfigurationOfCAnalyzer, > ConfigurationOfMondrian in the SqueakSource package > MetacelloRepository. > It would be great if you follow this convention. > > I load the tools I need using the script: > > -=-=-=-=-=-=-=-=-= > #('Mondrian' 'CAnalyzer' 'Spy') > do: [:t | > | name | > name := 'ConfigurationOf', t. > Gofer new > squeaksource: 'MetacelloRepository'; > package: name; > load. > (Smalltalk at: name asSymbol) perform: #loadDefault ]. > -=-=-=-=-=-=-=-=-= > > Cheers, > Alexandre > -- > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: > Alexandre Bergel http://www.bergel.eu > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > > > > > > _______________________________________________ > Moose-dev mailing list > Moose-dev@iam.unibe.ch > https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
-- Simon
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
-- www.tudorgirba.com
"Live like you mean it."
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
-- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
-- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
-- www.tudorgirba.com
"To lead is not to demand things, it is to make them happen."
Ok, but it cannot be just 'copied' to the Metacello repository.
Alexandre
On 11 Jan 2010, at 11:45, Tudor Girba wrote:
Hi Alex,
As the main script will remain in the Moose repository, you do not have to change anything. It will work just as it is.
Cheers, Doru
On 11 Jan 2010, at 14:57, Alexandre Bergel wrote:
I meant that the loading script has to be updated with the new repository (Moose -> MetacelloRepository). In the long method ConfigurationOfMoose>>baseline40beta3:, I had to change spec project: 'Mondrian for Moose' with: [ spec className: 'ConfigurationOfMondrian'; file: 'ConfigurationOfMondrian'; version: 'default'; repository: 'http://www.squeaksource.com/Mondrian' ].
into spec project: 'Mondrian for Moose' with: [ spec className: 'ConfigurationOfMondrian'; file: 'ConfigurationOfMondrian'; version: 'default'; repository: 'http://www.squeaksource.com/MetacelloRepository' ].
Alexandre
On 11 Jan 2010, at 10:46, Stéphane Ducasse wrote:
On Jan 11, 2010, at 1:56 PM, Alexandre Bergel wrote:
The problem is that you cannot just copy them. You need to change reference from Moose to MetacelloRepository when loading dependent ConfigurationOfYYY.
why? you click on the MC package and copy to another repository
Cheers, Alexandre
On 10 Jan 2010, at 10:42, Tudor Girba wrote:
I was thinking too about the MetacelloRepository. The problem is that a configuration without being completely up to date is not of much use.
So, let's try as Simon suggests to continue to work on the project repository and copy them when a release is done.
Cheers, Doru
On 9 Jan 2010, at 18:03, Simon Denier wrote:
On 9 janv. 2010, at 09:19, Stéphane Ducasse wrote:
> We can copy configuration there but we should not move them. > Each project should still have its own local copy. > Having a global entry is good but it is not incompatible with > the notion of locality
Yep, we can make a copy whenever a new stable/beta is released.
> > > Stef > > On Jan 8, 2010, at 9:44 PM, Alexandre Bergel wrote: > >> Dear List, >> >> The package management in Pharo is getting more centralized. >> I moved ConfigurationOfMoose, ConfigurationOfCAnalyzer, >> ConfigurationOfMondrian in the SqueakSource package >> MetacelloRepository. >> It would be great if you follow this convention. >> >> I load the tools I need using the script: >> >> -=-=-=-=-=-=-=-=-= >> #('Mondrian' 'CAnalyzer' 'Spy') >> do: [:t | >> | name | >> name := 'ConfigurationOf', t. >> Gofer new >> squeaksource: 'MetacelloRepository'; >> package: name; >> load. >> (Smalltalk at: name asSymbol) perform: #loadDefault ]. >> -=-=-=-=-=-=-=-=-= >> >> Cheers, >> Alexandre >> -- >> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: >> Alexandre Bergel http://www.bergel.eu >> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. >> >> >> >> >> >> _______________________________________________ >> Moose-dev mailing list >> Moose-dev@iam.unibe.ch >> https://www.iam.unibe.ch/mailman/listinfo/moose-dev > > > _______________________________________________ > Moose-dev mailing list > Moose-dev@iam.unibe.ch > https://www.iam.unibe.ch/mailman/listinfo/moose-dev
-- Simon
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
-- www.tudorgirba.com
"Live like you mean it."
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
-- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
-- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
-- www.tudorgirba.com
"To lead is not to demand things, it is to make them happen."
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
why? We copy a spec that says where the package should be loaded from.
Ok, but it cannot be just 'copied' to the Metacello repository.
Alexandre
On 11 Jan 2010, at 11:45, Tudor Girba wrote:
Hi Alex,
As the main script will remain in the Moose repository, you do not have to change anything. It will work just as it is.
I got confused.
Am'I correct?
The repository: can be 'http://www.squeaksource.com/Mondrian' even if the configuration is saved in 'http://www.squeaksource.com/MetacelloRepository
Stef
On 11 Jan 2010, at 14:57, Alexandre Bergel wrote:
I meant that the loading script has to be updated with the new repository (Moose -> MetacelloRepository). In the long method ConfigurationOfMoose>>baseline40beta3:, I had to change spec project: 'Mondrian for Moose' with: [ spec className: 'ConfigurationOfMondrian'; file: 'ConfigurationOfMondrian'; version: 'default'; repository: 'http://www.squeaksource.com/Mondrian' ].
into spec project: 'Mondrian for Moose' with: [ spec className: 'ConfigurationOfMondrian'; file: 'ConfigurationOfMondrian'; version: 'default'; repository: 'http://www.squeaksource.com/MetacelloRepository' ].
Alexandre
On 11 Jan 2010, at 10:46, Stéphane Ducasse wrote:
On Jan 11, 2010, at 1:56 PM, Alexandre Bergel wrote:
The problem is that you cannot just copy them. You need to change reference from Moose to MetacelloRepository when loading dependent ConfigurationOfYYY.
why? you click on the MC package and copy to another repository
Cheers, Alexandre
On 10 Jan 2010, at 10:42, Tudor Girba wrote:
I was thinking too about the MetacelloRepository. The problem is that a configuration without being completely up to date is not of much use.
So, let's try as Simon suggests to continue to work on the project repository and copy them when a release is done.
Cheers, Doru
On 9 Jan 2010, at 18:03, Simon Denier wrote:
> > On 9 janv. 2010, at 09:19, Stéphane Ducasse wrote: > >> We can copy configuration there but we should not move them. >> Each project should still have its own local copy. >> Having a global entry is good but it is not incompatible with the notion of locality > > > Yep, we can make a copy whenever a new stable/beta is released. > > >> >> >> Stef >> >> On Jan 8, 2010, at 9:44 PM, Alexandre Bergel wrote: >> >>> Dear List, >>> >>> The package management in Pharo is getting more centralized. >>> I moved ConfigurationOfMoose, ConfigurationOfCAnalyzer, ConfigurationOfMondrian in the SqueakSource package MetacelloRepository. >>> It would be great if you follow this convention. >>> >>> I load the tools I need using the script: >>> >>> -=-=-=-=-=-=-=-=-= >>> #('Mondrian' 'CAnalyzer' 'Spy') >>> do: [:t | >>> | name | >>> name := 'ConfigurationOf', t. >>> Gofer new >>> squeaksource: 'MetacelloRepository'; >>> package: name; >>> load. >>> (Smalltalk at: name asSymbol) perform: #loadDefault ]. >>> -=-=-=-=-=-=-=-=-= >>> >>> Cheers, >>> Alexandre >>> -- >>> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: >>> Alexandre Bergel http://www.bergel.eu >>> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. >>> >>> >>> >>> >>> >>> _______________________________________________ >>> Moose-dev mailing list >>> Moose-dev@iam.unibe.ch >>> https://www.iam.unibe.ch/mailman/listinfo/moose-dev >> >> >> _______________________________________________ >> Moose-dev mailing list >> Moose-dev@iam.unibe.ch >> https://www.iam.unibe.ch/mailman/listinfo/moose-dev > > -- > Simon > > > > > _______________________________________________ > Moose-dev mailing list > Moose-dev@iam.unibe.ch > https://www.iam.unibe.ch/mailman/listinfo/moose-dev
-- www.tudorgirba.com
"Live like you mean it."
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
-- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
-- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
-- www.tudorgirba.com
"To lead is not to demand things, it is to make them happen."
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
-- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
-
Alexandre Bergel -
Simon Denier -
Stéphane Ducasse -
Tudor Girba