From owner-freebsd-ports Sat Jan 8 12: 7:52 2000 Delivered-To: freebsd-ports@freebsd.org Received: from blackbird.lonetree.com (blackbird.lonetree.com [207.141.55.3]) by hub.freebsd.org (Postfix) with ESMTP id F141D15257; Sat, 8 Jan 2000 12:07:38 -0800 (PST) (envelope-from wolfman@csocs.com) Received: from csocs.com [209.64.46.23] by blackbird.lonetree.com with ESMTP (SMTPD32-6.00) id A8C7D16D00C0; Sat, 08 Jan 2000 13:06:31 -0700 Message-ID: <387799F8.3182DD68@csocs.com> Date: Sat, 08 Jan 2000 13:11:36 -0700 From: "J.C. Frazier" X-Mailer: Mozilla 4.7 [en] (X11; I; FreeBSD 3.4-STABLE i386) X-Accept-Language: en MIME-Version: 1.0 To: Dirk Froemberg Cc: Vincent Poy , "Scot W. Hetzel" , Patrick Bihan-Faou , freebsd-ports@FreeBSD.ORG, ache@FreeBSD.ORG, rse@engelschall.com, adam@algroup.co.uk Subject: Re: ports/15873: New Apache_fp+php+mod_ssl-1.3.9+3.0.12+2.4.8 port. References: <015d01bf57ef$34afcd00$8dfee0d1@westbend.net> <20000108150504.B76402@physik.TU-Berlin.DE> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-ports@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Dirk Froemberg wrote: > I asked about such integration about a year ago. The maintainer of > apache13-modssl stated that he'd like to keep a seperate port for > modssl. IIRC the maintainer of apache13 wanted to stay independent, > too. This has to be respected of course. > > So I think the major problem is not how to implement certain things, > but to come to a conclusion all (maintainers) can live with. > > Perhaps things have changed since then and we can discuss this issue > again. So I propose to do the following: > > - merge fp extensions into apache13-php3 > - make the php3 part of apache13-php3 optional (apache13-php3 should > be renamed to something reasonable then) > - remove apache13, apache13-fp, apache13-modssl, apache13-php3 and > apache13-ssl > > Alternatively we can integrate fp extensions into apache13-php3 and > leave everthing else as it is. But I think this wouldn't help very > much because it would be still confusing to have too many apache13-* > ports. > > So what do you think? > > [Cc'ed to apache13* maintainers] > > -- > Dirk Froemberg > > FreeBSD: The Power to Serve! http://www.FreeBSD.org/ I have talked to Dirk and agree with him that we need to organize and consolidate the apache* ports. I would be willing to work on it, with the permission from the other maintainers of course. I believe that 2 apache ports should be made as follows: - apache13-nonexport -apache13-export I could fairly easily integrate a configure script which would allow a user to have the choice of what they wanted to use, including but not limited to, mod_ssl, mod_perl, mod_dav, mod_frontpage, php3, php4, imap, xml, dbase, GD, FreeType, mcrypt, mhash, MySQL, mSQL, pdflib, OpenLDAP, zlib, PostgreSQL, and snmp. I think that these 2 ports would allow everyone to have what they want and/or need yet standardizing the apache ports and making everything a lot simpler. None of the current ports other then the one I submitted (PR ports/15873) have anything close to what I personally need. I believe that if we want to give the users the best choice and let them decide, then we either need to work together and build these 2 ports or some of the maintainers need to step down and let Dirk, Scot, or I go to work. Another option is to let a couple of the maintainers work on one and a couple others work on the other. Any feedback? J.C. Frazier To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-ports" in the body of the message