Newsgroups: php.internals,php.internals.win
Path: news.php.net
Xref: news.php.net php.internals:39507 php.internals.win:138
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: unknown (pb1.pair.com: domain php.net does not designate 64.99.136.181 as permitted sender)
Message-ID: <037601c8f327$efb5ead0$a7bd614d@foxbox>
To: "Pierre Joye" <pierre.php@gmail.com>
Cc: <internals-win@lists.php.net>,
	"internals" <internals@lists.php.net>
References: <032801c8f31f$553595d0$a7bd614d@foxbox> <fe05d1540807310816r18f7a6ddk63f2ade7906525eb@mail.gmail.com> <034701c8f322$91f6d710$a7bd614d@foxbox> <fe05d1540807310837r74bd66a5lf81a43ff04c599d7@mail.gmail.com>
Date: Thu, 31 Jul 2008 17:10:21 +0100
MIME-Version: 1.0
Content-Type: text/plain;
	format=flowed;
	charset="iso-8859-1";
	reply-type=original
Content-Transfer-Encoding: 7bit
Subject: Re: [INTERNALS-WIN] Re: [PHP-DEV] Broken Windows build
From: steph@php.net ("Steph Fox")

> Uninstall the old one, install the new one, et voila, no need to kill
> a cat to get that solved. Now that we have cleared the true issue, let
> us go back to work :)

Hard drive has 2.02 gigs, SDK installment requires 'at least 1.4 GB'. No 
way, can't risk it, I need this laptop for work.

The true issue is that the build worked here until a few days ago, *without* 
the need to upgrade or install anything, and no longer does. You want to 
move the Windows stuff on from VC6, fine, but you actually just dropped 
support for it during the final moments of a release cycle and that is *not* 
fine. You're also being more than a little ingenuous in declaring that 
there's been no change in the requirements. The crypt changes included a 
specific change in the requirements, and since you wrote it, you cannot 
possibly be unaware of that fact.

It might have been wise to advertise that change in requirements before 
committing the patch - or to find some way around it.

- Steph