ports/57662: [new port] www/mod_tidy: Validates the HTML output of your apache2 webserver

Clement Laforet sheepkiller at cultdeadsheep.org
Mon Oct 6 17:50:38 UTC 2003


>Number:         57662
>Category:       ports
>Synopsis:       [new port] www/mod_tidy: Validates the HTML output of your apache2 webserver
>Confidential:   no
>Severity:       non-critical
>Priority:       low
>Responsible:    freebsd-ports-bugs
>State:          open
>Quarter:        
>Keywords:       
>Date-Required:
>Class:          change-request
>Submitter-Id:   current-users
>Arrival-Date:   Mon Oct 06 10:50:23 PDT 2003
>Closed-Date:
>Last-Modified:
>Originator:     Clement Laforet
>Release:        FreeBSD 5.1-CURRENT i386
>Organization:
cotds.org
>Environment:
System: FreeBSD lucifer.cultdeadsheep.org 5.1-CURRENT FreeBSD 5.1-CURRENT #0: Mon Sep 22 08:20:10 CEST 2003 clement at lucifer.cultdeadsheep.org:/usr/obj/usr/src/sys/LUCIFER i386


	
>Description:
	mod_tidy validates the HTML output of your apache2 webserver. So you don't need 
	a separate application to check your HTML.
	It works as a filter that hooks up to HTML output. mod_tidy feeds the HTML 
	output to TidyLib which validates the HTML output. If TidyLib finds 
	an error the client receives a HTML page with a list of all found errors. If 
	TidyLib doesn't complain you will get your HTML data as without mod_tidy.

	WWW: http://home.snafu.de/tusk/mod_tidy/

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

	

--- mod_tidy.shar begins here ---
# This is a shell archive.  Save it in a file, remove anything before
# this line, and then unpack it by entering "sh file".  Note, it may
# create directories; files and directories will be owned by you and
# have default permissions.
#
# This archive contains:
#
#	mod_tidy
#	mod_tidy/pkg-descr
#	mod_tidy/Makefile
#	mod_tidy/pkg-plist
#	mod_tidy/distinfo
#
echo c - mod_tidy
mkdir -p mod_tidy > /dev/null 2>&1
echo x - mod_tidy/pkg-descr
sed 's/^X//' >mod_tidy/pkg-descr << 'END-of-mod_tidy/pkg-descr'
Xmod_tidy validates the HTML output of your apache2 webserver. So you don't need 
Xa separate application to check your HTML.
XIt works as a filter that hooks up to HTML output. mod_tidy feeds the HTML 
Xoutput to TidyLib which validates the HTML output. If TidyLib finds 
Xan error the client receives a HTML page with a list of all found errors. If 
XTidyLib doesn't complain you will get your HTML data as without mod_tidy.
X
XWWW: http://home.snafu.de/tusk/mod_tidy/
END-of-mod_tidy/pkg-descr
echo x - mod_tidy/Makefile
sed 's/^X//' >mod_tidy/Makefile << 'END-of-mod_tidy/Makefile'
X# New ports collection makefile for:	mod_tidy
X# Date created:				Sun Oct  5
X# Whom:					Clement Laforet <sheepkiller at cultdeadsheep.org>
X#
X# $FreeBSD$
X#
X
XPORTNAME=	mod_tidy
XPORTVERSION=	0.3
XCATEGORIES=	www
XMASTER_SITES=	http://home.snafu.de/tusk/mod_tidy/
X
XMAINTAINER=	sheepkiller at cultdeadsheep.org
XCOMMENT=	Validates the HTML output of your apache2 webserver
X
XBUILD_DEPENDS=	${LOCALBASE}/sbin/apxs:${PORTSDIR}/www/apache2
XRUN_DEPENDS=	${BUILD_DEPENDS}
XLIB_DEPENDS=	tidy:${PORTSDIR}/www/tidy-lib
X
XAPXS?=		${LOCALBASE}/sbin/apxs
X
XTIDY_INC=	${LOCALBASE}/include/tidy
XTIDY_LIBS=	${LOCALBASE}/lib
X
Xpost-extract:
X	@${ECHO_MSG} "===>  Removing distributed tidy libs to avoid conflicts"
X	@${RM} -fr ${WRKSRC}/tidy
X
Xdo-build:
X	@(cd ${WRKSRC}/src && ${APXS} -I ${TIDY_INC} -L ${TIDY_LIBS} -c ${PORTNAME}.c) 
X
Xdo-install:
X	@(cd ${WRKSRC}/src && ${APXS} -A -i ${PORTNAME}.la)
X
X.include <bsd.port.mk>
END-of-mod_tidy/Makefile
echo x - mod_tidy/pkg-plist
sed 's/^X//' >mod_tidy/pkg-plist << 'END-of-mod_tidy/pkg-plist'
Xlibexec/apache2/mod_tidy.so
X at exec %D/sbin/apxs -e -A -n tidy %D/%f
X at unexec echo "===>  If you do not plan on reinstalling mod_tidy, you must manually remove"; echo "===>  references to it in httpd.conf."
END-of-mod_tidy/pkg-plist
echo x - mod_tidy/distinfo
sed 's/^X//' >mod_tidy/distinfo << 'END-of-mod_tidy/distinfo'
XMD5 (mod_tidy-0.3.tar.gz) = f4af3e8e1ba21483e0483e114bd66838
END-of-mod_tidy/distinfo
exit
--- mod_tidy.shar ends here ---


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



More information about the freebsd-ports-bugs mailing list