Date: Sun, 16 Aug 1998 12:38:59 -0700 (PDT) From: Marc Slemko <marcs@znep.com> To: Bill Fumerola <billf@chc-chimes.com> Cc: ports@FreeBSD.ORG Subject: Re: php3 and modules for it. Message-ID: <Pine.GSO.4.00.9808161237350.7948-100000@redfish> In-Reply-To: <Pine.HPP.3.96.980815213630.25740A-100000@hp9000.chc-chimes.co m>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sat, 15 Aug 1998, Bill Fumerola wrote: > > 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. Fix the Apache port to use DSO (dynamic loadable modules), then all you need is Apache and Apache-SSL. Every other port can simply create a loadable object and require the base apache or apache-ssl. You can then have two zillion Apache modules that don't have much overhead. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-ports" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.GSO.4.00.9808161237350.7948-100000>