| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
| |
Closes: https://bugs.gentoo.org/648690
Package-Manager: Portage-2.3.24, Repoman-2.3.6
|
|
|
|
| |
Package-Manager: Portage-2.3.24, Repoman-2.3.6
|
|
|
|
|
| |
Package-Manager: Portage-2.3.24, Repoman-2.3.6
RepoMan-Options: --include-arches="ia64"
|
|
|
|
|
|
|
|
|
| |
Closes: https://bugs.gentoo.org/647046
Unlike suggested in the bug, I find drm being confusing in ffmpeg case as this can be mistaken for Digital Right Management support.
Since we do not have a drm/libdrm global useflag, I went for libdrm.
Package-Manager: Portage-2.3.24, Repoman-2.3.6
|
|
|
|
| |
Package-Manager: Portage-2.3.24, Repoman-2.3.6
|
|
|
|
| |
Package-Manager: Portage-2.3.24, Repoman-2.3.6
|
|
|
|
|
| |
Package-Manager: Portage-2.3.19, Repoman-2.3.6
RepoMan-Options: --include-arches="arm"
|
|
|
|
|
|
|
|
|
|
| |
My change to fix 9999 in 31be70b4de8dc1f3627765a4a35a4b5cf90a170f
broke all versions when ffmpeg is not already installed. I have
reverted this change for earlier versions and introduced a new patch
with a different approach for 9999.
Closes: https://bugs.gentoo.org/643750
Package-Manager: Portage-2.3.19, Repoman-2.3.6
|
|
|
|
|
|
|
| |
Suggested-by: stressfactor <redditcensorshipsucks@protonmail.com>
Acked-by: Alexis Ballier <aballier@gentoo.org>
Closes: https://bugs.gentoo.org/629938
Package-Manager: Portage-2.3.19, Repoman-2.3.6
|
|
|
|
| |
Gentoo-Bug: http://bugs.gentoo.org/639698
|
|
|
|
|
| |
Bug: https://bugs.gentoo.org/639698
Package-Manager: Portage-2.3.19, Repoman-2.3.6
|
|
|
|
| |
Package-Manager: Portage-2.3.19, Repoman-2.3.6
|
|
|
|
| |
Package-Manager: Portage-2.3.19, Repoman-2.3.6
|
|
|
|
|
|
|
|
|
|
|
|
| |
This flag controls a corresponding configure option, which previously
was left to autodetection, causing misdetection and compilation failure
for users having GNUstep installed.
Bug: https://bugs.gentoo.org/637482
Suggested-by: Alexis Ballier <aballier@gentoo.org>
Acked-by: Luca Barbato <lu_zero@gentoo.org>
Acked-by: Alexis Ballier <aballier@gentoo.org>
Package-Manager: Portage-2.3.17, Repoman-2.3.6
|
|
|
|
|
| |
Package-Manager: Portage-2.3.19, Repoman-2.3.6
RepoMan-Options: --include-arches="ppc64"
|
|
|
|
| |
Package-Manager: Portage-2.3.19, Repoman-2.3.6
|
|
|
|
|
|
|
|
| |
Some libraries were missing from the final link. This just involved
referencing FF_EXTRALIBS instead of FFEXTRALIBS. Also tested with
3.3.3.
Package-Manager: Portage-2.3.19, Repoman-2.3.6
|
|
|
|
|
| |
Closes: https://bugs.gentoo.org/635156
Package-Manager: Portage-2.3.16, Repoman-2.3.6
|
|
|
|
| |
Package-Manager: Portage-2.3.16, Repoman-2.3.6
|
|
|
|
|
| |
Closes: https://bugs.gentoo.org/636696
Package-Manager: Portage-2.3.16, Repoman-2.3.6
|
|
|
|
|
| |
Package-Manager: Portage-2.3.13, Repoman-2.3.3
RepoMan-Options: --include-arches="arm"
|
|
|
|
| |
Package-Manager: Portage-2.3.12, Repoman-2.3.4
|
|
|
|
|
| |
Package-Manager: Portage-2.3.13, Repoman-2.3.4
RepoMan-Options: --include-arches="ia64"
|
|
|
|
| |
Package-Manager: Portage-2.3.13, Repoman-2.3.4
|
|
|
|
| |
Package-Manager: Portage-2.3.13, Repoman-2.3.4
|
|
|
|
|
| |
Package-Manager: Portage-2.3.12, Repoman-2.3.3
RepoMan-Options: --include-arches="ppc ppc64"
|
|
|
|
|
|
|
| |
Otherwise build will fail at building tools/aviocat instead of
tools/aviocat.exe and so on.
Package-Manager: Portage-2.3.11, Repoman-2.3.3
|
|
|
|
| |
Package-Manager: Portage-2.3.11, Repoman-2.3.3
|
|
|
|
|
| |
Package-Manager: Portage-2.3.10, Repoman-2.3.3
RepoMan-Options: --include-arches="hppa"
|
|
|
|
| |
Package-Manager: Portage-2.3.8, Repoman-2.3.3
|
|
|
|
| |
Package-Manager: Portage-2.3.11, Repoman-2.3.3
|
|
|
|
|
|
|
| |
Andreas Sturmlechner.
Close: https://bugs.gentoo.org/633576
Package-Manager: Portage-2.3.11, Repoman-2.3.3
|
|
|
|
| |
Package-Manager: Portage-2.3.11, Repoman-2.3.3
|
|
|
|
|
| |
Package-Manager: Portage-2.3.10, Repoman-2.3.3
RepoMan-Options: --include-arches="ppc"
|
|
|
|
|
| |
Package-Manager: Portage-2.3.10, Repoman-2.3.3
RepoMan-Options: --include-arches="ppc64"
|
|
|
|
| |
Package-Manager: Portage-2.3.10, Repoman-2.3.3
|
|
|
|
| |
Package-Manager: Portage-2.3.10, Repoman-2.3.3
|
|
|
|
|
| |
Package-Manager: Portage-2.3.10, Repoman-2.3.3
RepoMan-Options: --include-arches="hppa"
|
|
|
|
|
| |
Package-Manager: Portage-2.3.8, Repoman-2.3.3
RepoMan-Options: --include-arches="ia64"
|
|
|
|
| |
Package-Manager: Portage-2.3.8, Repoman-2.3.3
|
|
|
|
| |
Package-Manager: Portage-2.3.8, Repoman-2.3.3
|
|
|
|
|
| |
Package-Manager: Portage-2.3.6, Repoman-2.3.1
RepoMan-Options: --include-arches="arm"
|
|
|
|
| |
Gentoo-Bug: 622912
|
|
|
|
|
| |
Bug: https://bugs.gentoo.org/show_bug.cgi?id=627018
Package-Manager: Portage-2.3.6, Repoman-2.3.3
|
|
|
|
|
|
|
| |
This version is about to go stable but I have stable masked the
chromium flag for now.
Package-Manager: Portage-2.3.8, Repoman-2.3.2
|
|
|
|
|
|
|
| |
This makes the patch apply against any version. The include line will
work just as well at the end of the Makefile.
Package-Manager: Portage-2.3.8, Repoman-2.3.2
|
|
|
|
|
| |
Package-Manager: Portage-2.3.8, Repoman-2.3.3
RepoMan-Options: --include-arches="ia64"
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Chromium is built from source and therefore can be built against the
system ffmpeg. Google Chrome already ships with support for
proprietary codecs and has libffmpeg.so built in.
Opera and Vivaldi, on the other hand, do not support proprietary
codecs and actively encourage you to replace the libffmpeg.so they
provide. Official instructions involve downloading the huge Chromium
tarball and building tons of baggage that you don't actually need,
despite the fact that libffmpeg.so is really just the main ffmpeg
libraries combined.
In order to build this, I felt it was worthwhile leveraging our
existing feature-rich ffmpeg package rather than duplicating it or
creating some poor imitation. This commit shows what little extra code
is required.
It would be possible to link to the regular libraries directly instead
of buildling additional copies if it weren't for the fact that these
browsers are usually built with -DFF_API_CONVERGENCE_DURATION=0,
making the ABI incompatible, at least until libavcodec hits 59.
That aside, all Chromium versions between 59 and 61 (maybe earlier?)
use the 55.57.57 ffmpeg ABI found in the 3.x series. Having these
browsers optionally RDEPEND on ffmpeg:0/55.57.57[chromium] should
therefore not be a problem for the time being. They simply need to
provide a symlink.
I have tested this with current versions of vivaldi, vivaldi-snapshot,
opera, opera-beta, and opera-developer. None were able to play videos
on news.bbc.co.uk without Flash until swapping in this library.
It has been noted that Vivaldi could potentially be built from
source. I may explore this possibility but I believe this change is
still useful, especially as some lack sufficient hardware to build
these browsers from source.
Package-Manager: Portage-2.3.6, Repoman-2.3.2
|
|
|
|
|
|
| |
bugs #628302 and #627562
Package-Manager: Portage-2.3.8, Repoman-2.3.3
|
|
|
|
| |
Package-Manager: Portage-2.3.5, Repoman-2.3.2
|