kpriv/pkgsrc
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity
pkgsrc/devel/mph/Makefile

22 lines
536 B
Makefile
Raw Normal View History

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 22:28:51 +01:00
# $NetBSD: Makefile,v 1.4 2006/03/04 21:29:18 jlam Exp $
Initial import of mph-1.2 into the NetBSD Packages Collection. The program mph tries to generate an order preserving minimal perfect hashing (MPH) function for the set of keys, one per line, on stdin. Each key can be at most 4095 characters long (see keys.h to increase this limit), and the keys must be unique. If mph terminates, it emits a language independent binary or text representation of the MPH function on stdout. To generate a usable hash function, this output should be fed to a language dependent filter, like emitc. e.g. % mph <foo | emitc >hash.c The algorithm used by mph is probabilistic - it iterates until it finds a MPH function. For each failed iteration, it prints a (cryptic) reason on stderr. There is no no guarantee that mph will terminate. In practice this is unlikely, unless the constants specified with options -c or -m are too small (see below).
2003-12-04 09:44:58 +01:00
#
DISTNAME= mph-1.2
CATEGORIES= devel
MASTER_SITES= http://www.ibiblio.org/pub/Linux/devel/lang/c/
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 22:28:51 +01:00
MAINTAINER= pkgsrc-users@NetBSD.org
Initial import of mph-1.2 into the NetBSD Packages Collection. The program mph tries to generate an order preserving minimal perfect hashing (MPH) function for the set of keys, one per line, on stdin. Each key can be at most 4095 characters long (see keys.h to increase this limit), and the keys must be unique. If mph terminates, it emits a language independent binary or text representation of the MPH function on stdout. To generate a usable hash function, this output should be fed to a language dependent filter, like emitc. e.g. % mph <foo | emitc >hash.c The algorithm used by mph is probabilistic - it iterates until it finds a MPH function. For each failed iteration, it prints a (cryptic) reason on stderr. There is no no guarantee that mph will terminate. In practice this is unlikely, unless the constants specified with options -c or -m are too small (see below).
2003-12-04 09:44:58 +01:00
#HOMEPAGE= none
COMMENT= Minimal perfect hashing functionality
Create directories before installing files into them.
2005-06-16 08:57:37 +02:00
INSTALLATION_DIRS= bin share/doc
Initial import of mph-1.2 into the NetBSD Packages Collection. The program mph tries to generate an order preserving minimal perfect hashing (MPH) function for the set of keys, one per line, on stdin. Each key can be at most 4095 characters long (see keys.h to increase this limit), and the keys must be unique. If mph terminates, it emits a language independent binary or text representation of the MPH function on stdout. To generate a usable hash function, this output should be fed to a language dependent filter, like emitc. e.g. % mph <foo | emitc >hash.c The algorithm used by mph is probabilistic - it iterates until it finds a MPH function. For each failed iteration, it prints a (cryptic) reason on stderr. There is no no guarantee that mph will terminate. In practice this is unlikely, unless the constants specified with options -c or -m are too small (see below).
2003-12-04 09:44:58 +01:00
do-install:
for i in emitc mph mphm; do \
${INSTALL_PROGRAM} ${WRKSRC}/$$i ${PREFIX}/bin; \
done
${INSTALL_SCRIPT} ${WRKSRC}/mphminm ${PREFIX}/bin
${INSTALL_DATA} ${WRKSRC}/mph.doc ${PREFIX}/share/doc
.include "../../mk/bsd.pkg.mk"
Reference in a new issue Copy permalink