All of lore.kernel.org
 help / color / mirror / Atom feed
From: Paul Sokolovsky <pmiscml@gmail.com>
To: Thomas Kunze <thommycheck@gmx.de>
Cc: oe ml <openembedded-devel@lists.openembedded.org>
Subject: Re: Hidden depenencies
Date: Sun, 27 Jan 2008 15:17:57 +0200	[thread overview]
Message-ID: <178568040.20080127151757@gmail.com> (raw)
In-Reply-To: <1201306409.6002.4.camel@HD>

Hello Thomas,

Saturday, January 26, 2008, 2:13:29 AM, you wrote:

> Hi everybody,

> I just spend some hours to figure out why a kernel module I added to
> MACHINE_EXTRA_RRECOMMENDS didn't show up in images. The solution is to
> rebuild task-base.

  To be more exact/verbose, the solution is to bump task-base's PR.

> I think there should a way to handle this in oe.

  Yes, the explicit bumping of PR. Why this is the way to handle it in
OE becomes clear after trying to devise some other scheme. Of course,
some warning from bitbake's side would be nice (just as many other
things from bitbake's side).

> But
> for now we should document such hidden dependencies.

  It's more of indirect dependencies than hidden IMHO. It's not hidden
per se - looking at task-base.bb will immediately shows the fact that
it references MACHINE_EXTRA_*. And vice-versa, doing a
grep -r MACHINE_EXTRA on OE tree will show all its referents.

> Where should this
> be in the wiki? Do you know additional hidden dependencies?

> My list so far:
> MACHINE_EXTRA_RRECOMMENDS -> task-base
module_autoload_* ->> virtual/kernel

   There's pretty developed manual for OE. It already has a section on
task-base, so that info should go there. The same for kernel.

> Regards,
> Thomas


[]

-- 
Best regards,
 Paul                            mailto:pmiscml@gmail.com




      reply	other threads:[~2008-01-27 13:06 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-26  0:13 Hidden depenencies Thomas Kunze
2008-01-27 13:17 ` Paul Sokolovsky [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=178568040.20080127151757@gmail.com \
    --to=pmiscml@gmail.com \
    --cc=openembedded-devel@lists.openembedded.org \
    --cc=thommycheck@gmx.de \
    /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.