I'd be fine if people distributed binaries as long as they're not huge. Npm doesn't try to build anything by default. The only real trick is having some way to tell npm which bin to use when doing install -g. It may be something Isaac is willing to help out with. I would ping him on this thread.
:Marco On Friday, May 4, 2012 3:58:39 PM UTC-7, Marcel wrote: > > Title says it all. > > It seems that modules with a compile stage can sometimes be difficult for > users to get installed. Ubuntu users may not have their node headers > installed, Windows users may not have any compiler at all, Linux users may > have broken build environments, there's just lots of issues that come up > and often require manual intervention. > > @japj right now is doing some awesome work getting fibers working on > Windows (as far as I can tell it's pretty much done) and it's got me > thinking about distribution for Windows users. It would be simple enough to > build a version of each tag for Windows 32/64 & Linux 32/64/arm & OS X > 32/64. Of course source would also be distributed so you could build it on > your own if you're feeling adventurous or if you're on a different platform. > > But is someone going to beat me up if I stick a bunch of compiled binaries > into npm? > -- 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
