Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] package/spidermonkey: do not build the JavaScript shell, by default
Date: Sun, 8 Mar 2020 22:26:58 +0100	[thread overview]
Message-ID: <20200308222658.0cdeee8d@windsurf.home> (raw)
In-Reply-To: <CAJ4jsado7Y_iHwtJVNNGta7pez_Zsx_fi_y6+wtrhmA_P0a5Xw@mail.gmail.com>

Hello Carlos,

On Sun, 8 Mar 2020 12:11:41 -0300
Carlos Santos <unixmania@gmail.com> wrote:

> > We already had a 0001 patch, we actually have 10 patches on
> > spidermonkey, so I renamed this one 0011.  
> 
> Hum, that's the price passing "1" instead of "11" to --start-number. :-(

Hehe :-)

> 
> > Has this patch been submitted upstream ?  
> 
> Well, "upstream" is Firefox and I don't believe they would care about
> an installation error when we compile a code sub-tree taken from a
> tarball made for Gentoo with an extra patch to force in-tree builds.
> ;-)

Indeed, there is not really a regular upstream for spidermonkey.
Fortunately, there are some patches submitting to polkit to make it use
the duktape JS engine instead of spidermonkey, hopefully they will be
merged in the near future.

> If the patch annoys you we can just use a post-install-target hook to
> remove js60. I didn't follow this approach because I was afraid that
> not passing --disable-js-shell would lead to the inclusion of code
> that could cause problem at run time.

Nah, the patch is fine, let's keep it this way.

Thanks!

Thomas
-- 
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com

      reply	other threads:[~2020-03-08 21:26 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-08  3:21 [Buildroot] [PATCH] package/spidermonkey: do not build the JavaScript shell, by default unixmania at gmail.com
2020-03-08 13:52 ` Thomas Petazzoni
2020-03-08 15:11   ` Carlos Santos
2020-03-08 21:26     ` Thomas Petazzoni [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=20200308222658.0cdeee8d@windsurf.home \
    --to=thomas.petazzoni@bootlin.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