On 13 Nov 2011, at 22:05, Stéphane Ducasse wrote:
Hi,
On 13 Nov 2011, at 09:02, Stéphane Ducasse wrote:
we do not lose anything if we have a clear process. Right now I have no idea what is the process. And just publishing a package and thinking that it will be loaded leads to the fact that we cannot load moose anymore.
This is because of the mess introduced by having hardcoded versions during development.
There is nothing like a free lunch and we could script metacello to generate support our process. It makes me smile because we say that we are tool builder and we still do not script the API of metacello.
You wrote a chapter on Metacello. So, you are a great candidate for providing the support :).
sure!
It was a joke :)
Now you will probably not like the result. I still do not understand what was wrong with putting versions.
Nothing. Just doing it manually was too error prone and I could not keep up with it. And for development, I want to continue to push for the last version of all packages.
The thing that would work well with our process is to produce a configuration for what is in the image at some moment. But, it is difficult to produce with nested configurations. So, in the meantime we should traverse the Configuration and produce a simple flat Gofer script. This could be a nice bridge solution.
I wonder why I wrote it since nobody reads it.
I will fork the ConfigurationOf and see but I have no time for that now.
Do not fork it :). Just add publish on top.
Doru
Stef _______________________________________________ Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
-- www.tudorgirba.com
"There are no old things, there are only old ways of looking at them."