From: Yann E. MORIN <yann.morin.1998@free.fr>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] package/iojs: new package
Date: Sun, 18 Jan 2015 17:29:59 +0100 [thread overview]
Message-ID: <20150118162959.GQ4275@free.fr> (raw)
In-Reply-To: <1421351925.2625.14.camel@posteo.de>
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.
Regards,
Yann E. MORIN.
--
.-----------------.--------------------.------------------.--------------------.
| Yann E. MORIN | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software Designer | \ / CAMPAIGN | ___ |
| +33 223 225 172 `------------.-------: X AGAINST | \e/ There is no |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL | v conspiracy. |
'------------------------------^-------^------------------^--------------------'
next prev parent reply other threads:[~2015-01-18 16:29 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 [this message]
2015-01-20 17:45 ` Jörg Krause
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=20150118162959.GQ4275@free.fr \
--to=yann.morin.1998@free.fr \
--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