From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] libglib2: Avoid absolute path to python in shebang
Date: Thu, 19 Jul 2018 10:04:56 +0200 [thread overview]
Message-ID: <20180719100456.2146ce8b@windsurf> (raw)
In-Reply-To: <20180719075842.k3gxopajcat7f4dt@bifrost>
Hello,
+Peter in Cc.
On Thu, 19 Jul 2018 09:58:42 +0200, Anisse Astier wrote:
> We just hit this issue with the buildroot-2018.02 branch. Is this is the
> scope of LTS-backportable patches ?
>
> Otherwise it's very easy to take the patch in an external, but I'm
> guessing it might break other builds somewhere.
I think it definitely makes sense to have it in 2018.02.x, so I guess
Peter will backport it there.
However, it would be nice if someone could try to push this
upstream. The OE patch says it's not appropriate for upstream, but I
disagree, the fact that the shebang can be too long is a real problem,
and if both OE and Buildroot have to fix it, upstream should
(hopefully) be interested in finding a solution.
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Bootlin (formerly Free Electrons)
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2018-07-19 8:04 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-12 16:37 [Buildroot] [PATCH 1/1] libglib2: Avoid absolute path to python in shebang David Owens
2018-07-18 15:18 ` Thomas Petazzoni
2018-07-19 7:58 ` Anisse Astier
2018-07-19 8:04 ` Thomas Petazzoni [this message]
2018-07-19 11:50 ` anisse at astier.eu
2018-07-19 12:15 ` Thomas Petazzoni
2018-07-19 12:58 ` anisse at astier.eu
2018-07-19 13:24 ` Thomas Petazzoni
2018-07-19 11:04 ` Peter Korsgaard
2018-07-19 11:55 ` anisse at astier.eu
2018-07-19 21:44 ` Peter Korsgaard
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=20180719100456.2146ce8b@windsurf \
--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