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(a)iam.unibe.ch
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
--
Simon
_______________________________________________
Moose-dev mailing list
Moose-dev(a)iam.unibe.ch
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
--
_,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
Alexandre Bergel
http://www.bergel.eu
^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
_______________________________________________
Moose-dev mailing list
Moose-dev(a)iam.unibe.ch
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
--
Simon