Re: Re: [phplib] Re: [PHP-PEAR] PHPLib and Pear merge

[Maxim Derkachev <kot@books.ru>] > Hello Sebastian, > > Actually, I've spent this time to examine how PEAR::DB works :). I > found it useless to me in its current state and I'm against of using > it instead of DB_SQL in PHPLib merged into PEAR. If the use of the > PEAR::DB is a condition of merging PHPLib into PEAR, I'm against > that merge. Why is PEAR DB unusable for you? > SB> Yesterday, the following thought formed in my head: Why not > SB> take the classes from PHPLIB that stand for themselves (like > SB> Forms, Tree, Menu) and "merge" them into the appropriate PEAR/ > SB> directories and put the PHPLIB Framework > SB> (Auth/User/Perm/Page/...) into PEAR/PHPLIB/ as a bundle of > SB> classes? > > Why not? Then the question is what PEAR people think PEAR should be? > If it should be like CPAN (a repository), there is no problem. If the > way is building a framework (where, e.g., every package that use a > database _must_ use PEAR::DB), I see big problems. PEAR is a repository, but we also aim to keep the overlap in functionality at a minimum. - Stig -- Stig Sæther Bakken <ssb@fast.no> Fast Search & Transfer ASA, Trondheim, Norway