cpet/openbsd-ports
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

initial import of node-bindings for node-bcrypt fix

Browse Source 
OK jeremy@
This commit is contained in:
abieber 2013-05-21 23:00:18 +00:00
parent e71445259f
commit dd06e27186
4 changed files with 41 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

22
devel/node-bindings/Makefile Normal file
View File

@ -0,0 +1,22 @@
# $OpenBSD: Makefile,v 1.1.1.1 2013/05/21 23:00:18 abieber Exp $
COMMENT = helper module for loading native modules in .node
NPM_VERSION = 1.0.0
NPM_NAME = bindings
CATEGORIES = devel
MAINTAINER = Aaron Bieber <abieber@openbsd.org>
HOMEPAGE = https://github.com/TooTallNate/node-bindings
# MIT
PERMIT_PACKAGE_CDROM = Yes
MODULES = lang/node
CONFIGURE_STYLE = npm
NO_TEST = Yes
.include <bsd.port.mk>

2
devel/node-bindings/distinfo Normal file
View File

@ -0,0 +1,2 @@
SHA256 (bindings-1.0.0.tgz) = yyEayFbRNa9e6GR2L66eVUIlphPqH9gVwguP3RZ5ye0=
SIZE (bindings-1.0.0.tgz) = 3456

12
devel/node-bindings/pkg/DESCR Normal file
View File

@ -0,0 +1,12 @@
This is a helper module for authors of Node.js native addon modules. It
is basically the "swiss army knife" of require()ing your native module's
.node file.
Throughout the course of Node's native addon history, addons have ended
up being compiled in a variety of different places, depending on which
build tool and which version of node was used. To make matters worse,
now the gyp build tool can produce either a Release or Debug build, each
being built into different locations.
This module checks all the possible locations that a native addon would
be built at, and returns the first one that loads successfully.

5
devel/node-bindings/pkg/PLIST Normal file
View File

@ -0,0 +1,5 @@
@comment $OpenBSD: PLIST,v 1.1.1.1 2013/05/21 23:00:18 abieber Exp $
lib/node_modules/bindings/
lib/node_modules/bindings/README.md
lib/node_modules/bindings/bindings.js
lib/node_modules/bindings/package.json