From: Sebastian Spaeth <Sebastian@SSpaeth.de>
To: openembedded-devel@lists.openembedded.org
Subject: Re: gst-plugins-base -> gnome-vfs question
Date: Tue, 27 Oct 2009 14:59:36 +0100 [thread overview]
Message-ID: <4AE6FCC8.8090704@SSpaeth.de> (raw)
In-Reply-To: <hc6tgk$bvp$1@ger.gmane.org>
Koen Kooi wrote:
> On 27-10-09 14:31, Sebastian Spaeth wrote:
>> Current "gst-plugins-base" in org.oe.dev unconditionally depends on
>> "gnome-vfs" which in turn pulls in stuff like "avahi".
> It's already optional, don't install gst-plugin-gnomevfs
Thanks for the quick reply.
I was referring to the fact that the "gst-plugins-base" package directly
depends on gnome-vfs.
eg.
http://cgit.openembedded.org/cgit.cgi/openembedded/tree/recipes/gstreamer/gst-plugins-base_0.10.22.bb
contains:
DEPENDS += "libtheora alsa-lib libsm virtual/libx11 freetype gnome-vfs
libxv"
This does not look very optional to me. I keep thinking that there must
be something very obvious that I have missed.
>> I don't want avahi on my Freerunner, just because I want sound on it :-).
> I think you are confusing avahi and pulseaudio, in both cases you need
> to read up on the subject.
I do know the difference between avahi and pulseaudio, thank you ;-).
> You overlooked that installing gst-plugin-gnomevfs is completely your
> own choice
but gst-plugins-base pulling in gnome-vfs in its DEPENDS is not
optional, right?
Anyway, thanks for you quick reply. I guess I must have overlooked
something glaringly obvious here...
spaetz
next prev parent reply other threads:[~2009-10-27 14:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-27 13:31 gst-plugins-base -> gnome-vfs question Sebastian Spaeth
2009-10-27 13:44 ` Koen Kooi
2009-10-27 13:59 ` Sebastian Spaeth [this message]
2009-10-27 14:24 ` Koen Kooi
2009-10-27 13:53 ` Graeme Gregory
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=4AE6FCC8.8090704@SSpaeth.de \
--to=sebastian@sspaeth.de \
--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