Re: [phplib] [RFC] Future of phplib From: Björn Schotte (bjoern <email protected>)
Date: 07/24/01

* nathan r. hruby wrote:
> people on this list are concerned, migrating to PEAR in the near future.

Sure, it will. And, for all of those who think PEAR folks
are lazy or are idiots:

| From: "Martin Jansen" <mail <email protected>>
| To: "PEAR Development Mailing List" <pear-dev <email protected>>
| Date: Tue, 24 Jul 2001 13:04:55 +0200
|
| Hi,
|
| what do you think of moving the code, that currently is located
| in php4/pear, to the "new" PEAR repository /pear?
|
| I think, the only things, that should be kept in php4/pear, are:
|
| - PEAR.php (we should provide global error handling)
| - PEAR/* (for the installer code)
| - CODING_STANDARS (for people wanting to contribute)
| - install-pear.txt
| - Makefile.in (Do we need this file in php4/pear?)
| - README (every good directory [tm] has a README :)
|
| What do you think? When should this be done? In PHP 4.0.7 or
| 4.1?
|
| - Martin

> However, please do not continue this thread about migrating to PEAR,
> please stop insulting a very large group of talented developers, please
> stop trying to troll for a flame war.

Neither do I insult nor do I troll for a flame war. I'll only
keep up what was consensus at the beginning of the year:
migrating PHPLIB's parts to PEAR.

> battles in the past months over this topic. You do not understand the
> intrisincs that the two groups have (and the diffrences of them) or seem

I don't care about _personal_ differences between those
two groups. I _do_ care about the advancement of PHP where
PEAR definitively is one of them. And that PHPLIB's classes
(components) like Template.inc, Auth.inc, OOHForms and
perhaps DB_Sql are definitively needed inside PEAR.

If you think that PEAR-DEV folks don't want to have other
code inside PEAR or many classes of the same functionality
(i.e. Template, DB abstraction), then please explain why
Martin wrote above mail to PEAR-DEV and why people on PEAR-DEV
say that they agree with having multiple classes of one
functionality (i.e. two Template classes and so on).

What I see is that there's only need of communication, there's
no need of saying "I feel offended, therefore I don't want
PHPLIB to migrate to PEAR". Communicate with them, get CVS
write account and begin to convert PHPLIB code to PEAR and
commit it to /pear module.

[PS: PHPLIB code is not "other's people" code to me, at least
for small parts as I have also been committing to PHPLIB
in the past.] 

-- 
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>