Re: RFC on merge of PHPLib and Pear

Quoting Björn Schotte <bjoern@baer.main.de>: > Why that? PHPLIB consists of several classes which don't > depend on each other, so why put those execellent things > outside of PEAR? Why not putting i.e. Cache/ outside of PEAR > because it could be part of an app framework? But the parts of PHPLIB that I'm saying should remain outside PEAR - auth, user, and perm - _do_ depend on each other. That's the only thing I'm saying should be outside. Cache:: is a building block you can use; auth/user/perm define a lot of how you're building your app. -chuck -- Charles Hagenbuch, <chuck@horde.org> "Live, from Washington, where the doctors were telling us what they did, and did not, do with Vice President Cheney." -Dan Rather