From owner-freebsd-ports Sat Aug 15 19:45:39 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA19620 for freebsd-ports-outgoing; Sat, 15 Aug 1998 19:45:39 -0700 (PDT) (envelope-from owner-freebsd-ports@FreeBSD.ORG) Received: from hp9000.chc-chimes.com (hp9000.chc-chimes.com [206.67.97.84]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA19615 for ; Sat, 15 Aug 1998 19:45:38 -0700 (PDT) (envelope-from billf@chc-chimes.com) Received: from localhost by hp9000.chc-chimes.com with SMTP (1.39.111.2/16.2) id AA259541676; Sat, 15 Aug 1998 21:41:16 -0400 Date: Sat, 15 Aug 1998 21:41:16 -0400 (EDT) From: Bill Fumerola To: ports@FreeBSD.ORG Subject: php3 and modules for it. Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-ports@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org As I work on a port that requires php3 AND mysql it leads me to an interesting dilemma. I need to compile php3, obviously. My gut feeling says I should make another port for php3 because there are programs other then the one I'm porting that use php3. I need the mysql stuff compiled in to php3 for this port, BUT others may not, or want OTHER modules compiled in (LDAP, SNMP, msql, sybase, etc) so should I make a php3-mysql port and let other make php3-ldap (for example) when they need it? I'd even make ports for all the modules, but that would be 10+ ports. I don't mind the work, but I think that would be a bit much. suggestions? - bill fumerola [root/billf]@chc-chimes.com - computer horizons corp - - ph:(800)252.2421 x128 / bfumerol@computerhorizons.com - BF1560 - "Logic, like whiskey, loses its beneficial effect when taken in too large quantities" -Lord Dunsany To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-ports" in the body of the message