Date: Thu, 31 Jul 2014 18:54:55 +0000 (UTC) From: Sunpoet Po-Chuan Hsieh <sunpoet@FreeBSD.org> To: ports-committers@freebsd.org, svn-ports-all@freebsd.org, svn-ports-head@freebsd.org Subject: svn commit: r363659 - head/textproc/p5-Regexp-Common-profanity_us Message-ID: <201407311854.s6VIst9d049504@svn.freebsd.org>
next in thread | raw e-mail | index | archive | help
Author: sunpoet Date: Thu Jul 31 18:54:55 2014 New Revision: 363659 URL: http://svnweb.freebsd.org/changeset/ports/363659 QAT: https://qat.redports.org/buildarchive/r363659/ Log: - Sort PLIST - Reformat pkg-descr - Remove Author line - Use single space after WWW: Modified: head/textproc/p5-Regexp-Common-profanity_us/Makefile head/textproc/p5-Regexp-Common-profanity_us/pkg-descr head/textproc/p5-Regexp-Common-profanity_us/pkg-plist Modified: head/textproc/p5-Regexp-Common-profanity_us/Makefile ============================================================================== --- head/textproc/p5-Regexp-Common-profanity_us/Makefile Thu Jul 31 18:54:48 2014 (r363658) +++ head/textproc/p5-Regexp-Common-profanity_us/Makefile Thu Jul 31 18:54:55 2014 (r363659) @@ -16,7 +16,7 @@ LICENSE_COMB= dual BUILD_DEPENDS= p5-Regexp-Common>=0:${PORTSDIR}/textproc/p5-Regexp-Common RUN_DEPENDS:= ${BUILD_DEPENDS} -USES= perl5 USE_PERL5= configure +USES= perl5 .include <bsd.port.mk> Modified: head/textproc/p5-Regexp-Common-profanity_us/pkg-descr ============================================================================== --- head/textproc/p5-Regexp-Common-profanity_us/pkg-descr Thu Jul 31 18:54:48 2014 (r363658) +++ head/textproc/p5-Regexp-Common-profanity_us/pkg-descr Thu Jul 31 18:54:55 2014 (r363659) @@ -1,21 +1,20 @@ -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. +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. +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" :) +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/ +WWW: http://search.cpan.org/dist/Regexp-Common-profanity_us/ Modified: head/textproc/p5-Regexp-Common-profanity_us/pkg-plist ============================================================================== --- head/textproc/p5-Regexp-Common-profanity_us/pkg-plist Thu Jul 31 18:54:48 2014 (r363658) +++ head/textproc/p5-Regexp-Common-profanity_us/pkg-plist Thu Jul 31 18:54:55 2014 (r363659) @@ -1,11 +1,11 @@ -%%PERL5_MAN3%%/Regexp::Common::profanity_us.3.gz -%%PERL5_MAN3%%/Regexp::Profanity::US.3.gz -%%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 +%%SITE_PERL%%/%%PERL_ARCH%%/auto/Regexp/Common/profanity_us/.packlist +%%PERL5_MAN3%%/Regexp::Common::profanity_us.3.gz +%%PERL5_MAN3%%/Regexp::Profanity::US.3.gz +@dirrm %%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/Common @dirrmtry %%SITE_PERL%%/Regexp
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?201407311854.s6VIst9d049504>