Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] mtd: add option to build mkfs.ubifs for target
Date: Wed, 31 Jul 2013 08:48:06 +0200	[thread overview]
Message-ID: <20130731084806.2270f7f3@skate> (raw)
In-Reply-To: <51F872B2.5080100@acm.org>

Dear Paul B. Henson,

On Tue, 30 Jul 2013 19:13:06 -0700, Paul B. Henson wrote:

> It looks like you copied the dependencies from util-linux? I'm not that 
> familiar with kconfig, there's no concept of transitive dependencies, 
> such that if mkfs.ubifs selects util-linux, it will automatically 
> inherit its dependencies? If I'm understanding correctly, if at some 
> point util-linux changes dependencies, the mtd config for mkfs.ubifs 
> would also need to be updated explicitly to capture them?

That's correct. When you "select FOO", kconfig ignores the dependencies
that "config FOO" may have, so you have to manually propagate them.
That's a bit annoying, but we don't have (yet?) enough understanding of
kconfig internals to change that. Yann E. Morin is getting more and
more knowledge about kconfig internals, so I'm hoping it may happen
some day, but for now, we have to propagate those dependencies manually.

Thanks!

Thomas
-- 
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com

      reply	other threads:[~2013-07-31  6:48 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-29  2:11 [Buildroot] [PATCH] mtd: add option to build mkfs.ubifs for target Paul B. Henson
2013-07-29 12:47 ` Thomas De Schampheleire
2013-07-29 18:20   ` Paul B. Henson
2013-07-29 18:51 ` Thomas Petazzoni
2013-07-31  2:13   ` Paul B. Henson
2013-07-31  6:48     ` 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=20130731084806.2270f7f3@skate \
    --to=thomas.petazzoni@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox