Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:32823 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 31962 invoked by uid 1010); 17 Oct 2007 06:48:19 -0000 Delivered-To: ezmlm-scan-internals@lists.php.net Delivered-To: ezmlm-internals@lists.php.net Received: (qmail 31947 invoked from network); 17 Oct 2007 06:48:19 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 17 Oct 2007 06:48:19 -0000 Authentication-Results: pb1.pair.com header.from=seanius@seanius.net; sender-id=unknown Authentication-Results: pb1.pair.com smtp.mail=seanius@seanius.net; spf=permerror; sender-id=unknown Received-SPF: error (pb1.pair.com: domain seanius.net from 66.93.22.232 cause and error) X-PHP-List-Original-Sender: seanius@seanius.net X-Host-Fingerprint: 66.93.22.232 cobija.connexer.com Received: from [66.93.22.232] ([66.93.22.232:54728] helo=cobija.connexer.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 21/65-14332-230B5174 for ; Wed, 17 Oct 2007 02:48:18 -0400 Received: from rangda.local (h-234-204.A189.cust.bahnhof.se [81.170.234.204]) by cobija.connexer.com (Postfix) with ESMTP id 6B35117C413 for ; Wed, 17 Oct 2007 02:48:16 -0400 (EDT) To: internals@lists.php.net Date: Wed, 17 Oct 2007 08:48:22 +0200 User-Agent: KMail/1.9.7 References: <64ED731E-CA44-498E-9AF9-C9B00037B863@omniti.com> <200710151910.49707.seanius@seanius.net> <47155266.4010209@zend.com> In-Reply-To: <47155266.4010209@zend.com> MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart1568435.Q6rERgJLbP"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit Message-ID: <200710170848.23053.seanius@seanius.net> Subject: Re: [PHP-DEV] Large file support for PHP From: seanius@seanius.net (sean finney) --nextPart1568435.Q6rERgJLbP Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline hi stanislav, On Wednesday 17 October 2007 02:08:06 am Stanislav Malyshev wrote: > > yes, this is of course a big deal for some people, esp if you're using > > proprietary software that's built against the "original" abi. of course > > if you're only using OSS extensions, you can simply recompile them > > against the new api/abi and there's no drawback. > > That's not only about OSS vs. proprietary - even if you use only OSS > extensions, but you do not compile everything from the source on each > install (and have many platforms to install on - such as big > organization with dozens of servers), you might have trouble. but this wouldn't be any different from any other api/abi bump. furthermor= e,=20 in the context of running debian (and by extension ubuntu) servers, you=20 wouldn't need to do anything if you were only using the pre-packaged module= s,=20 as they'd be compiled with the right options for you, ideally. so you'd ju= st=20 need to do an "apt-get upgrade", etc. and if you were using other pecl=20 extensions, i think the command to update that isn't so complicated either = :) sean --nextPart1568435.Q6rERgJLbP Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQBHFbA3ynjLPm522B0RAknTAJ9rzQhJNBG1IhvvUJjL3l7jpMicsACfReA/ 7WgpyPbPzhHHkCxoszkoIsM= =Rwub -----END PGP SIGNATURE----- --nextPart1568435.Q6rERgJLbP--