> How does prebuild differ from node-pre-gyp? prebuild lets you upload to GitHub for releases whereas node-pre-gyp expects you to push releases to S3. It appears that the builds from prebuild are compatible with node-pre-gyp ( https://github.com/mafintosh/prebuild#building). I'm still learning about how to work with native node packages, I'm no expert here.
> How do you make an "official" package so that npm knows where to find it? Once you have an npm account and have run `npm login`, from a base package (where you've defined a package.json), you can run `npm publish` and it will push it to the registry. That's a little light on details, this article is a better intro: https://docs.npmjs.com/getting-started/publishing-npm-packages Thus far I've only published dummies with zmq-prebuilt. On Thu, Feb 4, 2016 at 2:59 AM, Pieter Hintjens <[email protected]> wrote: > I've two questions: > > - How does prebuild differ from node-pre-gyp? > > - How do you make an "official" package so that npm knows where to find it? > > I'd probably aim at making this the official zmq package eventually, > and bring it into the zeromq organization. > > On Thu, Feb 4, 2016 at 8:12 AM, Kyle Kelley <[email protected]> wrote: > > Ok, cool. Thanks for letting me know. > > > > In order to use this with prebuild ( > https://github.com/mafintosh/prebuild), > > I opted to do a GitHub fork of zmq.node here: > > > > https://github.com/nteract/zmq-prebuilt > > > > I've got initial builds working on Windows and Linux while rather amused > > that I haven't been able to get OS X building (since that's what my dev > box > > is) > > > > > > On Wed, Feb 3, 2016 at 11:55 PM, Pieter Hintjens <[email protected]> wrote: > >> > >> The process is to start the project outside the ZeroMQ org and then > >> bring it in as a kind of sacrificial offering, which gets you admin > >> karma. This also avoids rashes of new projects that don't go anywhere. > >> > >> On Thu, Feb 4, 2016 at 5:01 AM, Kyle Kelley <[email protected]> wrote: > >> > Hey all, > >> > > >> > I'm interested in creating prebuilt versions of zmq for node > available. > >> > I > >> > know that Pieter has started the more long term approach to supporting > >> > node.js well with support in zproject: > >> > > >> > https://github.com/zeromq/zproject/pull/484 > >> > > >> > as well as in czmq: > >> > > >> > https://github.com/zeromq/czmq/pull/1319 > >> > > >> > In the meantime, I'd like to plug away on some of the prebuilt setup > for > >> > the > >> > current node bindings (https://github.com/JustinTulloss/zeromq.node), > as > >> > a > >> > standalone project (called e.g. node-zmq-prebuilt, zmq-prebuilt on > npm). > >> > This would mostly be dotting i's and crossing t's on appveyor + Travis > >> > configuration, as well as finishing off what I worked on in > >> > https://github.com/JustinTulloss/zeromq.node/pull/486 > >> > > >> > Would this be a good project to startup within zeromq, or should I > build > >> > it > >> > out on a different org for now? > >> > > >> > -- > >> > Kyle Kelley (@rgbkrk; lambdaops.com) > >> > > >> > _______________________________________________ > >> > zeromq-dev mailing list > >> > [email protected] > >> > http://lists.zeromq.org/mailman/listinfo/zeromq-dev > >> > > >> _______________________________________________ > >> zeromq-dev mailing list > >> [email protected] > >> http://lists.zeromq.org/mailman/listinfo/zeromq-dev > > > > > > > > > > -- > > Kyle Kelley (@rgbkrk; lambdaops.com) > > > > _______________________________________________ > > zeromq-dev mailing list > > [email protected] > > http://lists.zeromq.org/mailman/listinfo/zeromq-dev > > > _______________________________________________ > zeromq-dev mailing list > [email protected] > http://lists.zeromq.org/mailman/listinfo/zeromq-dev > -- Kyle Kelley (@rgbkrk <https://twitter.com/rgbkrk>; lambdaops.com)
_______________________________________________ zeromq-dev mailing list [email protected] http://lists.zeromq.org/mailman/listinfo/zeromq-dev
