From: Gustavo Zacarias <gustavo.zacarias@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] check: new package
Date: Tue, 8 Sep 2015 10:49:56 -0300 [thread overview]
Message-ID: <55EEE784.5090608@free-electrons.com> (raw)
In-Reply-To: <55EDE533.30103@mind.be>
On 07/09/15 16:27, Arnout Vandecappelle wrote:
>> Some people may use checkmk which is a host tool, which i remove for the target
>> (probably needs full gawk instead of busybox awk, and not very useful in the
>> target IMO).
>
> I fully agree on removing checkmk on the target. I can also see that you'd want
> it on the host, but the user has no way to select it since there is no
> Config.in.host... So the user would have to do an explicit 'make host-check' to
> get it. It also won't be tested in the autobuilders.
>
> So in principle, we only have host packages that are dependencies of other
> packages or that have a Config.in.host entry. An exception is when there is
> another package that uses it but that has not yet been accepted. Probably the
> reverse also exists: a host dependency that is no longer needed but the host
> package still exists.
>
> Thomas recently proposed to violate this principle in the context of the
> python-colorama package [1], to which I replied no [2]. But of course that's
> still open for discussion.
Hi Arnout.
I don't have any particular use for the host variant, so no plan on
arguing too much for it.
I'll spin v2 unless someone objects the other way around with a valid
argument.
Regards.
prev parent reply other threads:[~2015-09-08 13:49 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-07 13:37 [Buildroot] [PATCH] check: new package gustavo.zacarias at free-electrons.com
2015-09-07 14:40 ` Arnout Vandecappelle
2015-09-07 16:29 ` Gustavo Zacarias
2015-09-07 19:27 ` Arnout Vandecappelle
2015-09-08 13:49 ` Gustavo Zacarias [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=55EEE784.5090608@free-electrons.com \
--to=gustavo.zacarias@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 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.