From owner-freebsd-ports@FreeBSD.ORG Wed Nov 8 20:02:36 2006 Return-Path: X-Original-To: ports@freebsd.org Delivered-To: freebsd-ports@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5F03C16A412 for ; Wed, 8 Nov 2006 20:02:36 +0000 (UTC) (envelope-from wmoran@collaborativefusion.com) Received: from mx00.pub.collaborativefusion.com (mx00.pub.collaborativefusion.com [206.210.89.199]) by mx1.FreeBSD.org (Postfix) with ESMTP id C506143D53 for ; Wed, 8 Nov 2006 20:02:35 +0000 (GMT) (envelope-from wmoran@collaborativefusion.com) Received: from collaborativefusion.com (mx01.pub.collaborativefusion.com [206.210.89.201]) (TLS: TLSv1/SSLv3,256bits,AES256-SHA) by wingspan with esmtp; Wed, 08 Nov 2006 15:02:35 -0500 id 00056415.455237DB.000120CD Received: from Internal Mail-Server by mx01 (envelope-from wmoran@collaborativefusion.com) with AES256-SHA encrypted SMTP; 8 Nov 2006 15:02:12 -0500 Date: Wed, 8 Nov 2006 15:02:34 -0500 From: Bill Moran To: Jeremy Chadwick Message-Id: <20061108150234.8fcfe052.wmoran@collaborativefusion.com> In-Reply-To: <20061108150853.GA39844@icarus.home.lan> References: <20061108092446.32d21eb8.wmoran@collaborativefusion.com> <20061108150853.GA39844@icarus.home.lan> Organization: Collaborative Fusion X-Mailer: Sylpheed version 2.2.9 (GTK+ 2.10.6; i386-portbld-freebsd6.1) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Cc: ports@freebsd.org Subject: Re: Could use some help fixing the pecl-crack port (broken since php 5.2?) X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 08 Nov 2006 20:02:36 -0000 In response to Jeremy Chadwick : > On Wed, Nov 08, 2006 at 09:24:46AM -0500, Bill Moran wrote: > > Now, crack.so is in /usr/local/lib/php/20060613/crack.so, so it would > > appear as if my pkg-plist needs updated. No worries ... > > > > except I'm a little unclear on the build magic behind PHP. I'm guessing > > that 20060613 is some sort of API date? If so, is it Ok to be hard- > > coding this in to the pkg-plist? It seems as if this is handled by > > bsd.php.mk: > > > > .if ${PHP_VER} == 4 > > PHP_EXT_DIR= 20020429 > > .else > > PHP_EXT_DIR= 20060613 > > .endif > > > > Which means hardcoding the path into the pkg-plist will break the port for > > PHP 4. Despite the fact that I don't think many folks are using PHP 4, > > I'd rather not do this. > > Looking at ports/Mk/bsd.php.mk, label `add-plist-phpext`, it appears the > PHP port framework already adds the appropriate .so to the packing list > for you. You can verify this by removing it from your pkg-plist, doing a > make install, then looking at /var/db/pkg/whatever/+CONTENTS Thanks, Jeremy ... that explains it for me. -- Bill Moran Collaborative Fusion Inc. IMPORTANT: This message contains confidential information and is intended only for the individual named. If the reader of this message is not an intended recipient (or the individual responsible for the delivery of this message to an intended recipient), please be advised that any re-use, dissemination, distribution or copying of this message is prohibited. Please notify the sender immediately by e-mail if you have received this e-mail by mistake and delete this e-mail from your system.