Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:85818
Return-Path: <laruence@gmail.com>
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Delivered-To: mailing list internals@lists.php.net
Received: (qmail 43070 invoked from network); 15 Apr 2015 05:09:06 -0000
Received: from unknown (HELO lists.php.net) (127.0.0.1)
  by localhost with SMTP; 15 Apr 2015 05:09:06 -0000
Authentication-Results: pb1.pair.com header.from=laruence@gmail.com; sender-id=pass
Authentication-Results: pb1.pair.com smtp.mail=laruence@gmail.com; spf=pass; sender-id=pass
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.220.49 as permitted sender)
X-PHP-List-Original-Sender: laruence@gmail.com
X-Host-Fingerprint: 209.85.220.49 mail-pa0-f49.google.com  
Received: from [209.85.220.49] ([209.85.220.49:34984] helo=mail-pa0-f49.google.com)
	by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP
	id 8B/1D-47925-072FD255 for <internals@lists.php.net>; Wed, 15 Apr 2015 01:09:05 -0400
Received: by pabtp1 with SMTP id tp1so37180276pab.2
        for <internals@lists.php.net>; Tue, 14 Apr 2015 22:09:01 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=gmail.com; s=20120113;
        h=content-type:mime-version:subject:from:in-reply-to:date:cc
         :content-transfer-encoding:message-id:references:to;
        bh=PmxZJgrc6kd+8BgKRNleUqR6XYDH2/Q4vBEEkNSftUg=;
        b=lR5PxLzTgB3zY/ZdVQWF4lbzGUu1RPnuqXbf3BMZbgs9lj6mcV4AIp/NQAUUJZ912g
         vYAfWagcxjV/KD0qdHlMIInIqdUW7GHEWmXK3iuVX19r1INZJ/kfxg+ZF/rTHL8YRugr
         SNaR8yokku7mL4pFT1nyxxgkWClFnqOT1oWnRssXyHnY0cWtXiVH6cisF9L6cL5uUCSO
         h2DyhhiaTA67Vaw7uoSW97L1RHG9beU5qHOtagbqwQ98NIvyvADGarZY5wNp8Yiyj5jc
         4eUKa2nT8sPFbTzJ5t7IwWg709uko816TxkmHZVrW+2zsI2s8jyGNuAD3htumSjuf8yF
         IFdA==
X-Received: by 10.68.88.196 with SMTP id bi4mr43226077pbb.130.1429074541721;
        Tue, 14 Apr 2015 22:09:01 -0700 (PDT)
Received: from [10.10.0.5] ([108.61.201.12])
        by mx.google.com with ESMTPSA id qb7sm2720619pbc.43.2015.04.14.22.08.59
        (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128);
        Tue, 14 Apr 2015 22:09:00 -0700 (PDT)
Content-Type: text/plain;
	charset=gb2312
Mime-Version: 1.0 (1.0)
X-Mailer: iPhone Mail (12D508)
In-Reply-To: <CAEZPtU6gT7H4qavwPsdV1FT5y41ru2mdCB7f0tKFeYXoJRCG-g@mail.gmail.com>
Date: Wed, 15 Apr 2015 13:08:56 +0800
Cc: PHP internals <internals@lists.php.net>
Content-Transfer-Encoding: quoted-printable
Message-ID: <BC139705-A439-4BBD-B008-231730F94638@gmail.com>
References: <CAEZPtU6gT7H4qavwPsdV1FT5y41ru2mdCB7f0tKFeYXoJRCG-g@mail.gmail.com>
To: Pierre Joye <pierre.php@gmail.com>
Subject: Re: [PHP-DEV] Fixing bundled extension version mess
From: laruence@gmail.com (Xinchen Hui)

Hey=A3=BA

Sent from my iPhone

> On Apr 15, 2015, at 10:21 AM, Pierre Joye <pierre.php@gmail.com> wrote:
>=20
> hi,
>=20
> We tried that many times but we fail to handle the version of bundled
> extensions.
>=20
> Along with some installer work and other integration (projects
> dependencies management, composer or other), we need to find a way to
> get rid of this problem.
>=20
> What do you think to simply use the PHP version number instead of some
> outdated (most of the time) version for all bundled extensions?
in generally, I am +1 on this

I was also thinking of this yesterday, but the problem with opcache is:

We already release pecl opcache with version 7.0.X

If we now use Php version instead, then use may be confused with the version=
s?

Anyway,  I still +1 on this

Thanks
> For extensions being available both bundled or externally, the
> external versions will provide a sane version number when installed
> (like timezone db or other).
>=20
> Doing so will make requirements management much easier by adding a
> list of core extensions per PHP version.
>=20
> Thoughts?
>=20
> Cheers,
> --=20
> Pierre
>=20
> @pierrejoye | http://www.libgd.org
>=20
> --=20
> PHP Internals - PHP Runtime Development Mailing List
> To unsubscribe, visit: http://www.php.net/unsub.php