All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dvorkin Dmitry <dvorkin@tibbo.com>
To: openembedded-core@lists.openembedded.org
Subject: wrong automatic dependency
Date: Fri, 05 Sep 2014 16:36:03 +0800	[thread overview]
Message-ID: <540975F3.7050806@tibbo.com> (raw)

Hello!

I wrote my own recipe for crda.
(http://wireless.kernel.org/en/developers/Regulatory/CRDA)

Dependencies is:
DEPENDS = "libgcrypt libnl"
RDEPENDS_${PN} = "udev wireless-regdb"

Crda Makefile is using python to rebuild it's database in 
build/installation step.
After installation I have several packages: crda itself, crda-dev, 
crda-doc, ... etc.
In my image I'm using only 'crda' package that doesn't need python.

But it seems Yocto detects python and add automatic dependency of python 
to my image anyway.

$ grep "crda" ./*.dot | grep pyt
./task-depends.dot:"crda.do_build" -> "python-dbus.do_package_write_ipk"
./task-depends.dot:"crda.do_build" -> "python.do_package_write_rpm"
./task-depends.dot:"crda.do_build" -> "python.do_package_write_deb"
./task-depends.dot:"crda.do_build" -> "python.do_package_write_ipk"
./task-depends.dot:"crda.do_build" -> 
"python-pygobject.do_package_write_rpm"
./task-depends.dot:"crda.do_build" -> 
"python-pygobject.do_package_write_deb"
./task-depends.dot:"crda.do_build" -> 
"python-pygobject.do_package_write_ipk"
./task-depends.dot:"crda.do_build" -> "python-dbus.do_package_write_rpm"
./task-depends.dot:"crda.do_build" -> "python-dbus.do_package_write_deb"

Is there any way to get rid of python dependency in this and only this 
recipe? it makes my image significally bigger.


             reply	other threads:[~2014-09-05  8:36 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-05  8:36 Dvorkin Dmitry [this message]
2014-09-05  9:13 ` wrong automatic dependency Eric Bénard
2014-09-05  9:35   ` Dvorkin Dmitry
2014-09-05  9:46     ` Eric Bénard
  -- strict thread matches above, loose matches on Subject: below --
2014-09-05  1:51 Dvorkin Dmitry

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=540975F3.7050806@tibbo.com \
    --to=dvorkin@tibbo.com \
    --cc=openembedded-core@lists.openembedded.org \
    /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.