Subject: pkg/17091: Apache FPSE Extension Addition to Makefile
To: None <gnats-bugs@gnats.netbsd.org>
From: None <burgess@neonramp.com>
List: netbsd-bugs
Date: 05/28/2002 17:58:12
>Number:         17091
>Category:       pkg
>Synopsis:       Need a few lines added to the apache Makefile
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    pkg-manager
>State:          open
>Class:          change-request
>Submitter-Id:   net
>Arrival-Date:   Tue May 28 15:59:00 PDT 2002
>Closed-Date:
>Last-Modified:
>Originator:     Dave Burgess
>Release:        N/A
>Organization:
	Nebraska On-Ramp
>Environment:
System: NetBSD nfs3.neonramp.com 1.5 NetBSD 1.5 (NEONRAMP-RADIUS) #0: Sat Feb 3 07:42:20 CST 2001 root@radius1.neonramp.com:/usr/src/sys/arch/i386/compile/NEONRAMP i386


>Description:
I've been using the Microsoft FrontPage extensions extensively for
several years.  I have finally got it down to the point that all
I need is the following added to the base Makefile in the www/apache
directory.  There is also a patchfile that needs to be included,
but it comes straight from the FrontPage Server Extensions (either
FreeBSD or BSDI) server extension file.

Everything else just works.  I could probably package the rest of
this stuff up if that would be preferable.....

Without this change, the FPSE Makefile must be editted by hand,
which is a pain.  Everything else can be handled from the RTR patch.

>How-To-Repeat:
	N/A
>Fix:

--- Makefile.orig       Sat May 25 15:20:45 2002
+++ Makefile    Sat May 25 14:44:32 2002
@@ -46,6 +46,10 @@
 
 .include "../../mk/bsd.prefs.mk"
 
+.if defined(APACHE_FPSE) && ${APACHE_FPSE} == YES
+CONFIGURE_ARGS+=       --add-module=mod_frontpage.c
+.endif
+
 PKG_SYSCONFSUBDIR?=    httpd
 
 .if defined(APACHE_SUEXEC) && ${APACHE_SUEXEC} == YES


There are problems with the patch as it comes from Microsoft (like
it assumes everything is in the /usr/local directory) so I understand
that this isn't a super-clean addition, but a complete package
change could probably be found that would fix this.  As it stands,
the FrontPage patch from RTR installs cleanly without intervention.

This is enough (in the short term) and satisfied the Microsoft
installation documentation.

Since Ready-To-Run changes the patch file every time MS releases a
new FrontPage version (this one supports Apache 1.3.20+ IIRC) the
patch itself isn't a huge problem.  The catch is that one big chunk 
of the thing is an executable that the patched Apache server calls, 
so patching the system to operate where we would normally put it
is going to be unlikely (read: impossible).  As such, we are stuck
installing this in the default location.

Another obvious question would be "How do we add a patchfile on the
fly?"  If the builder doesn't want FPSE, there's no reason to include
the patch from the distribution.

>Release-Note:
>Audit-Trail:
>Unformatted: