From owner-cvs-all Wed Nov 15 8:10:42 2000 Delivered-To: cvs-all@freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id 216B237B4CF; Wed, 15 Nov 2000 08:10:39 -0800 (PST) Received: (from ade@localhost) by freefall.freebsd.org (8.9.3/8.9.2) id IAA32574; Wed, 15 Nov 2000 08:10:39 -0800 (PST) (envelope-from ade@FreeBSD.org) Message-Id: <200011151610.IAA32574@freefall.freebsd.org> From: Ade Lovett Date: Wed, 15 Nov 2000 08:10:38 -0800 (PST) To: cvs-committers@FreeBSD.org, cvs-all@FreeBSD.org Subject: cvs commit: ports/www/apache13-modssl Makefile pkg-plist ports/www/apache13-modssl/files FreeBSD.layout patch-ai apache.sh patch-aa patch-ac X-FreeBSD-CVS-Branch: HEAD Sender: owner-cvs-all@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG ade 2000/11/15 08:10:38 PST Modified files: www/apache13-modssl Makefile pkg-plist www/apache13-modssl/files apache.sh patch-aa patch-ac Added files: www/apache13-modssl/files FreeBSD.layout patch-ai Log: Gently persuade apache13-modssl to install in the same filesystem space as www/apache13 does, so that other apache-dependendent ports DTRT regardless of which one is installed. Nothing concrete (other than we're working on a real cleanup of the apache ports) has been heard from any of the maintainers. Obviously that is the best solution, but with 4.2-RELEASE just around the corner, we have an opportunity here to at least remove a few bogons. Both times I've raised this issue on -ports, however, there has been significant interest in the patches, and now plenty of confirmations that the modifications do not break the port in other ways. Revision Changes Path 1.76 +13 -24 ports/www/apache13-modssl/Makefile 1.18 +406 -389 ports/www/apache13-modssl/pkg-plist 1.2 +2 -2 ports/www/apache13-modssl/files/apache.sh 1.6 +22 -0 ports/www/apache13-modssl/files/patch-aa 1.4 +46 -0 ports/www/apache13-modssl/files/patch-ac To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe cvs-all" in the body of the message