From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v3 1/1] jsen: new package
Date: Tue, 23 Feb 2016 22:04:13 +0100 [thread overview]
Message-ID: <20160223220413.2050528c@free-electrons.com> (raw)
In-Reply-To: <56CCC4C4.5020402@mind.be>
Arnout,
On Tue, 23 Feb 2016 21:44:52 +0100, Arnout Vandecappelle wrote:
> I wonder if this is really the correct place for it. This menu is for
> Javascript libraries that are installed in /var/www, i.e. that are meant to be
> used by web clients. AFAICS, however, jsen is meant to be used with nodejs
> (which is why it's installed in /usr/share, I guess). So I think we should
> create a new menu under the nodejs package:
Atul originally placed jsen under the Libraries -> JSON/XML, and I
suggested him to put it under the Javascript libraries.
> source "package/nodejs/Config.in"
> if BR2_PACKAGE_NODEJS
> menu "NodeJS libraries/modules"
> source "package/jsen/Config.in"
> endmenu
> endif
If it's indeed a NodeJS package, then comes the question of how we are
going to package those zillions of modules. Today, one can request any
random NodeJS module to be installed using
BR2_PACKAGE_NODEJS_MODULES_ADDITIONAL (which is simple, but obviously
circumvents completely the download and legal infrastructures of
Buildroot).
Atul, are you using jsen in the context of NodeJS ? If not, in which
context are you using it ?
Thanks!
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2016-02-23 21:04 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-23 13:24 [Buildroot] [PATCH v3 1/1] jsen: new package Atul Singh
2016-02-23 20:44 ` Arnout Vandecappelle
2016-02-23 21:04 ` Thomas Petazzoni [this message]
2016-02-25 10:32 ` Jörg Krause
2016-02-25 12:51 ` Thomas Petazzoni
2016-02-25 14:01 ` Jörg Krause
2016-02-25 16:20 ` Thomas Petazzoni
2016-03-28 14:01 ` Jörg Krause
2016-03-28 14:07 ` Thomas Petazzoni
2016-04-25 15:45 ` Matthew Weber
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=20160223220413.2050528c@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