Date: 07/21/01
- Next message: Alan T. Miller: "RE: [phplib] [RFC] Future of phplib"
- Previous message: Björn Schotte: "Re: [phplib] [RFC] Future of phplib"
- In reply to: Bertrand Mansion: "Re: [phplib] [RFC] Future of phplib"
- Next in thread: giancarlo pinerolo: "Re: [phplib] [RFC] Future of phplib"
- Reply: giancarlo pinerolo: "Re: [phplib] [RFC] Future of phplib"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
* Bertrand Mansion wrote:
> I don't see neither why it should not be done. But it is not the point.
> 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.
I can only repeat myself: consensus was migrating PHPLIB
into PEAR and _not_ integrating it to /pear/phplib/.
-- PHP Schulungen und | International PHP Conference Schulungsmaterial: | 05. - 07.11.2001 http://thinkphp.de/ | Astron Hotel, Frankfurt http://rent-a-phpwizard.de/schulungen.php | http://www.php-kongress.de/-- Abbestellen mit Mail an: phplib-unsubscribe <email protected> Kommandoliste mit Mail an: phplib-help <email protected>
- Next message: Alan T. Miller: "RE: [phplib] [RFC] Future of phplib"
- Previous message: Björn Schotte: "Re: [phplib] [RFC] Future of phplib"
- In reply to: Bertrand Mansion: "Re: [phplib] [RFC] Future of phplib"
- Next in thread: giancarlo pinerolo: "Re: [phplib] [RFC] Future of phplib"
- Reply: giancarlo pinerolo: "Re: [phplib] [RFC] Future of phplib"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

