All of lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Tworek <tworaz666@gmail.com>
To: openembedded-devel@lists.openembedded.org
Cc: Koen Kooi <koen@dominion.thruhere.net>
Subject: Re: [meta-oe][PATCH 3/3] pidgin: Add gconf to RDEPENDS for libpurple.
Date: Mon, 30 Jan 2012 21:28:46 +0100	[thread overview]
Message-ID: <4F26FD7E.5040908@gmail.com> (raw)
In-Reply-To: <jg6sti$vjj$1@dough.gmane.org>

On 01/30/2012 09:00 PM, Koen Kooi wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> 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.

> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.11 (Darwin)
> Comment: GPGTools - http://gpgtools.org
>
> iEYEARECAAYFAk8m9u8ACgkQMkyGM64RGpGRTQCgrzWdMpyRtNE3kO2CKw6b7haa
> j5UAoJ2NPDIIlCsRwYOJSTGTWd2i/hj0
> =axku
> -----END PGP SIGNATURE-----
>
>
> _______________________________________________
> Openembedded-devel mailing list
> Openembedded-devel@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel




  reply	other threads:[~2012-01-30 20:38 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 [this message]
2012-01-31  8:06     ` Koen Kooi
2012-01-31 16:53       ` McClintock Matthew-B29882
2012-01-31 18:45         ` Koen Kooi
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=4F26FD7E.5040908@gmail.com \
    --to=tworaz666@gmail.com \
    --cc=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 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.