[nodejs] Re: NPM Downloading Binaries
On Apr 16, 4:58 am, Richard Astbury wrote: > Could the same approach be used to install other native modules? My general issue with this approach is that you either have to bundle compiled bits for every platform and configuration (ballooning the tarball size due to less compression), or you have a custom npm script that executes on install and downloads the appropriate binary files for the current particular platform (this means an internet connection is required wherever you want to install) from some place. -- -- 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 nodejs@googlegroups.com To unsubscribe from this group, send email to nodejs+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/nodejs?hl=en?hl=en --- You received this message because you are subscribed to the Google Groups "nodejs" group. To unsubscribe from this group and stop receiving emails from it, send an email to nodejs+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[nodejs] Re: NPM Downloading Binaries
Wouldn't it be possible to publish a npm package with binaries which is arch-specific ? like if you're installing node-fibers, the compiled sourced for my machine would be published at node-fibers-linux-x86_64 or something like this. if the package doesn't exist for my architecture, then just build it. I realise that this would mean a lot of "unusable out of the box" packages, but it seems that a lot of package managers do things like that. apt ? On Tuesday, 16 April 2013 10:58:25 UTC+2, Richard Astbury wrote: > > I recently installed the 'phantomjs' module, and was surprised to see the > installation script downloaded the phantomjs binary for the appropriate > platform (i.e. it did this on linux and windows). This makes complete > sense, phantom is probably both time consuming and complicated to compile, > but it made the module installation quite slick. > > Could the same approach be used to install other native modules? > > I know the node approach is to compile the source for native modules, but > on Windows this is painful (sometimes very painful). > > Perhaps the missing part of the equation is an automated build system for > native modules, which would provide the built binaries for certain > platforms. If you're on a compatible platform then NPM gets the binary from > there, otherwise you're back to building it on your own. > > Rich. > -- -- 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 nodejs@googlegroups.com To unsubscribe from this group, send email to nodejs+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/nodejs?hl=en?hl=en --- You received this message because you are subscribed to the Google Groups "nodejs" group. To unsubscribe from this group and stop receiving emails from it, send an email to nodejs+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[nodejs] Re: NPM Downloading Binaries
Here's a crazy idea for you. Why not extend NPM to connect to a registry (maybe this is an additional registry, maybe the NPM one) to look for a compiled version of the native module for your OS. Perhaps it only does this if you supply a specific command line argument (hopefully this satisfies @mscdex's point). The bigger problem is: how do you get the compiled modules into the repository? My suggestion is to crowd source this, again using NPM. If you successfully compile a module which doesn't exist in the repository, NPM could then offer to upload it, thus making it available for others to download. No need for an automated build system, no additional demands on the module author, only change required is to NPM. Nate is absolutely right, there are some trust issues here. Perhaps there is a way to sign the module in some way to demonstrate authenticity? Rich. On Wednesday, April 17, 2013 9:09:35 AM UTC+1, Floby wrote: > > Wouldn't it be possible to publish a npm package with binaries which is > arch-specific ? > like if you're installing node-fibers, the compiled sourced for my machine > would be published at node-fibers-linux-x86_64 or something like this. if > the package doesn't exist for my architecture, then just build it. > I realise that this would mean a lot of "unusable out of the box" > packages, but it seems that a lot of package managers do things like that. > apt ? > > On Tuesday, 16 April 2013 10:58:25 UTC+2, Richard Astbury wrote: >> >> I recently installed the 'phantomjs' module, and was surprised to see the >> installation script downloaded the phantomjs binary for the appropriate >> platform (i.e. it did this on linux and windows). This makes complete >> sense, phantom is probably both time consuming and complicated to compile, >> but it made the module installation quite slick. >> >> Could the same approach be used to install other native modules? >> >> I know the node approach is to compile the source for native modules, but >> on Windows this is painful (sometimes very painful). >> >> Perhaps the missing part of the equation is an automated build system for >> native modules, which would provide the built binaries for certain >> platforms. If you're on a compatible platform then NPM gets the binary from >> there, otherwise you're back to building it on your own. >> >> Rich. >> > -- -- 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 nodejs@googlegroups.com To unsubscribe from this group, send email to nodejs+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/nodejs?hl=en?hl=en --- You received this message because you are subscribed to the Google Groups "nodejs" group. To unsubscribe from this group and stop receiving emails from it, send an email to nodejs+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[nodejs] Re: NPM Downloading Binaries
Arch specific registries using multiple registry support is much simpler. npm --registries="ubuntu.x64.prebuilt.local registry.npmjs.org" when requesting against "ubuntu.x64.prebuilt.local" a proxy would prebuild the module if it 404s. end. Can be done as an internal proxy as well. -- -- 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 nodejs@googlegroups.com To unsubscribe from this group, send email to nodejs+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/nodejs?hl=en?hl=en --- You received this message because you are subscribed to the Google Groups "nodejs" group. To unsubscribe from this group and stop receiving emails from it, send an email to nodejs+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: [nodejs] Re: NPM Downloading Binaries
On Wednesday, April 17, 2013 at 9:28 , Richard Astbury wrote:
> Here's a crazy idea for you.
>
> Why not extend NPM to connect to a registry (maybe this is an additional
> registry, maybe the NPM one) to look for a compiled version of the native
> module for your OS. Perhaps it only does this if you supply a specific
> command line argument (hopefully this satisfies @mscdex's point).
If going for the flag option, I think people will probably just ignore and
compile locally. Perhaps this could be asked by npm when fetching a module?
("Module X needs compilation. There's one ready online, do you want to download
it? - Author: ")
>
> The bigger problem is: how do you get the compiled modules into the
> repository?
>
> My suggestion is to crowd source this, again using NPM. If you successfully
> compile a module which doesn't exist in the repository, NPM could then offer
> to upload it, thus making it available for others to download.
+1
>
> No need for an automated build system, no additional demands on the module
> author, only change required is to NPM.
>
> Nate is absolutely right, there are some trust issues here. Perhaps there is
> a way to sign the module in some way to demonstrate authenticity?
This had to be signed by the user and the trust issue is still there. Whether
you know the author and trust him or you don't.
--
--
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 nodejs@googlegroups.com
To unsubscribe from this group, send email to
nodejs+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/nodejs?hl=en?hl=en
---
You received this message because you are subscribed to the Google Groups
"nodejs" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to nodejs+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
