On Sat, Jun 14, 2014 at 10:11 AM, Pierre Joye <[email protected]> wrote:
> On Sat, Jun 14, 2014 at 6:56 PM, Hannes Magnusson
> <[email protected]> wrote:
>> On Sat, Jun 14, 2014 at 9:12 AM, Pierre Joye <[email protected]> wrote:
>>> On Sat, Jun 14, 2014 at 6:04 PM, Hannes Magnusson
>>> <[email protected]> wrote:
>>>> On Sat, Jun 14, 2014 at 8:54 AM, Pierre Joye <[email protected]> wrote:
>>>>> On Sat, Jun 14, 2014 at 5:50 PM, Hannes Magnusson
>>>>> <[email protected]> wrote:
>>>>>> On Sat, Jun 14, 2014 at 8:33 AM, Pierre Joye <[email protected]> 
>>>>>> wrote:
>>>>>>> On Sat, Jun 14, 2014 at 4:31 PM, Hannes Magnusson
>>>>>>> <[email protected]> wrote:
>>>>>>>
>>>>>>>>>>> - Duplicate the server setup
>>>>>>>>>>
>>>>>>>>>> Should not be too hard. Do you have a windows VM with VC + SDK
>>>>>>>>>> installed at hand?
>>>>>>>>
>>>>>>>> I imagine the build infrastructure is however sensitive to versions -
>>>>>>>> so which Windows version do I need, VC, ..?
>>>>>>>
>>>>>>> Windows 7+.
>>>>>>>
>>>>>>> VC depends on the PHP version, as usual.
>>>>>>>
>>>>>>> Did you try to build php on windows, manually?
>>>>>>
>>>>>>
>>>>>> Sure, lets say that works flawlessly.
>>>>>
>>>>> It does yes.
>>>>>
>>>>>> What else do I need to replicate whatever does the binaries for PECL 
>>>>>> extensions?
>>>>>> Does the system update automatically daily from the php repo?
>>>>>> When I push my fixes, when will they be rolled out to the server?
>>>>>
>>>>> Please do PRs, if needed. But it has to be a serious blocking issue to
>>>>> be applied at this point.
>>>>>
>>>>
>>>> So to clarify: I am not allowed to work on snapshot capabilities for
>>>> PECL extensions?
>>>
>>> No, that's not what I said. Please re read carefully.
>>>
>>>
>>>> Furthermore you have no intentions of telling us which exact repo is
>>>> being used? (from what I can tell, its not actually the repo on
>>>> git.php.net - but your corporate repository that we cannot push to?)
>>>
>>> We have no private repo. And I have no time to argue about such FUDs.
>>>
>>>> I appreciate your help in clarifying my concerns.
>>>> I have been trying to get this implemented for an long long time now
>>>> but you guys seem to be very much against "external" contributions :(
>>>
>>>
>>> Take it like that if you like to, I told you the roadmap and what is
>>> being done (and not only by my team). You do not want to understand
>>> it, your call.
>>
>>
>> Excellent. So pushes to
>> http://git.php.net/?p=web/rmtools.git;a=summary are automatically
>> deployed every hour? Or is it once a day?
>
> I have to check.

Please do. Anatol recently pushed ~50 commits to that repo that had
been live for a long time, so it does not look like it. I have asked
this question frequently in this thread. Your latest answer was "stop
spreading FUD"?!?

If you stop being excessively passive aggressive and stop derailing
every discussion and simply answer the question we would get much
better along - and safe sooooo much time.


> But again, do PRs pls. This code is used for the core as well and RMs
> relies on it to valid releases etc.

I've no interest in touching that code. All I am trying to work on is
creating a pecl build on-demand to verify it builds before actually
rolling out a release. Upon succeeding doing that, the ideas Anatol
and I came up with earlier in this thread will be worked on.


> And *again*, this is not what we will use for pecl snapshots, not for
> the build part. So can you please understand that and stop pushing
> that all of a sudden while we are working on the final solution?

Great. So where can I implement this functionality? What will be used?
For the past now 3weeks we have been discussing this subject and not
until you decide to derail the discussion has it ever been brought up
before that anything else will be used.
So please understand that you need to be transparent, even within your
own team, since they clearly have no idea.


-Hannes

-- 
PECL development discussion Mailing List (http://pecl.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php

Reply via email to