Sparks and Pear Libraries?

[eluser]Phil Sturgeon[/eluser]
The wiki is not gospel and is often either wrong, really bad or just out of date.

I'd just bang the PHP classes in with your spark then you can manage the dependencies.

The whole point of sparks is that they are self encapsulating, so including the file is a big help. Pear libs install system wide meaning an upgrade could break random apps, as we see happening in the ruby world with gems all the time.

The one issue is that you need to check a class doesn't exist before including it, or multiple PEAR.php dependent sparks will bitch about the double definition of the class.