From: "Jörg Krause" <jkrause@posteo.de>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] package/iojs: new package
Date: Tue, 20 Jan 2015 18:45:38 +0100 [thread overview]
Message-ID: <1421775938.28321.10.camel@posteo.de> (raw)
In-Reply-To: <20150118162959.GQ4275@free.fr>
Hi Yann,
On So, 2015-01-18 at 17:29 +0100, Yann E. MORIN wrote:
> J?rg, All,
>
> On 2015-01-15 20:58 +0100, J?rg Krause spake thusly:
> > On Do, 2015-01-15 at 09:34 +0100, Thomas Petazzoni wrote:
> > > On Thu, 15 Jan 2015 00:38:16 +0100, J?rg Krause wrote:
> > > > io.js is a fork of Node.js. This package is mainly based on the nodejs
> > > > package, except for the patches.
> > > >
> > > > io.js is currently marked as unstable and there is no stable release for now.
> > > >
> > > > Signed-off-by: J?rg Krause <jkrause@posteo.de>
> > >
> > > Immediate question that comes to mind: is the code base diverging from
> > > Node.js ?
> >
> > Yes, it is.
> >
> > > Do we need two separate packages ?
> >
> > I would say yes. io.js is build against modern versions of V8 and libuv
> > and bundles a recent npm package. This enables the user the new features
> > from the upcoming JavaScript ECMA-262 specification (ES6).
> >
> > From io.js ChangeLog:
> > "The io.js codebase inherits the majority of the changes found in the
> > v0.11 branch of the joyent/node repository and therefore can be seen as
> > an extension to v0.11."
>
> OK, so in the long run, will we need to have a virtual package for the
> NodeJS feature?
>
> That is, are there packages that would work with either NodeJS or iojs?
>
> We need not add such a virtual package for now, but will need to when/if
> we package in Buildroot new packages that can use either one.
I'm not quite sure if I get you right.
We would have two packages: nodejs and iojs. Node.js uses npm as package
management system. iojs is based on Node.js and compatible to npm. In
Buildroot, additional modules for Node.js are installed with
BR2_PACKAGE_NODEJS_MODULES_ADDITIONAL.
Additional modules for io.js will be installed with
BR2_PACKAGE_IOJS_MODULES_ADDITIONAL.
This is the config menu:
[*] iojs
Module Selection --->
() Additional modules
[] nodejs
Module Selection --->
() Additional modules
There are no packages in Buildroot which depends on or selects the
package nodejs (or iojs).
Best regards
J?rg
prev parent reply other threads:[~2015-01-20 17:45 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-14 23:38 [Buildroot] [PATCH 1/1] package/iojs: new package Jörg Krause
2015-01-15 4:47 ` Baruch Siach
2015-01-15 8:34 ` Thomas Petazzoni
2015-01-15 19:58 ` Jörg Krause
2015-01-18 16:29 ` Yann E. MORIN
2015-01-20 17:45 ` Jörg Krause [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1421775938.28321.10.camel@posteo.de \
--to=jkrause@posteo.de \
--cc=buildroot@busybox.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox