>
>
> Metacello
> -------------
> This is the most difficult part.
> - Right now, Metacello hardcodes repository paths in the references to
> other projects. This isn't bad, but an alternative should be provided.
> That is, when referencing external projects like:
>
> project: 'Refactoring-Core' with: [
> �spec
> � �className: 'ConfigurationOfRefactoringBrowser';
> � �loads: #('Refactoring-Core' );
> � �file: 'ConfigurationOfRefactoringBrowser';
> � �repository: 'http://www.squeaksource.com/MetacelloRepository' ];


But a spec is an object so we could have a visitor going over and doing the automatic
rewrite for us.



maybe repositoryOverrides:� does exactly that...I don't know

> Of course nothing prevents for a configuration to reference a project
> outside the "universe" repository, but that is a decision of the
> maintainer.

No this is a dogma. NO NO NO reference outside the repository.
NOT A SINGLE ONE. NEVER.
We want 100% self contained distribution.


+99999


Stef






_______________________________________________
Pharo-project mailing list
Pharo-project@lists.gforge.inria.fr
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project