mirror/freebsd-ports
1
0
Fork 0
mirror of https://git.FreeBSD.org/ports.git synced 2024-11-21 00:25:50 +00:00
Code Issues Releases Activity

- Sort PLIST

Browse Source 
- Reformat pkg-descr
- Remove Author line
- Use single space after WWW:
This commit is contained in:
Sunpoet Po-Chuan Hsieh 2014-07-31 18:54:55 +00:00
parent 4fb30aa1d5
commit 0e536fbec7
Notes: svn2git 2021-03-31 03:12:20 +00:00 
svn path=/head/; revision=363659
3 changed files with 23 additions and 24 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
textproc/p5-Regexp-Common-profanity_us/Makefile
View File

@ -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>

35
textproc/p5-Regexp-Common-profanity_us/pkg-descr
View File

@ -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/

10
textproc/p5-Regexp-Common-profanity_us/pkg-plist
View File

@ -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