On Apr 16, 2015 6:23 AM, "christopher jones" <christopher.jo...@oracle.com> wrote: > > > > On 4/14/15 9:58 PM, Pierre Joye wrote: >> >> On Wed, Apr 15, 2015 at 10:51 AM, christopher jones >> <christopher.jo...@oracle.com> wrote: >>> >>> >>> >>> On 4/14/15 7:21 PM, Pierre Joye wrote: >>>> >>>> >>>> hi, >>>> >>>> We tried that many times but we fail to handle the version of bundled >>>> extensions. >>>> >>>> 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. >>>> >>>> What do you think to simply use the PHP version number instead of some >>>> outdated (most of the time) version for all bundled extensions? >>>> >>>> For extensions being available both bundled or externally, the >>>> external versions will provide a sane version number when installed >>>> (like timezone db or other). >>>> >>>> Doing so will make requirements management much easier by adding a >>>> list of core extensions per PHP version. >>>> >>>> Thoughts? >>>> >>>> Cheers, >>>> >>> >>> What do you mean external version? >> >> >> Too many "versions" :) installed not using the core sources but >> github, pecl, whatever. >> >>> I don't have a problem with extensions having different versions >>> depending how they are installed. >> >> >> Cheers, >> Pierre >> > > What I really meant to ask was about your proposed numbering scheme > (or #ifdefs or whatever) for versioning of external packages. (I read > "external version" as "version of the external package"). Subsequent > emails in the thread answered this.
And sounds good to you?
