Date: Tue, 11 Jul 2006 16:21:59 +0800 (CST) From: Gea-Suan Lin <gslin@gslin.org> To: FreeBSD-gnats-submit@FreeBSD.org Cc: gslin@gslin.org Subject: ports/100070: [NEW PORT] textproc/p5-Regexp-Common-profanity_us: Provide regexes for U.S. profanity Message-ID: <20060711082159.0F113634@netnews.NCTU.edu.tw> Resent-Message-ID: <200607110830.k6B8UI2t049070@freefall.freebsd.org>
next in thread | raw e-mail | index | archive | help
>Number: 100070 >Category: ports >Synopsis: [NEW PORT] textproc/p5-Regexp-Common-profanity_us: Provide regexes for U.S. profanity >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: Tue Jul 11 08:30:17 GMT 2006 >Closed-Date: >Last-Modified: >Originator: Gea-Suan Lin >Release: FreeBSD 6.1-RELEASE i386 >Organization: >Environment: System: FreeBSD netnews.NCTU.edu.tw 6.1-RELEASE FreeBSD 6.1-RELEASE #0: Sat May 13 03:43:48 CST 2006 >Description: 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/ Generated with FreeBSD Port Tools 0.77 >How-To-Repeat: >Fix: --- p5-Regexp-Common-profanity_us-2.2.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: # # p5-Regexp-Common-profanity_us # p5-Regexp-Common-profanity_us/pkg-descr # p5-Regexp-Common-profanity_us/Makefile # p5-Regexp-Common-profanity_us/pkg-plist # p5-Regexp-Common-profanity_us/distinfo # echo c - p5-Regexp-Common-profanity_us mkdir -p p5-Regexp-Common-profanity_us > /dev/null 2>&1 echo x - p5-Regexp-Common-profanity_us/pkg-descr sed 's/^X//' >p5-Regexp-Common-profanity_us/pkg-descr << 'END-of-p5-Regexp-Common-profanity_us/pkg-descr' XInstead of a dry technical overview, I am going to explain the Xstructure of this module based on its history. I consult at a company Xthat generates customer leads primarily by having websites that Xattract people (e.g. lowering loan values, selling cars, buying real Xestate, etc.). For some reason we get more than our fair share of Xprofane leads. For this reason I was told to write a profanity checker. X XFor the data that I was dealing with, the profanity was most often in Xthe email address or in the first or last name, so I naively started Xfiltering profanity with a set of regexps for that sort of data. Note Xthat both names and email addresses are unlike what you are reading Xnow: they are not whitespace-separated text, but are instead labels. X XTherefore full support for profanity checking should work in 2 Xentirely different contexts: labels (email, names) and text (what you Xare reading). Because open-source is driven by demand and I have no Xneed for detecting profanity in text, only label is implemented at the Xmoment. And you know the next sentence: "patches welcome" :) X XAuthor: T. M. Brannon, tbone@cpan.org XWWW: http://search.cpan.org/dist/Regexp-Common-profanity_us/ END-of-p5-Regexp-Common-profanity_us/pkg-descr echo x - p5-Regexp-Common-profanity_us/Makefile sed 's/^X//' >p5-Regexp-Common-profanity_us/Makefile << 'END-of-p5-Regexp-Common-profanity_us/Makefile' X# New ports collection makefile for: p5-Regexp-Common-profanity_us X# Date created: 2006-07-11 X# Whom: Gea-Suan Lin <gslin@gslin.org> X# X# $FreeBSD$ X# X XPORTNAME= Regexp-Common-profanity_us XPORTVERSION= 2.2 XCATEGORIES= textproc perl5 XMASTER_SITES= ${MASTER_SITE_PERL_CPAN} XMASTER_SITE_SUBDIR= Regexp XPKGNAMEPREFIX= p5- X XMAINTAINER= gslin@gslin.org XCOMMENT= Provide regexes for U.S. profanity X XBUILD_DEPENDS= ${SITE_PERL}/Regexp/Common.pm:${PORTSDIR}/textproc/p5-Regexp-Common XRUN_DEPENDS= ${BUILD_DEPENDS} X XPERL_CONFIGURE= yes X X.include <bsd.port.mk> END-of-p5-Regexp-Common-profanity_us/Makefile echo x - p5-Regexp-Common-profanity_us/pkg-plist sed 's/^X//' >p5-Regexp-Common-profanity_us/pkg-plist << 'END-of-p5-Regexp-Common-profanity_us/pkg-plist' X@comment $FreeBSD$ X%%SITE_PERL%%/%%PERL_ARCH%%/auto/Regexp/Common/profanity_us/.packlist X%%SITE_PERL%%/Regexp/Common/profanity_us.pm X%%SITE_PERL%%/Regexp/Profanity/US.pm X@dirrmtry %%SITE_PERL%%/%%PERL_ARCH%%/auto/Regexp/Common/profanity_us X@dirrmtry %%SITE_PERL%%/%%PERL_ARCH%%/auto/Regexp/Common X@dirrmtry %%SITE_PERL%%/%%PERL_ARCH%%/auto/Regexp X@dirrmtry %%SITE_PERL%%/Regexp/Common X@dirrmtry %%SITE_PERL%%/Regexp/Profanity X@dirrmtry %%SITE_PERL%%/Regexp END-of-p5-Regexp-Common-profanity_us/pkg-plist echo x - p5-Regexp-Common-profanity_us/distinfo sed 's/^X//' >p5-Regexp-Common-profanity_us/distinfo << 'END-of-p5-Regexp-Common-profanity_us/distinfo' XMD5 (Regexp-Common-profanity_us-2.2.tar.gz) = 863b9847c70d6fd319d3766b9728447d XSHA256 (Regexp-Common-profanity_us-2.2.tar.gz) = bd8069e7e56569809d69008bc8509c812213d87f6730c03c344e3ec6e1a627ee XSIZE (Regexp-Common-profanity_us-2.2.tar.gz) = 5912 END-of-p5-Regexp-Common-profanity_us/distinfo exit --- p5-Regexp-Common-profanity_us-2.2.shar ends here --- >Release-Note: >Audit-Trail: >Unformatted:
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20060711082159.0F113634>