Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:95194
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.220.41 as permitted sender)
To: Pierre Joye <pierre.php@gmail.com>, Kalle Sommer Nielsen <kalle@php.net>
References: <f790ef52-0a92-a8a3-bb3d-891713b390be@gmail.com>
 <CAJW__o29+y02aWjzHqLEdXJG9-=GtgiexU8v_hctTP=gqtQGgg@mail.gmail.com>
 <CAEZPtU6KNe0QQpCdrLF7=P51e7PmBksyVF84aUpo0UT6Fmy_9Q@mail.gmail.com>
Cc: Christopher Jones <sixd@php.net>, PHP internals <internals@lists.php.net>
Message-ID: <a86d743b-591c-f29c-663d-ec0a1cb40933@gmail.com>
Date: Mon, 15 Aug 2016 09:50:37 -0700
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:45.0)
 Gecko/20100101 Thunderbird/45.2.0
MIME-Version: 1.0
In-Reply-To: <CAEZPtU6KNe0QQpCdrLF7=P51e7PmBksyVF84aUpo0UT6Fmy_9Q@mail.gmail.com>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP-DEV] [RFC] orphan extensions cleanup
From: smalyshev@gmail.com (Stanislav Malyshev)

Hi!

>> enchant:
>> I thought Pierre maintained enchant? Despite it haven't had much real
>> activity for years
> 
> Well there are not much changes in the api.
> 
> And it works. So -1 here.

Wait, -1 for what? Having a maintainer? How that makes sense? OK,
there's no changes in API, but tomorrow comes security issue - who's
going to take care of it? Would we just ship knowingly broken code then
and not even tell users?

>> gettext
>> WordPress can optionally use gettext for some of their po/mo files,
>> I'm not entirely sure how this is today[1], but it might be worth
>> taking into consideration if there are other users.
> 
> Here as much as I do not like it. I have to oppose it. That is a major
> breakage (no, pecl is not the same).

What is major breakage - having a maintainer for this extension? I'm
sorry, I don't understand it.
-- 
Stas Malyshev
smalyshev@gmail.com