Date: 01/18/01
- Next message: Kristian Koehntopp: "[phplib] Re: [phpslash-users] [Fwd: [phplib] [Fwd: [PHP-PEAR] Merging PHPLIB into PEAR]]"
- Previous message: Kristian Koehntopp: "Re: [phplib] [Fwd: [PHP-PEAR] Merging PHPLIB into PEAR]"
- Next in thread: Kristian Koehntopp: "[phplib] Re: [phpslash-users] [Fwd: [phplib] [Fwd: [PHP-PEAR] Merging PHPLIB into PEAR]]"
- Maybe reply: Kristian Koehntopp: "[phplib] Re: [phpslash-users] [Fwd: [phplib] [Fwd: [PHP-PEAR] Merging PHPLIB into PEAR]]"
- Reply: Chris Johnson: "RE: [phplib] Re: [phpslash-users] [Fwd: [phplib] [Fwd: [PHP-PEAR] Merging PHPLIB into PEAR]]"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
In netuse.lists.phpslash you write:
>- Continue using phplib (Ulf and Kristian are writing a wrapper class to
>support phplib in PEAR for the short term) and deal with migrating to
>PEAR in the next devel cycle.. (I personally think PEAR sucks, same with
>php's built in session code which things will be rewritten to use, as
>well as PEAR::DB and friends)
>- Rewrite everything (again) to use something like binarycloud (which
>might not be that bad.. it seems cool, I need to look into more, it's
>got auth/user/perm/templates.. I moght do this for a diffrent project
>I'm working on: Carousel - that other thing down there in my sig :)).
>Or we can all go home and let phpNuke have the glory.
I fully understand that there is _much_ code out there using
PHPLIB. I assure you, I won't let that code break. I won't
hasten things.
But: There is very little use in maintaining two large class
repositories with incompatible interfaces (or three, counting in
binarycloud as well). PEAR is the one repository that is being
distributed with each install of PHP.
If you want to be part of a standard PHP install, you become
part of PEAR. If you do not like PEAR, you must become part of
PEAR and change it to suit your needs. We (Ulf and I) will do
that, and when we are satisfied, we invite you to do the
transition.
I recommend that the Binarycloud people have a look at PEAR as
well, and hit it hard. There is much in it that (IMHO) sucks at
the moment. If you do not kill what sucks, it will become
standard part of each PHP install. This cannot be what you or
anybody wants.
Finally: PHP 4 is the future. PHP 3 has not been developed
actively for some months now. There is less and less bugfixing
done on it. Force your providers to upgrade. There will be less
and less support for PHP 3 by library creators and maintainers.
And again: We try to break as little code as possible and we try
to do this migration with you, the PHPLIB users, and make it as
smooth as possible and over an extended timeframe. But we will
become of the PHP standard install, and that's a good thing.
Kristian
---------------------------------------------------------------------
To unsubscribe, e-mail: phplib-unsubscribe <email protected>
For additional commands, e-mail: phplib-help <email protected>
- Next message: Kristian Koehntopp: "[phplib] Re: [phpslash-users] [Fwd: [phplib] [Fwd: [PHP-PEAR] Merging PHPLIB into PEAR]]"
- Previous message: Kristian Koehntopp: "Re: [phplib] [Fwd: [PHP-PEAR] Merging PHPLIB into PEAR]"
- Next in thread: Kristian Koehntopp: "[phplib] Re: [phpslash-users] [Fwd: [phplib] [Fwd: [PHP-PEAR] Merging PHPLIB into PEAR]]"
- Maybe reply: Kristian Koehntopp: "[phplib] Re: [phpslash-users] [Fwd: [phplib] [Fwd: [PHP-PEAR] Merging PHPLIB into PEAR]]"
- Reply: Chris Johnson: "RE: [phplib] Re: [phpslash-users] [Fwd: [phplib] [Fwd: [PHP-PEAR] Merging PHPLIB into PEAR]]"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

