From: Koen Kooi <koen@dominion.thruhere.net>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [meta-oe][PATCH 3/3] pidgin: Add gconf to RDEPENDS for libpurple.
Date: Tue, 31 Jan 2012 19:45:15 +0100 [thread overview]
Message-ID: <jg9crr$bni$1@dough.gmane.org> (raw)
In-Reply-To: <CAEsOVNc+FnZf4hqDrHYE3AcjPO6wM3vFReQkbppJV9uqo=+tqQ@mail.gmail.com>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Op 31-01-12 17:53, McClintock Matthew-B29882 schreef:
> On Tue, Jan 31, 2012 at 2:06 AM, Koen Kooi <koen@dominion.thruhere.net>
> wrote:
>> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
>>
>> Op 30-01-12 21:28, Peter Tworek schreef:
>>> On 01/30/2012 09:00 PM, Koen Kooi wrote: Op 30-01-12 20:47, Peter
>>> Tworek schreef:
>>>>>> Without it postinst script for libpurple fails when gconf is
>>>>>> not installed: //var/lib/opkg/info/libpurple.postinst: line 8:
>>>>>> gconftool-2: command not found
>>> Why is gconf.bbclass failing to do that?
>>>> As far as I understand it only adds gconf to DEPENDS. If a package
>>>> contents are not linked with libgconf-2 (libpurple only needs
>>>> gconftool-2) gconf won't be pulled in as a runtime dependency.
>>
>> That means it's a bug in gconf.bbclass and needs to get fixed there.
>
> Really? Do you really want to automatically add gconf deps to the misc.
> packages added by a recipe?
Since it's adding the postinst calls with gconf-tool already, yes. Or do you
like having broken postinsts?
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (Darwin)
Comment: GPGTools - http://gpgtools.org
iEYEARECAAYFAk8oNrYACgkQMkyGM64RGpHORQCfbiw/JoEW5byJaWXigd23GNDD
TTIAn2xJ/EgmHT9LMoykyPVLB0DLTEZ7
=hvUv
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2012-01-31 18:53 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-30 19:47 [meta-oe][PATCH 3/3] pidgin: Add gconf to RDEPENDS for libpurple Peter Tworek
2012-01-30 20:00 ` Koen Kooi
2012-01-30 20:28 ` Peter Tworek
2012-01-31 8:06 ` Koen Kooi
2012-01-31 16:53 ` McClintock Matthew-B29882
2012-01-31 18:45 ` Koen Kooi [this message]
2012-01-31 19:05 ` Otavio Salvador
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='jg9crr$bni$1@dough.gmane.org' \
--to=koen@dominion.thruhere.net \
--cc=openembedded-devel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox