From: Koen Kooi <koen@dominion.thruhere.net>
To: openembedded-devel@lists.openembedded.org
Subject: Re: unnecessary dependencies?
Date: Mon, 01 Aug 2011 11:28:07 +0200 [thread overview]
Message-ID: <j15rj7$ng1$1@dough.gmane.org> (raw)
In-Reply-To: <4E367018.7020709@dresearch-fe.de>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Op 01-08-11 11:21, Steffen Sledz schreef:
> On 01.08.2011 11:00, Phil Blundell wrote:
>> On Mon, 2011-08-01 at 08:58 +0200, Steffen Sledz wrote:
>>> We are working on an application which requires libgssdp.
>>>
>>> libgssdp requires libsoup, libsoup inherits gnome, gnome inherits gtk-icon-cache, gtk-icon-cache rdepends hicolor-icon-theme. So this icon theme (probably a lot more gnome stuff) unnecessarily allocates place in our image (we do not have a GUI). :(
>>>
>>> Are these deps really necessary?
>>
>> It sounds as though libsoup possibly shouldn't be inheriting gnome. Can you figure out whether gtk-icon-cache is actually doing anything useful in this case?
>
> "libsoup is an HTTP client/server library" only. I can't really see any need for GUI componenets.
And if you look at the source, you'll see it links against libgnome-keyring, libgconf and and other GNOME, but non-GUI components. Libsoup is heavy, we all know that. So please send a patch for gtk-icon-cache to only conditionally add the RDEPENDS as I said earlier in this thread.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Darwin)
iD8DBQFONnGnMkyGM64RGpERAjPPAJ4wZYUAnfB4vyy8GF28FrkTvseHhgCfbhw4
iTv4QcQI2EnqO/pLou5itmk=
=rvYI
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2011-08-01 9:32 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-01 6:58 unnecessary dependencies? Steffen Sledz
2011-08-01 7:12 ` Koen Kooi
2011-08-01 8:35 ` Frans Meulenbroeks
2011-08-01 9:19 ` Steffen Sledz
2011-08-01 9:22 ` Phil Blundell
2011-08-01 9:00 ` Phil Blundell
2011-08-01 9:21 ` Steffen Sledz
2011-08-01 9:28 ` Koen Kooi [this message]
2011-08-01 9:29 ` Phil Blundell
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='j15rj7$ng1$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 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.