Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:46734 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 63703 invoked from network); 14 Jan 2010 19:52:04 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 14 Jan 2010 19:52:04 -0000 Authentication-Results: pb1.pair.com header.from=news@ger.gmane.org; sender-id=pass Authentication-Results: pb1.pair.com smtp.mail=php-php-dev@m.gmane.org; spf=pass; sender-id=pass Received-SPF: pass (pb1.pair.com: domain m.gmane.org designates 80.91.229.12 as permitted sender) X-PHP-List-Original-Sender: php-php-dev@m.gmane.org X-Host-Fingerprint: 80.91.229.12 lo.gmane.org Linux 2.6 Received: from [80.91.229.12] ([80.91.229.12:42277] helo=lo.gmane.org) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 80/D0-56067-1E57F4B4 for ; Thu, 14 Jan 2010 14:52:02 -0500 Received: from list by lo.gmane.org with local (Exim 4.50) id 1NVVjX-0006PS-ML for internals@lists.php.net; Thu, 14 Jan 2010 20:51:55 +0100 Received: from 200.56.172.118 ([200.56.172.118]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Thu, 14 Jan 2010 20:51:55 +0100 Received: from geissert by 200.56.172.118 with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Thu, 14 Jan 2010 20:51:55 +0100 X-Injected-Via-Gmane: http://gmane.org/ To: internals@lists.php.net Followup-To: gmane.comp.php.devel Date: Thu, 14 Jan 2010 13:51:37 -0600 Lines: 55 Message-ID: References: <20100113154657.GA7177@panix.com> <20100113174845.GA11844@panix.com> Mime-Version: 1.0 Content-Type: text/plain; charset="ISO-8859-1" Content-Transfer-Encoding: 7Bit X-Gmane-NNTP-Posting-Host: 200.56.172.118 Sender: news Subject: Re: [PHP-DEV] 5.3 release schedule and other bits From: geissert@debian.org (Raphael Geissert) Daniel Convissor wrote: > Hi Raphael: > >> What patch do you want to know more about? > > None. I am wondering if there is a resource for lay-people interested in > installing PHP via packages so they can know any eccentricities they will > encounter when compared to compiling it themselves. Well, there are multiple packages to make php use the system copies of the libraries and security enhancements, among many other reasons. > > For example, you discussed changing some ini settings and the possibility > of making short tags throw deprecated warnings. So I wouldn't be > surprised if there are other changes in your forks. The change on the ini file is to avoid breaking applications (that incorrectly rely on short_open_tag being On) on upgrade (which is very important). We aren't doing anything really different, the default value in the interpreter is still On. The warning was being proposed to make sure those applications are fixed to avoid having to carry the ini patch too long. > > Such a document could also be used to clarify/direct your discussions > here. The documentation will be included in the patch header. Note that most of them predate the time I joined the maintenance team. >> Patches have not been properly documented, but they are usually >> referenced by an entry on the changelog giving a bit more information. >> >> You can browse the patches applied to every release (and download or view >> them individually) at: >> http://patch-tracker.debian.org/package/php5 > > This is a little nicer than reading the whole diff file, but as you > mentioned, it still isn't documented well. Meaning it doesn't say > whether a patch is Debian specific or just bringing in something done by > the PHP team itself. Only the debian-quirks and php.ini_securitynotes patches are really Debian- specific. The rest should find its way to the upstream code (but some of the patches were not accepted in the past). Cheers, -- Raphael Geissert - Debian Developer www.debian.org - get.debian.net