Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Yann E. MORIN <yann.morin.1998@free.fr>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 2/2] jq: enable host package
Date: Thu, 22 Oct 2015 18:39:02 +0200	[thread overview]
Message-ID: <20151022163902.GA3797@free.fr> (raw)
In-Reply-To: <20151021223958.5605a589@free-electrons.com>

Thomas?, All,

On 2015-10-21 22:39 +0200, Thomas Petazzoni spake thusly:
> On Mon, 19 Oct 2015 12:42:09 +0200, Thomas De Schampheleire wrote:
> > From: Thomas De Schampheleire <thomas.de.schampheleire@gmail.com>
> > 
> > Allow building jq as host utility for use in post-build scripts.
> > This can be useful to created, edit, merge or even perform syntax checking
> > on JSON files.
> > 
> > Signed-off-by: Thomas De Schampheleire <thomas.de.schampheleire@gmail.com>
> 
> Since this host package clearly doesn't fall into the "debugging tool,
> flashing tool or image preparation tool" category, I'd like to collect
> the opinion of a few other developers before applying.
> 
> Peter, Arnout, Yann, what do you think?

On principle, I'm OK with user-selectable host packages, as long as there
is a real benefit to having it, like:
  - image preparation tools (fs, flash, dtc, bootloader utils...)
  - configuration tools (pwgen, SElinux compiler...)
  - debug tools

(Note: I'm not listing dependency of target package, since that is not
user-selectable.)

Adding any other type of package to be user-selectable will always be
debatable. I'm not sure where we should draw the line, but we could
provide guidelines, like:

  - the package is not usually packaged in distributions (or too old);
    libxslt for xsltproc comes to mind for example;

  - the submitter comes with a very clear use-case which can not
    otherwise be solved by other means (overlays, conditionals in
    post-build scripts...)

Now, as far as host-jq is concerned, I'm not very sure. The use-case
Thomas DS. invoques is tweaking config files for various targets.

Even though I understand that, and even though I could have thought the
same, I'm still not quite sure. JSON is indeed a pretty much usual
configuration format those days (whether that is sane is a question for
another thread ;-] ). However, I would argue (weakly) that this tool
should be provided by the host environment, not us.

Except: old, enterprise-class distributions (e.g. RHEL5) may lack that
tool, especially since it was born in 2012.

So, really, I wouln't really argue either way.

But surely, this would be our first host-package that is not in the
categories I listed above.

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.  |
'------------------------------^-------^------------------^--------------------'

  parent reply	other threads:[~2015-10-22 16:39 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-19 10:42 [Buildroot] [PATCH 1/2] jq: disable maintainer mode Thomas De Schampheleire
2015-10-19 10:42 ` [Buildroot] [PATCH 2/2] jq: enable host package Thomas De Schampheleire
2015-10-21 20:39   ` Thomas Petazzoni
2015-10-21 21:04     ` Arnout Vandecappelle
2015-10-21 21:20       ` Thomas Petazzoni
2015-10-22  8:22         ` Thomas De Schampheleire
2015-10-22 19:54           ` Arnout Vandecappelle
2015-10-22 16:39     ` Yann E. MORIN [this message]
2015-10-22 19:22       ` Thomas De Schampheleire
2015-10-25 20:37         ` Peter Korsgaard
2015-10-21 20:39 ` [Buildroot] [PATCH 1/2] jq: disable maintainer mode Thomas Petazzoni

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=20151022163902.GA3797@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