From owner-freebsd-ports Sun Oct 4 03:42:27 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id DAA16596 for freebsd-ports-outgoing; Sun, 4 Oct 1998 03:42:27 -0700 (PDT) (envelope-from owner-freebsd-ports@FreeBSD.ORG) Received: from slarti.muc.de (slarti.muc.de [193.174.4.10]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id DAA16478 for ; Sun, 4 Oct 1998 03:41:40 -0700 (PDT) (envelope-from rse@engelschall.com) Received: (qmail 29384 invoked by uid 66); 4 Oct 1998 10:40:55 -0000 Received: by en1.engelschall.com (Sendmail 8.9.1) for ports@freebsd.org id MAA21506; Sun, 4 Oct 1998 12:40:17 +0200 (CEST) Message-ID: <19981004121422.A19533@engelschall.com> Date: Sun, 4 Oct 1998 12:14:22 +0200 From: "Ralf S. Engelschall" To: cvs-comitters@FreeBSD.ORG Subject: Re: cvs commit: ports/www/apache13-php3 Makefile ports/www/apache13-php3/files md5 configure.patch ports/www/apache13-php3/patches patch-aa patch-ab patch-am patch-an ports/www/apache13-php3/patches.modssl patch-aa patch-ab patch- Reply-To: rse@engelschall.com Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i Organization: Engelschall, Germany. X-Web-Homepage: http://www.engelschall.com/ X-PGP-Public-Key: http://www.engelschall.com/ho/rse/pgprse.asc X-PGP-Fingerprint: 00 C9 21 8E D1 AB 70 37 DD 67 A2 3A 0A 6F 8D A5 Status: RO Lines: 48 Sender: owner-freebsd-ports@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org In article <19981002065920.B1941@klemm.gtn.com> you wrote: > Well, that might be possible. But the crux is, that we don't > want only to build pure apache modssl, php3, xxxx ports, but > also mixtures of that. Correct. And as Marc already explained: Some modules like mod_ssl cannot be build as DSOs because the Apache API contains no crypto hooks which allows this. > In an ideal world we would have one port maintainer for the > apache port and perhaps one port that handles all of this. Yes, of course. > But Ralf Engelschall for example wants to keep his version > of apache-modssl port as a pure modssl port and wants to > maintain it him self, so we are kind of split here. Please don't understand me correctly here. I don't want to maintain a apache13-modssl port myself because of my ego, of course. The reasons are different: 1. The whole SSL stuff is complicated enough. When you bundle it with PHP3 and other things it gets even more complicated. This leads to a lot of bug reports to me which aren't actually related to mod_ssl. It costs me already a lot of time to support mod_ssl without PHP3 or mod_perl or whatever else related problems. So I appreciate to have a stand-alone Apache+mod_ssl port here. 2. The mod_ssl stuff is restricted because it contains Cryptography. So, the apache13-modssl port is marked as RESTRICTED. This means packages of it are not included on CDROMs and FTP servers. When you now bundle it to the other Apache ports it encumbers these, too. So, another good point why I want a stand-alone Apache+mod_ssl port. > I think the first step would be, to agree / rely on one > apache port maintainer and to give him the chance to > put it all in one port, or maybe two or three, if people want > to have precompiled packages of apache-php3 and apache-modssl. Yes, sounds reasonable. But please keep the above two points in mind. Greetings, Ralf S. Engelschall rse@engelschall.com www.engelschall.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-ports" in the body of the message