Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:6309
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Message-ID: <05e501c3be8e$bc5c39a0$8802a8c0@obsidian>
To: "Thies C.Arntzen" <thies@thiesos.org>,
	"PHP Internals" <internals@lists.php.net>
Cc: "Thies C.Arntzen" <thies@thiesos.org>
References: <AE808FE6-2A7B-11D8-8016-000393C4A12A@thiesos.org>
Date: Tue, 9 Dec 2003 19:57:52 -0000
Organization: The Brain Room Ltd.
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP-DEV] oci in pecl...
From: wez@thebrainroom.com ("Wez Furlong")

> it was actually my idea to for the oci8 stuff - and have some new 
> maintainer maintain it in pecl.

Yep, I remember.
 
> i see no valid reason against it. he can start hacking on it (in pecl) 
> starting today - once he is comfortable with it we'll nuke the ext/oci 
> and use(link, package) the stuff from pecl.

We can go a little bit further than that; lets move it properly in
CVS and roll a pecl release (1.0), and then Tony can continue
his work in the way that pecl is supposed to be working.
 
> loosing all history for the 2 files is not a deal at all if you ask me, 
> as not much has happened to teh code in the last many month.
 
> why do we manage to make a big deal out of everything?

I agree; I was surprised that it hadn't actually been
moved properly, but thought that someone else had handled
that (along the same lines as the surprise appearance of
pecl/perl today).
 
> if we get a new maintainer, i'd like him to be able to roll independent 
> from the main-tree. (also - don't forget - not too many ppls use 
> oracle, and those who do would be more than happy to get new 
> features/improvemnt from a new maintainer)

This is precisely what I want to encourage in PECL.

--Wez.