On Wed, Jun 9, 2010 at 12:13 AM, Andrei Stebakov <lispercat@gmail.com>wrote:
I've come across this a few times using Pharo: When I try to install a new package (either through HTTP repository or Gofer) sometimes it complains about a dependency and you have a option to proceed or abandon. I guess proceeding could be dangerous in this case since you never know when this missing dependency will backfire.
exactly.
What's the general rule of how to look for a package with the missing class(es)? Let's say I was trying to install Pastell (XPath library) via repository and during installation I had the message:
This package depends on the following classes: XMLNodeWithElements You must resolve these dependencies before you will be able to load these definitions: XMLNodeWithElements>>/ XMLNodeWithElements>>// XMLNodeWithElements>>child: XMLNodeWithElements>>children XMLNodeWithElements>>descendant: XMLNodeWithElements>>doesNotUnderstand:
Where do I go look for a package with this class implemented?
Several times I had this problem but I don't know to solve it :(
Shouldn't the package being installed check for its dependencies and install them prior to its own installation (or at least give you a hint where this missing class belongs)?
As they already answered, that's the intention of Metacello: http://code.google.com/p/metacello/ There is a tutorial you can follow. Cheers Mariano
Thank you, Andrei
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project