Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Martin Jansa <martin.jansa@gmail.com>
To: Paul Eggleton <paul.eggleton@linux.intel.com>
Cc: "yocto@yoctoproject.org" <yocto@yoctoproject.org>,
	openembedded-core@lists.openembedded.org,
	OE-devel <openembedded-devel@lists.openembedded.org>
Subject: Re: [yocto] GStreamer 0.10's future
Date: Thu, 8 May 2014 19:21:44 +0200	[thread overview]
Message-ID: <20140508172144.GR30955@jama> (raw)
In-Reply-To: <2287383.nOAQ2ykZqg@peggleto-mobl5.ger.corp.intel.com>

[-- Attachment #1: Type: text/plain, Size: 3589 bytes --]

On Thu, May 08, 2014 at 05:57:54PM +0100, Paul Eggleton wrote:
> On Thursday 08 May 2014 18:19:08 Martin Jansa wrote:
> > On Thu, May 08, 2014 at 04:07:19PM +0100, Paul Eggleton wrote:
> > > On Thursday 08 May 2014 15:48:40 Burton, Ross wrote:
> > > > Hi all,
> > > > 
> > > > Sorry for the cross-post but I want this to have a wide audience.
> > > > 
> > > > For the 1.7 release I want to move GStreamer 0.10 from oe-core into
> > > > meta-multimedia, and ensure everything in oe-core has ported to
> > > > GStreamer 1.x.  GStreamer 0.10 is considered dead upstream and is
> > > > unmaintained so we don't need to be shipping both versions anymore.
> > > > 
> > > > Everyone in agreement?  Should I expect any hate mail over this?
> > > 
> > > +1
> > > 
> > > The next question is does that mean for the "old" libav (which gst-ffmpeg
> > > depends upon), do we move that as well or drop it?
> > 
> > libav was migrated to oe-core quite recently and there is couple of
> > recipes in meta-oe, meta-webserver depending on it/ffmpeg so moving to
> > meta-multimedia wouldn't be very easy.
> > 
> > meta-multimedia/recipes-multimedia/sox/sox_14.4.0.bb:DEPENDS = "libpng libav
> > libsndfile1" meta-multimedia/recipes-mediacentre/xbmc/xbmc_git.bb:DEPENDS =
> > "libusb1 libcec libplist expat yajl gperf-native libxmu fribidi mpeg2dec
> > ffmpeg samba fontconfig curl python libass libmodplug libmicrohttpd wavpack
> > libmms cmake-native libsdl-image libsdl-mixer virtual/egl mysql5 sqlite3
> > libmms faad2 libcdio libpcre boost lzo enca avahi libsamplerate0
> > libxinerama libxrandr libxtst bzip2 virtual/libsdl jasper zip-native zlib
> > libtinyxml libmad"
> > meta-multimedia/recipes-multimedia/musicpd/mpd_0.18.9.bb:DEPENDS =
> > "alsa-lib libsamplerate0 libsndfile1 libvorbis libogg faad2 ffmpeg curl
> > sqlite bzip2 pulseaudio" meta-multimedia/recipes-multimedia/vlc/vlc.inc:  
> > faad2 ffmpeg flac libxpm libxinerama fluidsynth alsa-lib libdvdcss \
> > 
> > meta-oe/recipes-multimedia/nonworking/minidlna/minidlna_1.0.25.bb:DEPENDS =
> > "flac libav jpeg sqlite3 libexif libogg libid3tag"
> > meta-oe/recipes-support/opencv/opencv_2.4.bb:PACKAGECONFIG ??= "eigen gtk
> > jpeg libav png tiff v4l"
> > meta-oe/recipes-graphics/gegl/gegl_0.2.0.bb:PACKAGECONFIG[avformat] =
> > "--with-libavformat,--without-libavformat,libav"
> > meta-oe/recipes-multimedia/libpostproc/libpostproc_git.bb:DEPENDS = "libav"
> > meta-oe/recipes-multimedia/mplayer/mplayer2_git.bb:DEPENDS = "libvpx
> > libdvdread libtheora virtual/libsdl ffmpeg xsp zlib \
> > 
> > meta-webserver/recipes-httpd/cherokee/cherokee_1.2.98.bb:PACKAGECONFIG[ffmpe
> > g] = "--with-ffmpeg,--without-ffmpeg,libav"
> > 
> > But I would like to see migration to libav-9 which currently has negative
> > D_P (mplayer2 already depends on 9*, but there are few recipes which fails
> > with libav-9 too - see earlier world builds for list).
> 
> Yes, I'm just talking about libav 0.8 here - libav 9 would remain where it is. 
> That might still be problematic though given that their PN is the same. I'm 
> open to better suggestions, but I think we have to do *something* here.

Ah ok, I though you meant both versions.

Then I would rather drop 0.8 completely, otherwise it will be preferred
even with negative D_P from meta-multimedia (YOCTO #2964) and we cannot
expect people which happen to have meta-multimedia layer to know that
they are expected to update P_V everytime libav is updated in oe-core.

-- 
Martin 'JaMa' Jansa     jabber: Martin.Jansa@gmail.com

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 205 bytes --]

  reply	other threads:[~2014-05-08 17:28 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-08 14:48 GStreamer 0.10's future Burton, Ross
2014-05-08 15:02 ` Koen Kooi
2014-05-08 15:07 ` Paul Eggleton
2014-05-08 15:14   ` Burton, Ross
2014-05-08 16:04   ` Tim Orling
2014-05-08 16:19   ` [yocto] " Martin Jansa
2014-05-08 16:57     ` Paul Eggleton
2014-05-08 17:21       ` Martin Jansa [this message]
2014-05-08 17:29         ` Paul Eggleton
2014-05-08 22:06       ` Richard Purdie
2014-05-08 15:11 ` Carlos Rafael Giani
2014-05-08 15:25   ` Burton, Ross
2014-05-08 15:54 ` Burton, Ross
     [not found]   ` <536CF208.3000400@gmx.de>
2014-05-09 18:47     ` [yocto] [oe] " Burton, Ross
2014-05-09 19:22     ` Burton, Ross
2014-05-10 16:14 ` Khem Raj

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=20140508172144.GR30955@jama \
    --to=martin.jansa@gmail.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=openembedded-devel@lists.openembedded.org \
    --cc=paul.eggleton@linux.intel.com \
    --cc=yocto@yoctoproject.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