Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:51739 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 69389 invoked from network); 22 Mar 2011 08:11:09 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 22 Mar 2011 08:11:09 -0000 Authentication-Results: pb1.pair.com smtp.mail=seanius@seanius.net; spf=permerror; sender-id=unknown Authentication-Results: pb1.pair.com header.from=seanius@seanius.net; 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:41764] helo=cobija.connexer.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 8C/71-54529-799588D4 for ; Tue, 22 Mar 2011 03:11:08 -0500 Received: by cobija.connexer.com (Postfix, from userid 1000) id 1BCB830009; Tue, 22 Mar 2011 04:10:58 -0400 (EDT) Date: Tue, 22 Mar 2011 09:10:58 +0100 To: Raphael Geissert Cc: internals@lists.php.net Message-ID: <20110322081058.GA6959@cobija.connexer.com> References: <92.00.54529.D5E288D4@pb1.pair.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <92.00.54529.D5E288D4@pb1.pair.com> User-Agent: Mutt/1.5.18 (2008-05-17) Subject: Re: [PHP-DEV] embedded libmagic (from file) From: seanius@seanius.net (sean finney) On Mon, Mar 21, 2011 at 11:06:28PM -0600, Raphael Geissert wrote: > It's easy to understand the wish of hacking libmagic to provide some more > features, but it would be great to keep the divergence to the strict > minimum. And ideally we could find some kind of technical solution/compromise that would keep all parties satisfied. I know this is a touchy subject, but embedded code copies are a pretty big issue for us and not allowing them plays a part in what keeps the QA in Debian so well respected. I haven't looked very closely at this particular problem, but as a last resort (assuming we can't find something one-size-fits-all), we can always add support in the debian source package, so that users who want any missing functionality can easily get it by recompiling with some arbitrary option (like what we're already doing with PHP5_COMPAT for keeping ABI compatibility). sean