Date: Fri, 20 Aug 2004 09:01:00 -0500 From: Scot Hetzel <swhetzel@gmail.com> To: "linimon@freebsd.org" <linimon@freebsd.org> Cc: ports@freebsd.org Subject: Re: FreeBSD ports which are currently scheduled for deletion Message-ID: <790a9fff040820070137a1e8da@mail.gmail.com> In-Reply-To: <200408200558.i7K5w5hH097377@quark.rcs.purdue.edu> References: <200408200558.i7K5w5hH097377@quark.rcs.purdue.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, 20 Aug 2004 00:58:05 -0500 (EST), linimon@freebsd.org <linimon@freebsd.org> wrote: > portname: www/apache13-fp > description: The Apache webserver with MS Frontpage Module > maintainer: apache@FreeBSD.org > status: FORBIDDEN > deprecated because: multiple vulnerabilities: > http://www.apacheweek.com/features/security-13 > expiration date: 2004-08-20 > build errors: none. > overview: http://portsmon.firepipe.net/portoverview.py?category=www&portname=apache13-fp > This port should be replaced with the new port for the mod_frontpage modules contained in PR 48217: http://www.freebsd.org/cgi/query-pr.cgi?pr=ports/48217 Unfortunately, I haven't had time to update it. The main problem with the port is if you have apache13 installed and then try to install the mod_frontpage2(apache2 only) port, you'll get compile errors. Same with apache2 installed and installing mod_frontpage13 (apache13 only) port. Conflict checking for the apache* ports doesn't prevent the port from trying to build. We have attempted to solve the problem by making the ports depend on apache* header files. If someone could have a look at this PR, and fix any of the remaining problem. This would then allow the www/apache13-fp port to be retired. Thanks, Scot
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?790a9fff040820070137a1e8da>