public inbox for buildroot@busybox.net
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] package/linux-tools: selftests: add numactl dependency for net tests
Date: Wed, 22 Apr 2020 10:24:04 +0200	[thread overview]
Message-ID: <20200422102404.05b99229@windsurf.home> (raw)
In-Reply-To: <20200422112336.6cwyac5wim5i43n2@vkochan-ThinkPad-T470p>

On Wed, 22 Apr 2020 14:23:36 +0300
Vadim Kochan <vadim4j@gmail.com> wrote:

> My only concern is that user should guess which packages are needed for
> particular test suites (I mean at least per sub-system), or document it
> somewhere ?

This is pretty common in Buildroot that we have automatic optional
dependencies: we enable a feature if the necessary dependencies are
available. Having sub-options for everything would be a nightmare.

In addition, if a user had to build the selftests manually, he would
also have to figure out "aaah, I need numactl to build the network
tests".

In any case, the Buildroot .mk clearly documents the fact that package
ABC is needed to get a given feature in package XYZ.

Best regards,

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

      reply	other threads:[~2020-04-22  8:24 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-25 16:42 [Buildroot] [PATCH] package/linux-tools: selftests: add numactl dependency for net tests Vadym Kochan
2020-04-11 13:26 ` Thomas Petazzoni
2020-04-21 17:51   ` Vadim Kochan
2020-04-21 14:55     ` Thomas Petazzoni
2020-04-22 11:23       ` Vadim Kochan
2020-04-22  8:24         ` 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=20200422102404.05b99229@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