Haha, no offense but it sounds like this isn't the best use case for
distributing through npm :) I don't think people want to download a huge
binary and certainly not multiple. I would suggest you provide links to
downloadable binaries separately. The trouble is it's not just multiple
platforms, but multiple node versions that you may want to support. I'm
assuming your binary is a node extension. Is that true? If not there's
another option. You could distribute your module without the binary and
tell people to grab the binary themselves in whatever way they feel is best.
:Marco
On Saturday, May 5, 2012 1:58:14 PM UTC-7, Brandon Benvie wrote:
>
> Because the module has Chromium Embedded Frame as a dependency. It takes
> like an hour to compile on my pretty fast computer, and the Windows
> binaries are like 40mb. I think the linux binaries are 300mb.
>
> On Saturday, May 5, 2012 12:51:48 PM UTC-4, Marcel wrote:
>>
>> Why do that? Then you're just adding another point of failure.
>>
>> On Sat, May 5, 2012 at 4:41 AM, Morteza Milani wrote:
>>
>>> Create tarballs for each platform that contains all binaries you need.
>>> serve them somewhere.
>>>
>>> Create a downloader script that downloads tarballs based on users'
>>> platform.
>>>
>>> Then in your package.json:
>>>
>>> "scripts": {
>>> "preinstall": "./bin/downloader || true; node-gyp rebuild"
>>> }
>>>
>>> This is what I do here: https://github.com/milani/appjs/tree/master/bin
>>>
>>>
--
Job Board: http://jobs.nodejs.org/
Posting guidelines:
https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines
You received this message because you are subscribed to the Google
Groups "nodejs" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/nodejs?hl=en?hl=en
