Commit graph

11 commits

Author SHA1 Message Date
jlam
9c8b5ede43 Point MAINTAINER to pkgsrc-users@NetBSD.org in the case where no
developer is officially maintaining the package.

The rationale for changing this from "tech-pkg" to "pkgsrc-users" is
that it implies that any user can try to maintain the package (by
submitting patches to the mailing list).  Since the folks most likely
to care about the package are the folks that want to use it or are
already using it, this would leverage the energy of users who aren't
developers.
2006-03-04 21:28:51 +00:00
joerg
5911def816 Recursive revision bump / recommended bump for gettext ABI change. 2006-02-05 23:08:03 +00:00
wiz
6301213966 Reset MAINTAINER -- he stopped working on pkgsrc. 2005-07-27 16:21:16 +00:00
rillig
f795c2e475 Removed trailing white-space. 2005-05-23 08:26:03 +00:00
tv
f816d81489 Remove USE_BUILDLINK3 and NO_BUILDLINK; these are no longer used. 2005-04-11 21:44:48 +00:00
agc
4a3d2f7ce2 Add RMD160 digests. 2005-02-23 22:24:08 +00:00
recht
367eed19fe Build Python with thread support by default and turn the existing
python*-pth packages into meta-packages which will install the non-pth
packages. Bump PKGREVISIONs on the non-pth versions to propagate the
thread change, but leave the *-pth versions untouched to not affect
existing installations.
Sync all PYTHON_VERSIONS_AFFECTED lines in package Makefiles.
2005-01-23 20:41:45 +00:00
recht
4150812b27 add python as category
ok'd a while back at pkgsrcCon by agc and wiz
2004-07-22 09:15:59 +00:00
snj
7bdebf2480 Convert to buildlink3. 2004-04-27 03:09:57 +00:00
recht
eed7b27b60 Add USE_BUILDLINK2 so this picks up a proper depend
This should fix hubertf's bulk build.
2003-09-25 15:43:35 +00:00
recht
d06a3bdc67 Initial import of py-TPG 2.1.6
based upon the pkg provided by Michal Pasternak in PR 21982

TPG can very simply write parsers that are usefull for most every day needs
(even if it can't make your coffee). With a very clear and simple syntax,
you can write an attributed grammar that is translated into a recursive
descendant parser. TPG generated code is very closed to the original
grammar. This means that the parser works "like" the grammar. A grammar rule
can be seen as a method of the parser class, symbols as method calls,
attributes as method parameters and semantic values as return values. You
can also add Python code directly into grammar rules and build abstract
syntax trees while parsing.
2003-09-15 22:08:35 +00:00