Openembedded Devel Discussions
 help / color / mirror / Atom feed
From: "Rafaël Carré" <funman@videolan.org>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [meta-multimedia][PATCH 3/3] VLC: drop gnome-vfs, it will be removed from upstream in VLC 3.0
Date: Thu, 5 Nov 2015 12:29:07 +0100	[thread overview]
Message-ID: <563B3D83.4000007@videolan.org> (raw)
In-Reply-To: <20151105111611.GC2556@jama>

On 05/11/2015 12:16, Martin Jansa wrote:
> On Thu, Nov 05, 2015 at 11:59:14AM +0100, Rafaël Carré wrote:
>> Hello,
>>
>> On 04/11/2015 23:25, Martin Jansa wrote:
>>> On Wed, Nov 04, 2015 at 05:03:19PM +0100, Rafaël Carré wrote:
>>>> ---
>>>
>>> Is it still used in 2.2.1 version? we aren't using 3.0 yet:
>>
>> Yes, that module is still present in 2.2 (2.2.1 and future 2.2.X versions).


>> What do you think?
> 
> NAK it's not acceptable to make gnome-vfs support undeterministic in
> 2.2.x just because some future 3.0 recipe won't use it.

Ok

> We already have too many autodetected dependencies again, last bunch
> added by new 1394 recipes in meta-multimedia:
> vlc-2.2.1: vlc rdepends on libavc1394, but it isn't a build dependency? [build-deps]
> vlc-2.2.1: vlc rdepends on libdvdnav, but it isn't a build dependency? [build-deps]
> vlc-2.2.1: vlc rdepends on libupnp, but it isn't a build dependency? [build-deps]
> 
> Add PACKAGECONFIG for it please and to get bonus points add

Done

> PACKAGECONFIG for deps from QA issues above.

I will take a deeper look as there are more than just those

>> Thanks for the feedback
>>
>>>>  meta-multimedia/recipes-multimedia/vlc/vlc.inc | 2 +-
>>>>  1 file changed, 1 insertion(+), 1 deletion(-)
>>>>
>>>> diff --git a/meta-multimedia/recipes-multimedia/vlc/vlc.inc b/meta-multimedia/recipes-multimedia/vlc/vlc.inc
>>>> index ad5c81d..dddbb5b 100644
>>>> --- a/meta-multimedia/recipes-multimedia/vlc/vlc.inc
>>>> +++ b/meta-multimedia/recipes-multimedia/vlc/vlc.inc
>>>> @@ -8,7 +8,7 @@ LIC_FILES_CHKSUM = "file://COPYING;md5=b234ee4d69f5fce4486a80fdaf4a4263"
>>>>  DEPENDS = "libfribidi libtool libgcrypt libgcrypt-native \
>>>>     virtual/libsdl libsdl-image dbus dbus-glib libxml2 gnutls \
>>>>     tremor faad2 ffmpeg flac libxpm libxinerama fluidsynth alsa-lib \
>>>> -   libdvdcss libdvdread lua-native lua libidn gnome-vfs \
>>>> +   libdvdcss libdvdread lua-native lua libidn \
>>>>     libdc1394 libraw1394 avahi libjpeg-turbo xz libmodplug mpeg2dec \
>>>>     libmtp libopus orc libsamplerate0 libusb1 schroedinger taglib \
>>>>     tiff xcb-util-keysyms samba"


      reply	other threads:[~2015-11-05 11:29 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-04 16:03 [meta-multimedia][PATCH 1/3] VLC: depends on gst-plugins-bad only if gst is enabled Rafaël Carré
2015-11-04 16:03 ` [meta-multimedia][PATCH 2/3] VLC: make libnotify a configurable dependency Rafaël Carré
2015-11-05 20:17   ` Martin Jansa
2015-11-05 20:42     ` Rafaël Carré
2015-11-05 20:57       ` Martin Jansa
2015-11-06  0:07         ` Tim Orling
2015-11-06 15:16           ` Rafaël Carré
2015-11-04 16:03 ` [meta-multimedia][PATCH 3/3] VLC: drop gnome-vfs, it will be removed from upstream in VLC 3.0 Rafaël Carré
2015-11-04 22:25   ` Martin Jansa
2015-11-05 10:59     ` Rafaël Carré
2015-11-05 11:16       ` Martin Jansa
2015-11-05 11:29         ` Rafaël Carré [this message]

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=563B3D83.4000007@videolan.org \
    --to=funman@videolan.org \
    --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