Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:80240 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 84710 invoked from network); 6 Jan 2015 18:44:42 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 6 Jan 2015 18:44:42 -0000 Authentication-Results: pb1.pair.com header.from=smalyshev@gmail.com; sender-id=pass Authentication-Results: pb1.pair.com smtp.mail=smalyshev@gmail.com; spf=pass; sender-id=pass Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.218.48 as permitted sender) X-PHP-List-Original-Sender: smalyshev@gmail.com X-Host-Fingerprint: 209.85.218.48 mail-oi0-f48.google.com Received: from [209.85.218.48] ([209.85.218.48:33003] helo=mail-oi0-f48.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 2A/53-61664-91D2CA45 for ; Tue, 06 Jan 2015 13:44:41 -0500 Received: by mail-oi0-f48.google.com with SMTP id u20so53346016oif.7 for ; Tue, 06 Jan 2015 10:44:38 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=vPklV/LZvzUkhcP8babYyD5Fikp//4+ZcHFLs63wzDY=; b=r5I9/GTWRewCLASueY0CTNXRJAtQcGQgbOdWuipYvQ/8FNd5E8dQo+Yl/9J4f1pdwj XFYW6NtHgAFXHlzTfrIsWPwsYVvgPNgiDawb/Q/ZAdf5c7C98E4M9cocnQwxMY4PAj3n cIf8NNBQtiFUv2P0Mjvm0QaTUh6PAqlCz2UDTWcX+W70N7fylQKm66eeTZCbqnaMnE/L G94PDZwILEAlsUFiMdsJN5F/r7emOMpKYAUJI8wjycn7Xpt7Osf9zvlH0n/XDE7Zphwk Uwz7yHI9YHdmRUPihPn/OpepzeS4h41CYwwVUTFR4mq54VWQ/RCliHP1mDAuEro2D6A0 L/BQ== X-Received: by 10.182.28.196 with SMTP id d4mr59134892obh.66.1420569877998; Tue, 06 Jan 2015 10:44:37 -0800 (PST) Received: from [192.168.2.145] (108-66-6-48.lightspeed.sntcca.sbcglobal.net. [108.66.6.48]) by mx.google.com with ESMTPSA id u10sm31280408oeo.14.2015.01.06.10.44.36 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 06 Jan 2015 10:44:37 -0800 (PST) Message-ID: <54AC2D12.7060209@gmail.com> Date: Tue, 06 Jan 2015 10:44:34 -0800 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:31.0) Gecko/20100101 Thunderbird/31.3.0 MIME-Version: 1.0 To: francois@tekwire.net, 'Pierre Joye' , 'Derick Rethans' CC: 'Sara Golemon' , 'Benjamin Eberlei' , 'PHP Internals' References: <54AAF98B.4020709@gmail.com> <001b01d029bb$fa687fc0$ef397f40$@tekwire.net> In-Reply-To: <001b01d029bb$fa687fc0$ef397f40$@tekwire.net> Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit Subject: Re: [PHP-DEV] [RFC] Extension Prepend Files From: smalyshev@gmail.com (Stanislav Malyshev) Hi! > The first reason is that, if we consider a released extension as a > conceptual unit, the best way to protect its integrity is to store it > as a single file. Storing it as separate files brings a lot of > potential issues : files can be renamed, deleted, etc. Offline tools Yet people have been releasing mulfi-file software packages for decades, and it seems to work fine and the software world has yet to collapse under these problems. Which suggests they maybe not as severe as they seem to be. > code. But, if we consider the PHP code as an integral part of the > extension, this should be avoided, as C and PHP code need to be kept > in sync. Again, there is a multitude of solutions for this, all in the realm of packaging. It's not like we've just encountered the idea of software package having more than one file. -- Stas Malyshev smalyshev@gmail.com