> 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. -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
