Torsten,
I assume that you've seen the mail from Mariano where he describes the
proposed approach ... in the next week or so I will implement the
proposal so that folks can validate the proposal before unleashing it
... The key component to the proposal is that the configurations are
_not_ forked ... the same config version can be used for all versions of
Pharo and in all repositories.
Dale
Torsten Bergmann wrote:
One thing I think that should be discussed at ESUG
(sorry I'm not there) is if and how we want to maintain
Metacello repositories for the different Pharo versions
in the future.
I still think about the project/repo dependency issue:
An example: we have a repo for Pharo 1.2:
MetaRepoForPharo12 it may contain a ConfigurationOfFFI that works
for Pharo 1.1. and loads FFI.
it may also contain a ConfigurationOfExternalBrowser
that requires the ConfigurationOfFFI (usual Metacello
project
dependency)
When Pharo 1.3 comes out we have a new MetaRepoForPharo13 and may just
copy ConfigurationOfFFI over since it only loads packages and these packages
may be compatible to Pharo 1.3. So far so good ... but:
What about ConfigurationOfExternalBrowser, if we just copy it to the
new repo the config still points to the "old" ConfigurationOfFFI in the old
MetaRepoForPharo12 repo and not to the new one in MetaRepoForPharo13.
So we will have to adopt the configs for any new platform version ...
and since world keeps spinnning we may also end up with forked configurations.
Bye
T.
_______________________________________________
Pharo-project mailing list
[email protected]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
