Date: 07/21/01
- Next message: nathan r. hruby: "Re: [phplib] [RFC] Future of phplib"
- Previous message: darcy w. christ: "Re: [phplib] [RFC] Future of phplib"
- In reply to: Björn Schotte: "Re: [phplib] [RFC] Future of phplib"
- Next in thread: Tarique Sani
email protected>>: "Re: [phplib] [RFC] Future of phplib" - Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
> > There already has been a discussion whether or not PHPLIB (just like Binary
> > Cloud) should be part of PEAR and the conclusion was no.
>
> That's true because the discussion point was "integrating
> whole PHPLIB". This is actually not the point, as you see
> on Jon' post referring to Sebastian Bergmann's words:
>
> | It was agreed not to put PHPLIB as a whole into /pear/phplib
>
> Nobody says integrating the whole PHPLIB into /pear/phplib/.
> E.g. PHPLIB's template class (if it would be integrated into
> PEAR) should take place in pear/HTML/Template/, PHPLIB's auth
> class should take place in pear/somewhere/else/, and so on.
This sounds wise. Scorporate things is wise.
If PEAR mantains the promise of easy and uniform integration, not
adhering is a mistake.
As I said, I see there are already integration problems *whithin* PHPLib
and
between different PHPLib applications that need to be solved... Adopting
some uniform standard, common with a lot of other extensions, can be a
great gain.
Giancarlo
> I can only repeat myself: consensus was migrating PHPLIB
> into PEAR and _not_ integrating it to /pear/phplib/.
-- Abbestellen mit Mail an: phplib-unsubscribe <email protected> Kommandoliste mit Mail an: phplib-help <email protected>
- Next message: nathan r. hruby: "Re: [phplib] [RFC] Future of phplib"
- Previous message: darcy w. christ: "Re: [phplib] [RFC] Future of phplib"
- In reply to: Björn Schotte: "Re: [phplib] [RFC] Future of phplib"
- Next in thread: Tarique Sani
email protected>>: "Re: [phplib] [RFC] Future of phplib" - Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

