Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:85826 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 89702 invoked from network); 15 Apr 2015 15:14:10 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 15 Apr 2015 15:14:10 -0000 Authentication-Results: pb1.pair.com header.from=derokorian@gmail.com; sender-id=pass Authentication-Results: pb1.pair.com smtp.mail=derokorian@gmail.com; spf=pass; sender-id=pass Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.212.175 as permitted sender) X-PHP-List-Original-Sender: derokorian@gmail.com X-Host-Fingerprint: 209.85.212.175 mail-wi0-f175.google.com Received: from [209.85.212.175] ([209.85.212.175:36625] helo=mail-wi0-f175.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 27/B2-05595-0408E255 for ; Wed, 15 Apr 2015 11:14:09 -0400 Received: by wizk4 with SMTP id k4so159053661wiz.1 for ; Wed, 15 Apr 2015 08:14:05 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=nZijSOu0lSifikIOtx501koXmZjIiiW4TaoPGUkilxo=; b=UwuG+gGcFYLp3CBQpxJHwlIpa+T1w3eg503eMPZXOXwLVvRQ+hzjODkH50jyq2zCyG 3z1UyhQ+67llYfM2mPP6QiG3mNNf2jmS7+BG5E/bxbVrGo0mdXfpSzrQK0izokTRVq1J /FlKD824TZpGbhPYBoXTQiL57tCTrUS/hfrWsnXflA0ABsRbaw09l4JLe37DXLXFQE6X nqTTL3blLj7izxWu1PoXH5pwKMBMzzHhqvT3pMmgk/B4RQ1EM7BHNyLtp6H+B6OE4p/8 X0JEpwikm72qE98xLrKi1hQbHFDXOc2SqQOuDYQbnY03GPn/7l03ZiNsIqYYf2UPMHR8 lSGg== MIME-Version: 1.0 X-Received: by 10.180.230.226 with SMTP id tb2mr42649169wic.64.1429110845842; Wed, 15 Apr 2015 08:14:05 -0700 (PDT) Received: by 10.28.7.196 with HTTP; Wed, 15 Apr 2015 08:14:05 -0700 (PDT) In-Reply-To: <014401d0778d$e5683410$b0389c30$@php.net> References: <012601d0776b$8672a250$9357e6f0$@php.net> <014401d0778d$e5683410$b0389c30$@php.net> Date: Wed, 15 Apr 2015 09:14:05 -0600 Message-ID: To: francois@php.net Cc: Pierre Joye , Benjamin Eberlei , PHP internals Content-Type: multipart/alternative; boundary=001a113612bc4fae980513c4ccab Subject: Re: [PHP-DEV] Fixing bundled extension version mess From: derokorian@gmail.com (Ryan Pallas) --001a113612bc4fae980513c4ccab Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable On Wed, Apr 15, 2015 at 9:07 AM, Fran=C3=A7ois Laupretre wrote: > >De : Pierre Joye [mailto:pierre.php@gmail.com] > > > > Again, take #3, ext released in and outiside the core will use the > external version number everywhere. Like oci, zip and other well managed > versions. > > The stupid think like 0.1 since 8 years will use the php version. That > is all. > > > > Or am I missing something obvious? > > No, I just didn't understand you were just talking about extensions *not* > released outside of the core distrib. > > So, I am adapting my questions :) : > > - When we distribute the same extension code in more than one PHP release= , > which version do we set for this extension ? Do we set a different versio= n > for the same code in each release ? > I would like to see the numbers representative of changes. In that light, the version number should change, because its a new "package" even if the same code. The main I think it should change, is because many of the distros don't "include" all the core extensions (for example, installing php from apt-get in ubuntu 14.04 installs 5.5 but not with ZendOptimizer) and these extensions are separate install. As such, it would be easier to make sure you have the right things, if the versions are more specific (as per the original post in the thread). > - 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 > > - Ryan --001a113612bc4fae980513c4ccab--