On 10 Mar 2017, at 00:21, Nicolas Cellier <nicolas.cellier.aka.nice@gmail.com> wrote:
Grrr, even the mailing list changes, the first match in gmail just bounces, ;)
---------- Forwarded message ---------- From: Nicolas Cellier <nicolas.cellier.aka.nice@gmail.com> Date: 2017-03-10 0:05 GMT+01:00 Subject: Where are the Metacello ConfigurationOfYourProject supposed to be? To: Pharo Development <Pharo-project@lists.gforge.inria.fr>, The general-purpose Squeak developers list <squeak-dev@lists.squeakfoundation.org>
Hi, I must come back to one of the balkanization and lack of stability that most upset me.
Imagine that you are developping a cross dialect library, say for Squeak/Pharo and why not Gemstone.
Imagine that this library has a few dependencies to some other libraries, either Core like Alien/FFI or more exotic third party also available in other dialects.
The question are: -1) where are you supposed to maintain your own ConfigurationOf*?
Just next to your original source code. It is your config and you maintain it.
-2) where are you supposed to find the ConfigurationOf* dependencies?
Anywhere ;-) The config refers to its home repo. That is the one you should use in your dependency. The different repos Pharo uses are for classification purposes. That is how I understand it anyway.
Once upon a time, the answer would have been http://www.squeaksource.com/MetacelloRepository
But now, what is it? I see surprisingly few updates here (apart from Sven and a few others).
How can the Metacello feature of supporting cross-dialect work if the dialect specific configuration of dependencies are scattered all around the web?
Do the CPAN or PyPI have to change their URL each time a new release of perl or python is released?
Careless decisions in this area can easily sabotage the cross-dialect initiative.
Maybe I'm ranting by ignorance. I wish your answers will reassure me.
Nicolas