From: Saul Wold <sgw@linux.intel.com>
To: Constantin Musca <constantinx.musca@intel.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH v2] intltool: include intltool.m4 and add missing rdepends
Date: Wed, 19 Sep 2012 08:09:54 -0700 [thread overview]
Message-ID: <5059E042.3050805@linux.intel.com> (raw)
In-Reply-To: <5059C2CE.4050109@intel.com>
On 09/19/2012 06:04 AM, Constantin Musca wrote:
> On 09/19/2012 04:23 PM, Khem Raj wrote:
>>> >--- a/meta/recipes-devtools/intltool/intltool.inc
>>> >+++ b/meta/recipes-devtools/intltool/intltool.inc
>>> >@@ -7,11 +7,18 @@ SRC_URI
>>> ="http://launchpad.net/${BPN}/trunk/${PV}/+download/${BP}.tar.gz"
>>> > S = "${WORKDIR}/intltool-${PV}"
>>> >
>>> > DEPENDS = "libxml-parser-perl-native"
>>> >+RDEPENDS_${PN} = "gettext-dev libxml-parser-perl"
>> creating a runtime dependency on a dev package seems troublesome to me.
>> Can you explain why is this being done ?
>>
The question here is why do we need the gettext-dev package for
intltool? What does intltool need from the -dev package?
Sau!
>>> > DEPENDS_virtclass-native = "libxml-parser-perl-native"
>>> >-#RDEPENDS_${PN} = "libxml-parser-perl"
>>> >+# gettext is assumed to exist on the host
>>> >+RDEPENDS_${PN}_virtclass-native = "libxml-parser-perl-native"
>>> > RRECOMMENDS_${PN} = "perl-modules"
> Ross suggested to use these RDEPENDS after having issues with some
> packages on a image due to intltool.
>
> Constantin
>
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
>
next prev parent reply other threads:[~2012-09-19 15:22 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-19 9:59 [PATCH v2] intltool: include intltool.m4 and add missing rdepends Constantin Musca
2012-09-19 13:23 ` Khem Raj
2012-09-19 13:04 ` Constantin Musca
2012-09-19 15:09 ` Saul Wold [this message]
2012-09-19 15:15 ` Burton, Ross
2012-09-19 14:33 ` Constantin Musca
2012-09-19 15:10 ` Burton, Ross
2012-09-20 13:34 ` Richard Purdie
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=5059E042.3050805@linux.intel.com \
--to=sgw@linux.intel.com \
--cc=constantinx.musca@intel.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.