Since I'm working on something related... what's the verdict here? :)
> On 20.04.2015, at 20:00, Jakub Zelenka wrote:
>
> Hi,
>
> On Thu, Apr 16, 2015 at 1:21 PM, Pierre Joye wrote:
>
>> On Thu, Apr 16, 2015 at 6:27 PM, François Laupretre
>> wrote:
De : Pierre Joye [mailto:pierre@
Hi,
On Thu, Apr 16, 2015 at 1:21 PM, Pierre Joye wrote:
> On Thu, Apr 16, 2015 at 6:27 PM, François Laupretre
> wrote:
> >> De : Pierre Joye [mailto:pierre@gmail.com]
> >>
> >> The problem we have now is core extensions with senseless versions
> >> without
> >> any external versions. Or mix
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Le 15/04/2015 11:47, Pierre Joye a écrit :
> On Apr 15, 2015 4:12 PM, "Remi Collet"
> wrote: , I still +1 on this
>>>
>>
>> I'm mostly +1 on this proposal.
>>
>> Of course extension (like oci8) should be able to keep its
>> version (when it is cor
On Thu, Apr 16, 2015 at 6:27 PM, François Laupretre wrote:
>> De : Pierre Joye [mailto:pierre@gmail.com]
>>
>> The problem we have now is core extensions with senseless versions
>> without
>> any external versions. Or mixed codebase, like core is a mix of external
>> and core specific codes wh
> De : Pierre Joye [mailto:pierre@gmail.com]
>
> The problem we have now is core extensions with senseless versions
> without
> any external versions. Or mixed codebase, like core is a mix of external
> and core specific codes which is not in any external releases. That is what
> we should solv
On Apr 16, 2015 6:23 AM, "christopher jones"
wrote:
>
>
>
> On 4/14/15 9:58 PM, Pierre Joye wrote:
>>
>> On Wed, Apr 15, 2015 at 10:51 AM, christopher jones
>> wrote:
>>>
>>>
>>>
>>> On 4/14/15 7:21 PM, Pierre Joye wrote:
hi,
We tried that many times but we fail to handle
On 4/14/15 9:58 PM, Pierre Joye wrote:
On Wed, Apr 15, 2015 at 10:51 AM, christopher jones
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
d
On Apr 15, 2015 10:07 PM, "François Laupretre" wrote:
>
> >De : Pierre Joye [mailto:pierre@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 sinc
On Wed, Apr 15, 2015 at 9:07 AM, François Laupretre
wrote:
> >De : Pierre Joye [mailto:pierre@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
>De : Pierre Joye [mailto:pierre@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
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.
Installer can easily knows which uses what.
Or am I missing somethin
On Wed, Apr 15, 2015 at 1:01 PM, François Laupretre
wrote:
> > De : Pierre Joye [mailto:pierre@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 avail
On Apr 15, 2015 6:01 PM, "François Laupretre" wrote:
>
> > De : Pierre Joye [mailto:pierre@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
> De : Pierre Joye [mailto:pierre@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 change more
often than the bundled ver
On Apr 15, 2015 4:12 PM, "Remi Collet" wrote:
, I still +1 on this
> >
>
> I'm mostly +1 on this proposal.
>
> Of course extension (like oci8) should be able to keep its version (when
> it is correctly managed).
>
> Yes opcache have an issue... so we probably have to keep 7.0.x until PHP
7.1
>
>
Le 15/04/2015 07:08, Xinchen Hui a écrit :
> Hey：
>
> Sent from my iPhone
>
>> On Apr 15, 2015, at 10:21 AM, 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 (project
Hey：
Sent from my iPhone
> On Apr 15, 2015, at 10:21 AM, 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
On Wed, Apr 15, 2015 at 10:51 AM, christopher jones
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 manageme
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 y
On Tue, Apr 14, 2015 at 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
20 matches
Mail list logo
