>> > > Sorry, but I am too stupid for it. It is too complex for me. > > You can take my scripts and get a working and minimal image. For many > years I've been building images without problems.
sure Do not change. You are right. I'm wrong. Let us know try to improve metacello and bash it. > Now you can say that this is not your use-case, but Metacello > configurations are not my use-case either. I say nothing. I just totally convinced that if we do not want to stay an obscure little toy we have to capture dependencies and scripts do not capture that. For me metacello is not the panacea but it exists and if we would spend a little time then the system would benefit from it. Now there are problems because I have to fix configurations for systems I have no clue how they are built. So what your attitude just create is more burden on my shoulder. Sadly I would love that we do not have to use your projects but we cannot so I should do the fucking stupid job of extracting the dependencies in your project. It would cost you 3 min and it costs me hours but apparently your are right and I'm wrong and this is my stone. So I will continue. I do it because I want pharo to be a success. We will have a new engineer and we will ask him to improve metacello. because there is no other ways. I do not want to maintain Pharo without spec of dependencies and support for development because metacello supports that. Stef
