Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:85823 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 78066 invoked from network); 15 Apr 2015 13:19:52 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 15 Apr 2015 13:19:52 -0000 Authentication-Results: pb1.pair.com header.from=kontakt@beberlei.de; sender-id=unknown Authentication-Results: pb1.pair.com smtp.mail=kontakt@beberlei.de; spf=permerror; sender-id=unknown Received-SPF: error (pb1.pair.com: domain beberlei.de from 209.85.212.171 cause and error) X-PHP-List-Original-Sender: kontakt@beberlei.de X-Host-Fingerprint: 209.85.212.171 mail-wi0-f171.google.com Received: from [209.85.212.171] ([209.85.212.171:36635] helo=mail-wi0-f171.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 68/C0-05595-6756E255 for ; Wed, 15 Apr 2015 09:19:51 -0400 Received: by wizk4 with SMTP id k4so154481937wiz.1 for ; Wed, 15 Apr 2015 06:19:48 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=rWUpwCYC39/6pnltjB/fOnr1Ij9AGRWDn2SET70uTVA=; b=gD+bhVNdZ4039qQjwyQtgVJ10h3J1jPiBGFITjBWQMpd+u1OyJo61M/f8zztbpuCvU 0Tc73FufCLboMjcXFRhSyzmP88kvpG7aBW27Mlp614YuIf55S/qx1PZTONzwI3AB92q0 hsnRgd8B/ZhDmwPbPKjPagn8YuBe5HkebziX78DODuwHRxxPUbeBN+XEku4hmV9e7RaH 8uVAoAknlWD0mbnVUK194riIYdbepgEBPt7qBKhPYZvNgVYgdU2s8n2Y5l2mnFzoR1NW HuLB7n/BqD3HW5yKEPd1jfc8LLSrTVVIbSKB+ZHj+YQdKJcAlBdULv+qUae0gOW+LaBP YSPw== X-Gm-Message-State: ALoCoQlQkbDhIfWStUWqYNQSMjKiYF5C1M+/GcYX1n3qLsXeBF32qDTM3Dw4grNbKLSI0KiYOwmj MIME-Version: 1.0 X-Received: by 10.194.185.9 with SMTP id ey9mr50491090wjc.135.1429103988061; Wed, 15 Apr 2015 06:19:48 -0700 (PDT) Received: by 10.194.36.134 with HTTP; Wed, 15 Apr 2015 06:19:47 -0700 (PDT) X-Originating-IP: [93.129.71.8] In-Reply-To: <012601d0776b$8672a250$9357e6f0$@php.net> References: <012601d0776b$8672a250$9357e6f0$@php.net> Date: Wed, 15 Apr 2015 15:19:47 +0200 Message-ID: To: francois Cc: Pierre Joye , PHP internals Content-Type: multipart/alternative; boundary=047d7bd6adce8e502c0513c3332a Subject: Re: [PHP-DEV] Fixing bundled extension version mess From: kontakt@beberlei.de (Benjamin Eberlei) --047d7bd6adce8e502c0513c3332a Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable On Wed, Apr 15, 2015 at 1:01 PM, Fran=C3=A7ois Laupretre wrote: > > De : Pierre Joye [mailto:pierre.php@gmail.com] > > > > What do you think to simply use the PHP version number instead of some > > outdated (most of the time) version for all bundled extensions? > > As the idea is that extensions available externally are supposed to chang= e > more often than the bundled version, why wouldn't we add a fourth number = to > their version ? By definition, version X.Y.Z.0 would correspond to the > version distributed with PHP X.Y.Z. > But its not clear if this makes sense. if you have extension "foo" in php 7.0.1 and 7.0.2 and you want to provide an override via pecl, would you need to release 7.0.1.1 and 7.0.2.1? That doesnt make sense imho. Its either PHP Version =3D=3D Ext Version or Ext has its own version. By default it should be the first, but some maintainers could deviate if they wish. > > Also : > > - When we distribute the same extension code with PHP 5.4, 5.5, and 5.6, > what is the version we set for this code in pecl ? Will we have to create= 3 > branches, just for versions ? > > - If a new PHP version is released, do we need to change the extension > version even if the code was not modified ? > > Regards > > Fran=C3=A7ois > > > -- > PHP Internals - PHP Runtime Development Mailing List > To unsubscribe, visit: http://www.php.net/unsub.php > > --047d7bd6adce8e502c0513c3332a--