Hi,
would it make sense to take configurations from metarepos instead
directly from the source?
I do not think so but if people show me otherwise I could follow that.
Usually I have a conf in my repo referencing other repo and not the meta
one
Then I push in the meta just to config.
And more imporantly: would be considered bad practice for users to do it
right now?
E.g.
spec
project: 'Magritte'
with: [ spec
className: #ConfigurationOfMagritte3;
versionString: #stable;
repository:
'http://smalltalkhub.com/mc/Pharo/MetaRepoForPharo50/main/' ].
v. repository: 'http://smalltalkhub.com/mc/Magritte/Magritte3/main/'
pros:
* the (e.g. Magritte) developer can freely change platforms
* the ConfigurationOf could differ between various MetaRepo versions
(combined with git it could reduce their complexity)
* users do not have to think about where is the canonical repo (I've
seen project that had copies on SS, STHub, GitHub, and a custom location
-_-)
cons:
* the ConfigurationOf could differ between various MetaRepo versions (if
the code is compatible, then two repos have to be updated
Any thoughts?
Peter
--
Using Opera's mail client: http://www.opera.com/mail/
