Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:37694
Return-Path: <greg@chiaraquartet.net>
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Delivered-To: mailing list internals@lists.php.net
Received: (qmail 91645 invoked from network); 17 May 2008 20:10:06 -0000
Received: from unknown (HELO lists.php.net) (127.0.0.1)
  by localhost with SMTP; 17 May 2008 20:10:06 -0000
Authentication-Results: pb1.pair.com header.from=greg@chiaraquartet.net; sender-id=unknown
Authentication-Results: pb1.pair.com smtp.mail=greg@chiaraquartet.net; spf=permerror; sender-id=unknown
Received-SPF: error (pb1.pair.com: domain chiaraquartet.net from 38.99.98.18 cause and error)
X-PHP-List-Original-Sender: greg@chiaraquartet.net
X-Host-Fingerprint: 38.99.98.18 beast.bluga.net Linux 2.6
Received: from [38.99.98.18] ([38.99.98.18:58119] helo=mail.bluga.net)
	by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP
	id 22/77-33811-C9B3F284 for <internals@lists.php.net>; Sat, 17 May 2008 16:10:05 -0400
Received: from mail.bluga.net (localhost.localdomain [127.0.0.1])
	by mail.bluga.net (Postfix) with ESMTP id 85324C11111
	for <internals@lists.php.net>; Sat, 17 May 2008 13:10:06 -0700 (MST)
Received: from [192.168.0.106] (CPE-76-84-4-101.neb.res.rr.com [76.84.4.101])
	(using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))
	(No client certificate requested)
	by mail.bluga.net (Postfix) with ESMTP id 46568C108E5
	for <internals@lists.php.net>; Sat, 17 May 2008 13:10:06 -0700 (MST)
Message-ID: <482F3BA6.8090408@chiaraquartet.net>
Date: Sat, 17 May 2008 15:10:14 -0500
User-Agent: Thunderbird 2.0.0.14 (X11/20080502)
MIME-Version: 1.0
To: internals Mailing List <internals@lists.php.net>
X-Enigmail-Version: 0.95.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-Virus-Scanned: ClamAV using ClamSMTP
Subject: HEADS UP: phar now enabled statically by default
From: greg@chiaraquartet.net (Gregory Beaver)

Hi,

I've reversed my initial patch enabling phar as shared by default, and
instead now enable it statically by default.

I was able to solve the dependency on zlib/bz2 I noted in my last
message through some very simple logic, and testing confirms that phar
can be built statically with zlib/bz2 shared with absolutely no problems
whatsoever because phar never uses these extensions directly, only
through the stream filter API.

So, in short, problem solved, and phar can be built statically and works
just great with static zlib/bz2 or shared zlib/bz2.

Greg