Commit graph

7 commits

Author SHA1 Message Date
seb
c3f1e700ad Bump the PKGREVISION for all packages which depend directly on perl,
to trigger/signal a rebuild for the transition 5.10.1 -> 5.12.1.

The list of packages is computed by finding all packages which end
up having either of PERL5_USE_PACKLIST, BUILDLINK_API_DEPENDS.perl,
or PERL5_PACKLIST defined in their make setup (tested via
"make show-vars VARNAMES=..."), minus the packages updated after
the perl package update.

sno@ was right after all, obache@ kindly asked and he@ led the
way. Thanks!
2010-08-21 16:32:42 +00:00
sno
e9dd764e4a pkgsrc changes:
- Updating package for p5 module Text::Context::EitherSide from 1.3nb1
    to 1.4
  - Setting artistic-2.0 as license

Upstream changes:
1.4   Mon May  4 13:22:08 EEST 2009
    - Relicense as AL2.0
2009-05-21 12:14:26 +00:00
he
b021813da0 Bump the PKGREVISION for all packages which depend directly on perl,
to trigger/signal a rebuild for the transition 5.8.8 -> 5.10.0.

The list of packages is computed by finding all packages which end
up having either of PERL5_USE_PACKLIST, BUILDLINK_API_DEPENDS.perl,
or PERL5_PACKLIST defined in their make setup (tested via
"make show-vars VARNAMES=...").
2008-10-19 19:17:40 +00:00
heinz
545db81a7c Roman Kulik cannot maintain those packages anymore (he told me in
private mail some months ago).
2008-07-20 16:09:34 +00:00
joerg
ba171a91fa Add DESTDIR support. 2008-06-12 02:14:13 +00:00
jlam
56ba4d2690 Remove empty PLISTs from pkgsrc since revision 1.33 of plist/plist.mk
can handle packages having no PLIST files.
2007-10-25 16:54:26 +00:00
minskim
180288a298 Import p5-Text-Context-EitherSide from pkgsrc-wip. Packaged by Roman Kulik.
Suppose you have a large piece of text - typically, say, a web page or
a mail message.  And now suppose you've done some kind of full-text
search on that text for a bunch of keywords, and you want to display
the context in which you found the keywords inside the body of the
text.

A simple-minded way to do that would be just to get the two words
either side of each keyword.  But hey, don't be too simple minded,
because you've got to make sure that the list doesn't overlap.  If you
have

    the quick brown fox jumped over the lazy dog

and you extract two words either side of ``fox'', ``jumped'' and
``dog'', you really don't want to end up with

    quick brown fox jumped over brown fox jumped over the the lazy dog

so you need a small amount of smarts.  This module has a small amount
of smarts.
2006-04-17 15:15:25 +00:00