[SCM] ffmpeg/master: Disable unavailable frei0r, opencv and x264 on mips64el.
balint at balintreczey.hu
Tue Sep 22 16:23:57 UTC 2015
2015-09-22 16:23 GMT+02:00 Andreas Cadhalpun <andreas.cadhalpun at googlemail.com>:
> Hi James,
> On 16.09.2015 11:50, James Cowgill wrote:
>> On Tue, 2015-09-15 at 23:03 +0000, aca-guest at users.alioth.debian.org wrote:
>>> The following commit has been merged in the master branch:
>>> commit d4a91baaa754a5f60c84ca9c85decf82dc6bfc82
>>> Author: Andreas Cadhalpun <Andreas.Cadhalpun at googlemail.com>
>>> Date: Tue Sep 15 20:34:18 2015 +0200
>>> Disable unavailable frei0r, opencv and x264 on mips64el.
>> Please don't do this (unless you've been asked to by someone else?).
> Why not?
>> mips64el is still in its initial build and lots of stuff hasn't been
>> built yet (due to time).
> All other ffmpeg build-dependencies have already been built there.
>> FFmpeg is also involved in a few dependency cycles
> Exactly. The cycles involve frei0r, opencv and x264.
>> which can be resolved without any source changes.
>> Eg this cycle:
>> [ffmpeg] -> libx264-dev [x264] -> libavformat-dev [ffmpeg]
>> will be resolved after either ffmpeg or x264 are manually uploaded by
>> the mips64el potrers.
> They will also be resolved with this change, which won't require
> any manual intervention from mips64el porters.
> Then x264 and opencv (and after that frei0r) can build, so that they
> can be re-enabled on mips64el with the next ffmpeg upload.
> I've done the same for x32 and it worked fine.
It will always work, FTP Masters nor dpkg-buildpackage won't reject it. :-)
It is just obsolete IMO.
In my packages I let porters decide on those matters, I never disable
build-dependencies like those on my own.
If a dependency becomes available, my package will build, too. I think
porters prefer this way, too.
More information about the pkg-multimedia-maintainers