All of lore.kernel.org
 help / color / mirror / Atom feed
From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 2/2] jq: enable host package
Date: Thu, 22 Oct 2015 21:54:38 +0200	[thread overview]
Message-ID: <56293EFE.9050009@mind.be> (raw)
In-Reply-To: <CAAXf6LVLoU=sFyoEFhPyagqguVO0OV-dhFT5-JmMVPJGF4i9AA@mail.gmail.com>

On 22-10-15 10:22, Thomas De Schampheleire wrote:
> On Wed, Oct 21, 2015 at 11:20 PM, Thomas Petazzoni
> <thomas.petazzoni@free-electrons.com> wrote:
>> Arnout,
>>
>> On Wed, 21 Oct 2015 23:04:21 +0200, Arnout Vandecappelle wrote:
>>
>>>  I was thinking the same thing when I say the patch, but I don't care enough to
>>> really comment on it. It's a bit similar to packages that depend on some host
>>> preprocessing tool, like flex. But then of course we just have a dependency and
>>> not a Config.in.host.
>>
>> To me, host packages that are a dependency of some other target
>> packages have a real and strong reason to exist. The ones that don't
>> should really fall into the "useful for debugging, flashing or
>> preparing images" category IMO.
>>
>>>  OTOH, if we accept this, it kind of opens the doors to support almost
>>> everything as a host package. But maybe there's nothing wrong with that either.
>>
>> Opening the door to almost everything as a host package is personally
>> something that I'd like to avoid.
> 
> I don't think that we would open the door to 'almost every package' as
> host package. For many packages, it makes no sense to have them as
> host package in the context of buildroot, say audio/video,
> profiling/benchmark, hardware handling, mail, miscellaneous,
> networking apps, ...
> In fact, I would argue that almost none of the packages we have in
> Buildroot make sense as host packages, except those that we already
> have, and a few limited categories of tools. In my opinion, one such
> category could be config file handling, and host-jq fits into that
> category. It's the type of thing one can reasonably need to put
> together filestystem images for embedded devices, especially in
> environments where many (variants of) devices are being developed.

 So that basically puts jq into the 'image generation' category for you :-)

 Note that personally I don't have much of a problem with adding more host
packages, I don't think they tend to add much of a maintenance burden.

 Regards,
 Arnout



-- 
Arnout Vandecappelle                          arnout at mind be
Senior Embedded Software Architect            +32-16-286500
Essensium/Mind                                http://www.mind.be
G.Geenslaan 9, 3001 Leuven, Belgium           BE 872 984 063 RPR Leuven
LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle
GPG fingerprint:  7493 020B C7E3 8618 8DEC 222C 82EB F404 F9AC 0DDF

  reply	other threads:[~2015-10-22 19:54 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 [this message]
2015-10-22 16:39     ` Yann E. MORIN
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=56293EFE.9050009@mind.be \
    --to=arnout@mind.be \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.