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(a)iam.unibe.ch
>
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
_______________________________________________
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
"Live like you mean it."
_______________________________________________
Moose-dev mailing list
Moose-dev(a)iam.unibe.ch