aboutsummaryrefslogtreecommitdiff
path: root/textproc/p5-Regexp-Common-profanity_us
diff options
context:
space:
mode:
authorSunpoet Po-Chuan Hsieh <sunpoet@FreeBSD.org>2014-07-31 18:54:55 +0000
committerSunpoet Po-Chuan Hsieh <sunpoet@FreeBSD.org>2014-07-31 18:54:55 +0000
commit0e536fbec75bd531939a1cddd7efb98a6e14809b (patch)
treec54c0732e29bd3910179c77e14eef3f130bf9585 /textproc/p5-Regexp-Common-profanity_us
parent4fb30aa1d5a1e337ceb1d4541709f5d836144ac6 (diff)
downloadports-0e536fbec75bd531939a1cddd7efb98a6e14809b.tar.gz
ports-0e536fbec75bd531939a1cddd7efb98a6e14809b.zip
- Sort PLIST
- Reformat pkg-descr - Remove Author line - Use single space after WWW:
Notes
Notes: svn path=/head/; revision=363659
Diffstat (limited to 'textproc/p5-Regexp-Common-profanity_us')
-rw-r--r--textproc/p5-Regexp-Common-profanity_us/Makefile2
-rw-r--r--textproc/p5-Regexp-Common-profanity_us/pkg-descr35
-rw-r--r--textproc/p5-Regexp-Common-profanity_us/pkg-plist10
3 files changed, 23 insertions, 24 deletions
diff --git a/textproc/p5-Regexp-Common-profanity_us/Makefile b/textproc/p5-Regexp-Common-profanity_us/Makefile
index 76131a16df42..5e4f51360885 100644
--- a/textproc/p5-Regexp-Common-profanity_us/Makefile
+++ b/textproc/p5-Regexp-Common-profanity_us/Makefile
@@ -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>
diff --git a/textproc/p5-Regexp-Common-profanity_us/pkg-descr b/textproc/p5-Regexp-Common-profanity_us/pkg-descr
index de103e5f018b..5d7aa551e322 100644
--- a/textproc/p5-Regexp-Common-profanity_us/pkg-descr
+++ b/textproc/p5-Regexp-Common-profanity_us/pkg-descr
@@ -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/
diff --git a/textproc/p5-Regexp-Common-profanity_us/pkg-plist b/textproc/p5-Regexp-Common-profanity_us/pkg-plist
index 35fd92737009..1f6446761135 100644
--- a/textproc/p5-Regexp-Common-profanity_us/pkg-plist
+++ b/textproc/p5-Regexp-Common-profanity_us/pkg-plist
@@ -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