public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Alexis Ballier <aballier@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] The Gentoo Qt Project wants your help!
Date: Sat, 2 Mar 2013 14:32:47 +0100	[thread overview]
Message-ID: <20130302143247.3376a7d0@portable> (raw)
In-Reply-To: <20130302140828.2c498a46@gentoo.org>

On Sat, 2 Mar 2013 14:08:28 +0100
Tom Wijsman <TomWij@gentoo.org> wrote:

> On Sat, 2 Mar 2013 14:54:22 +0800
> Ben de Groot <yngwin@gentoo.org> wrote:
> 
> > media-video/avidemux (bundled libs)
> 
> I like this application, but am not so sure about maintaining this...
> =/
> 
> Would it be reasonable to create a new package avidemux-ffmpeg in
> which we create a version of ffmpeg with their patches applied?
> Perhaps we can also remove the parts of ffmpeg that aren't used by
> avidemux to keep the overhead of having ffmpeg twice on the system
> low.
> 
> I don't see any other reliable solution, unless upstream is willing to
> stop bundling ffmpeg and get their patches incorporated on that.
> But upon reading the progress on Debian, there is barely any progress
> on that as far as I am aware of; and I'm not willing to maintain a
> package that has 1) an unpatched ffmpeg that breaks it for people or
> 2) a bundled ffmpeg that keeps it from getting unmasked /
> reliable / ...
> 
> The other approach is for someone to attempt to try to get all these
> patches upstream, but some of them are undocumented which makes it
> hard to understand what the changes actually are done for; and at
> this point in time it is not guaranteed that ffmpeg would take these
> patches.
> 
> So, what is the Qt herd's opinion on creating a avidemux-ffmpeg
> package?

In the end if you dump their ffmpeg version and use it only for
avidemux, the end result is the same as bundling it.

If you want to do things correctly, you'd try to get the patches merged
upstream. Maybe some are not even necessary these days.

First you'd need to have an option to use system ffmpeg. Then you could
work on porting patches.

That is what xbmc is doing: they have a bundled copy with a couple of
patches they try to get merged upstream (mainly windows patches btw)
but allow using system version. That way it is easier to work on fixing
bugs rather than trusting avidemux for adding random undocumented
fixes...


  parent reply	other threads:[~2013-03-02 13:33 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-02  6:54 [gentoo-dev] The Gentoo Qt Project wants your help! Ben de Groot
2013-03-02  7:57 ` Diego Elio Pettenò
2013-03-03  9:43   ` Ben de Groot
2013-03-02 12:26 ` Jauhien Piatlicki
2013-03-03  9:44   ` Ben de Groot
2013-03-02 12:33 ` Samuli Suominen
2013-03-03 10:09   ` Ben de Groot
2013-03-02 12:36 ` Alexis Ballier
2013-03-02 13:08 ` Tom Wijsman
2013-03-02 13:29   ` Samuli Suominen
2013-03-02 14:35     ` Tom Wijsman
2013-03-02 14:39       ` Samuli Suominen
2013-03-02 17:27       ` Ben de Groot
2013-03-02 19:35       ` Davide Pesavento
2013-03-02 13:32   ` Alexis Ballier [this message]
2013-03-02 14:41     ` Tom Wijsman

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=20130302143247.3376a7d0@portable \
    --to=aballier@gentoo.org \
    --cc=gentoo-dev@lists.gentoo.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