From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] Analysis of build results for 2017-05-04
Date: Sat, 6 May 2017 14:45:41 +0200 [thread overview]
Message-ID: <20170506144541.36687ea3@free-electrons.com> (raw)
In-Reply-To: <CAFGQKxefZ5eA+aQ9WqWR9J8GN_4oOoPApUPBOGebuC7YeHSONQ@mail.gmail.com>
Hello,
On Sat, 6 May 2017 10:14:57 +0100, Martin Bark wrote:
> I had been thinking for a while about removing
> BR2_PACKAGE_NODEJS_MODULES_EXPRESS
> and BR2_PACKAGE_NODEJS_MODULES_COFFEESCRIPT given you can just set them
> with BR2_PACKAGE_NODEJS_MODULES_ADDITIONAL. They are also not that useful
> since they choose the latest version meaning builds are not even
> reproducible. BR2_PACKAGE_NODEJS_MODULES_ADDITIONAL allows you to install
> them and choose the exact version you want.
>
> Since they also cause build errors i think they should go. Node 7.10.0 was
> just released so i'll submit a patch set to upgrade node and remove the
> express and coffee script settings.
Agreed with the proposal of removing those options.
Thanks!
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
next prev parent reply other threads:[~2017-05-06 12:45 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-05 6:28 [Buildroot] [autobuild.buildroot.net] Build results for 2017-05-04 Thomas Petazzoni
2017-05-05 11:24 ` [Buildroot] Analysis of build " Thomas Petazzoni
2017-05-05 21:28 ` Peter Seiderer
2017-05-05 22:11 ` Matthew Weber
2017-05-06 12:52 ` Thomas Petazzoni
2017-05-06 14:14 ` Matthew Weber
2017-05-06 14:54 ` Thomas Petazzoni
2017-05-06 9:14 ` Martin Bark
2017-05-06 12:45 ` Thomas Petazzoni [this message]
2017-05-16 19:01 ` Peter Seiderer
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=20170506144541.36687ea3@free-electrons.com \
--to=thomas.petazzoni@free-electrons.com \
--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