BC break?

Consider this scenario: Package Foo extends PEAR, although it doesn't use the PEAR class at all. This means that Foo::raiseError() should work from a script that is using package Foo. It's obvious that PEAR.php shouldn't be included, and Foo shouldn't extend PEAR needlessly. But would it break BC to remove it? On a similar note, say Foo depends on Bar, and Bar changes it's API and Foo updates accordingly. Methods used directly by the user that are inherited from Bar don't work anymore, apparently breaking Foo's API. How does one deal with this? There's no real reason to release Foo2, but the API *technically* did change... -- Marshall Roch http://pear.php.net/user/mroch