1
0
mirror of https://git.FreeBSD.org/ports.git synced 2024-12-23 04:23:08 +00:00

Add p5-Regexp-Common-profanity_us 2.2, provide regexes for U.S.

profanity.

PR:		ports/100070
Submitted by:	Gea-Suan Lin <gslin at gslin.org>
This commit is contained in:
Rong-En Fan 2006-07-11 20:42:43 +00:00
parent beb0aba164
commit 4d5dc1b29b
Notes: svn2git 2021-03-31 03:12:20 +00:00
svn path=/head/; revision=167536
5 changed files with 61 additions and 0 deletions

View File

@ -415,6 +415,7 @@
SUBDIR += p5-RTF-Writer
SUBDIR += p5-Regex-PreSuf
SUBDIR += p5-Regexp-Common
SUBDIR += p5-Regexp-Common-profanity_us
SUBDIR += p5-Regexp-Log
SUBDIR += p5-Regexp-Log-Common
SUBDIR += p5-SGMLSpm

View File

@ -0,0 +1,26 @@
# New ports collection makefile for: p5-Regexp-Common-profanity_us
# Date created: 2006-07-11
# Whom: Gea-Suan Lin <gslin@gslin.org>
#
# $FreeBSD$
#
PORTNAME= Regexp-Common-profanity_us
PORTVERSION= 2.2
CATEGORIES= textproc perl5
MASTER_SITES= ${MASTER_SITE_PERL_CPAN}
MASTER_SITE_SUBDIR= Regexp
PKGNAMEPREFIX= p5-
MAINTAINER= gslin@gslin.org
COMMENT= Provide regexes for U.S. profanity
BUILD_DEPENDS= ${SITE_PERL}/Regexp/Common.pm:${PORTSDIR}/textproc/p5-Regexp-Common
RUN_DEPENDS= ${BUILD_DEPENDS}
PERL_CONFIGURE= yes
MAN3= Regexp::Common::profanity_us.3 \
Regexp::Profanity::US.3
.include <bsd.port.mk>

View File

@ -0,0 +1,3 @@
MD5 (Regexp-Common-profanity_us-2.2.tar.gz) = 863b9847c70d6fd319d3766b9728447d
SHA256 (Regexp-Common-profanity_us-2.2.tar.gz) = bd8069e7e56569809d69008bc8509c812213d87f6730c03c344e3ec6e1a627ee
SIZE (Regexp-Common-profanity_us-2.2.tar.gz) = 5912

View File

@ -0,0 +1,21 @@
Instead of a dry technical overview, I am going to explain the
structure of this module based on its history. I consult at a company
that generates customer leads primarily by having websites that
attract people (e.g. lowering loan values, selling cars, buying real
estate, etc.). For some reason we get more than our fair share of
profane leads. For this reason I was told to write a profanity checker.
For the data that I was dealing with, the profanity was most often in
the email address or in the first or last name, so I naively started
filtering profanity with a set of regexps for that sort of data. Note
that both names and email addresses are unlike what you are reading
now: they are not whitespace-separated text, but are instead labels.
Therefore full support for profanity checking should work in 2
entirely different contexts: labels (email, names) and text (what you
are reading). Because open-source is driven by demand and I have no
need for detecting profanity in text, only label is implemented at the
moment. And you know the next sentence: "patches welcome" :)
Author: T. M. Brannon, tbone@cpan.org
WWW: http://search.cpan.org/dist/Regexp-Common-profanity_us/

View File

@ -0,0 +1,10 @@
@comment $FreeBSD$
%%SITE_PERL%%/%%PERL_ARCH%%/auto/Regexp/Common/profanity_us/.packlist
%%SITE_PERL%%/Regexp/Common/profanity_us.pm
%%SITE_PERL%%/Regexp/Profanity/US.pm
@dirrmtry %%SITE_PERL%%/%%PERL_ARCH%%/auto/Regexp/Common/profanity_us
@dirrmtry %%SITE_PERL%%/%%PERL_ARCH%%/auto/Regexp/Common
@dirrmtry %%SITE_PERL%%/%%PERL_ARCH%%/auto/Regexp
@dirrmtry %%SITE_PERL%%/Regexp/Common
@dirrmtry %%SITE_PERL%%/Regexp/Profanity
@dirrmtry %%SITE_PERL%%/Regexp