Re: something I noticed re:licenses.
| From: | nathan r. hruby | Date: | Fri, 19 Jan 2001 22:10:23 +0000 |
| Subject: | Re: something I noticed re:licenses. | ||
| References: | 1 | Groups: | php.pear |
| Request: | Send a blank email to php-pear+get-1102@lists.php.net to get a copy of this message | ||
On 1/19/01 4:43 PM, "Kristian Koehntopp" <kris@koehntopp.de> wrote:
> On Fri, Jan 19, 2001 at 04:28:49PM -0500, Chuck Hagenbuch wrote:
>> The PHPLIB folks claim a large installed base and that PEAR
>> should accept the phplib code as it is so as not to create
>> compatibility problems.
>
> Not code, only the API. I have obligations to an installed base,
> but these cover only the API, not the actual code that is being
> run behind that API. This is an essential difference.
>
> Kristian
>
Agreed. I don't think that anyone in phplib-land expected the current code
to simply *poof* into PEAR as is. I think we all know that there is some
work to be done to PEAR-ify phplib in terms of using php4/PEAR syntax,
methodology, and conventions, which IMHO is a good thing (adherence to a
larger standard). I think we all realize that some stuff will get broken,
in terms of phplib, as well.
The wrapper classes are a different story and I don't think they should go
into PEAR. A phplib-pear file should be availible from some source (maybe
the phplib site, maybe in the php tarball, maybe SourceForge, I don't
know..) that provides a phplib-7.2 compatible interface to PEAR for existing
applications that require phplib and have not upgraded to the new
syntax/API.
I think that there's a miscommunication somewhere here between, phplib, PEAR
and what exactly is going on. (Or maybe I'm just daft.. Always a
possibility.. Hey look.. Shiny things! Oohhhh.)
Anyway. My understanding is that phplib will be migrated/ported to PEAR and
that the phplib classes will be PEAR-ified and pigeon-holed into their
proper places in the PEAR tree (another, separate discussion). In that move
some functionality would get broken by using php native sessions, PEAR::DB
(if chosen) etc.. etc.. And the wrapper classes would provide backwards
compatibility for a while till app developers and phplib users had a chance
to test, try and port to the native PEAR packages.
Is this the correct assumption, or am I looking at shiny things again?
-n
........
nathan hruby
Webmaster: UGA Department of Drama and Theatre
Project Maintainer: phpSlash, Carousel
nhruby@arches.uga.edu
........