Newsgroups: php.internals,php.webmaster Path: news.php.net Xref: news.php.net php.internals:86664 php.webmaster:21351 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 44836 invoked from network); 15 Jun 2015 15:38:25 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 15 Jun 2015 15:38:25 -0000 Authentication-Results: pb1.pair.com smtp.mail=anatol.php@belski.net; spf=permerror; sender-id=unknown Authentication-Results: pb1.pair.com header.from=anatol.php@belski.net; sender-id=unknown Received-SPF: error (pb1.pair.com: domain belski.net from 85.214.73.107 cause and error) X-PHP-List-Original-Sender: anatol.php@belski.net X-Host-Fingerprint: 85.214.73.107 klapt.com Received: from [85.214.73.107] ([85.214.73.107:51602] helo=h1123647.serverkompetenz.net) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 88/C3-25272-071FE755 for ; Mon, 15 Jun 2015 11:38:25 -0400 Received: by h1123647.serverkompetenz.net (Postfix, from userid 1006) id 5DF266D2038; Mon, 15 Jun 2015 17:38:21 +0200 (CEST) X-Spam-Checker-Version: SpamAssassin 3.3.2 (2011-06-06) on h1123647.serverkompetenz.net X-Spam-Level: X-Spam-Status: No, score=-2.9 required=2.5 tests=ALL_TRUSTED,BAYES_00 autolearn=unavailable version=3.3.2 Received: from w530phpdev (pD9FD2BF6.dip0.t-ipconnect.de [217.253.43.246]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by h1123647.serverkompetenz.net (Postfix) with ESMTPSA id 063FC23D615B; Mon, 15 Jun 2015 17:38:18 +0200 (CEST) To: =?utf-8?Q?'Johannes_Schl=C3=BCter'?= , "'Christoph Becker'" Cc: "'Hannes Magnusson'" , "'PHP Development'" , "'PHP Webmaster ML'" References: <00c501d0a773$f84fee90$e8efcbb0$@belski.net> <557EDF48.9000800@gmx.de> <1434379932.17693.5.camel@kuechenschabe> In-Reply-To: <1434379932.17693.5.camel@kuechenschabe> Date: Mon, 15 Jun 2015 17:38:17 +0200 Message-ID: <012e01d0a781$4f4a17e0$edde47a0$@belski.net> MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable X-Mailer: Microsoft Outlook 15.0 Thread-Index: AQHpdUQkhoANRXvSxO0Sr7gX+wtPhgKluB3LAVkrseQCKPEE+AGd8A9RnT3nQ/A= Content-Language: en-us Subject: RE: [PHP-DEV] PHP7 releases vs Windows Sources? From: anatol.php@belski.net ("Anatol Belski") Hi Johannes, > -----Original Message----- > From: Johannes Schl=C3=BCter [mailto:johannes@schlueters.de] > Sent: Monday, June 15, 2015 4:52 PM > To: Christoph Becker > Cc: Hannes Magnusson; Anatol Belski; PHP Development; PHP Webmaster ML > Subject: Re: [PHP-DEV] PHP7 releases vs Windows Sources? >=20 > On Mon, 2015-06-15 at 16:20 +0200, Christoph Becker wrote: > > Hannes Magnusson wrote: > > > > > Then this fix doesn't make any sense -- you are saying if I = download > > > the .tar.gz and .zip and extract those two, I will have precisely > > > the same sources? > > > Then this fix should be reverted as there is isn't any special > > > Windows Sources and the official releases should work just fine. > > > > There is some difference (timestamps?) which causes building from = the > > tarred sources to fail on Windows (see bug #69829). >=20 > "touching" generated files as part of the packaging process is a good = idea for all > platforms. >=20 > > Furthermore > > extracting the tarred sources with 7zip (which seems to be a pretty > > common archiver) results in spurious PaxHeaders.##### directories, > > what is bug in 7zip[1], and doesn't really affect the build, but is > > confusing nonetheless (and requires more disk space). > > > > At least until these issue are solved, IMO it's better to link to = the > > "Windows" sources packaged as .zip. >=20 > If there is a need for zip archives I'd put them next to tar.gz etc. = and distribute > them via our mirror network. >=20 Yep, this could work and were probably proper solution. Except we = wouldn't add some issue for the non Windows users :) I'm not sure, why = is it done so ATM, probably it has its historical reasons. But this = would probably cause us need to update the release process procedure? = And, for PHP7 or for any other as well? Currently that zipball is just = generated with the build process, so it'll need to be sent over somehow. = Were anyway doable, wondering what the other RMs would say. Frankly, = I'd leave it as it is - as long as it's reachable and documented. Regards Anatol