Thanks for your answer. I have read this document and I know that dependencies can be defined in Metacello configuration classes. I guess I question whether this is the best location to store package dependencies.
If, for example, I were to port my integration with DTangler to Pharo, I am unsure how the tool will be able to find dependencies for a given package. Would it need to search though ConfigurationOf-classes? How would it determine the correct version to use, etc? Maybe it can be done, but it would be harder than VisualWorks’ approach were you have this information directly in the package. Also consider that you might want to query dependencies not just for a single project (like Seaside), but for the entire image. Using a single ConfigurationOf-class, might not be sufficient. Then again, I do not have much knowledge of Pharo. Maybe Pharo’s approach makes sense once I start using it… Is my understanding correct when I expect Pharo to continue having package dependencies only defined in Metacello configuration classes? Kind regards Runar Jordahl
