From: "Vitaly Zdanevich" <zdanevich.vitaly@ya.ru>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/proj/guru:dev commit in: www-client/yandex-browser/
Date: Sat, 9 Mar 2024 10:24:43 +0000 (UTC) [thread overview]
Message-ID: <1709979863.4fe7e5847d87118071d03671cff7ed766abfa928.zdanevich.vitaly@gentoo> (raw)
commit: 4fe7e5847d87118071d03671cff7ed766abfa928
Author: Vitaly Zdanevich <zdanevich.vitaly <AT> ya <DOT> ru>
AuthorDate: Sat Mar 9 10:24:23 2024 +0000
Commit: Vitaly Zdanevich <zdanevich.vitaly <AT> ya <DOT> ru>
CommitDate: Sat Mar 9 10:24:23 2024 +0000
URL: https://gitweb.gentoo.org/repo/proj/guru.git/commit/?id=4fe7e584
www-client/yandex-browser: Fix ffmpeg codec
Signed-off-by: Vitaly Zdanevich <zdanevich.vitaly <AT> ya.ru>
www-client/yandex-browser/yandex-browser-24.1.1.940_p1.ebuild | 7 +++++--
1 file changed, 5 insertions(+), 2 deletions(-)
diff --git a/www-client/yandex-browser/yandex-browser-24.1.1.940_p1.ebuild b/www-client/yandex-browser/yandex-browser-24.1.1.940_p1.ebuild
index a8c0c2bf13..56d08e7238 100644
--- a/www-client/yandex-browser/yandex-browser-24.1.1.940_p1.ebuild
+++ b/www-client/yandex-browser/yandex-browser-24.1.1.940_p1.ebuild
@@ -14,6 +14,8 @@ else
MY_PN=${PN}
fi
+FFMPEG="120"
+
DESCRIPTION="The web browser from Yandex"
HOMEPAGE="https://browser.yandex.ru/"
LICENSE="Yandex-EULA"
@@ -50,14 +52,13 @@ RDEPEND="
x11-libs/libXrandr
x11-libs/pango[X]
x11-misc/xdg-utils
- ffmpeg-codecs? ( media-video/ffmpeg-chromium )
+ ffmpeg-codecs? ( =media-video/ffmpeg-chromium-${FFMPEG} )
sys-libs/libudev-compat
dev-qt/qtcore
dev-qt/qtgui
dev-qt/qtwidgets
app-accessibility/at-spi2-core
"
-# TODO: check media-video/ffmpeg-chromium
DEPEND="
>=dev-util/patchelf-0.9
"
@@ -112,6 +113,8 @@ src_install() {
make_wrapper "${PN}" "./${PN}" "/${YANDEX_HOME}" "/usr/$(get_libdir)/${MY_PN}/lib" || die "Failed to mae wrapper"
+ dosym "${EPREFIX}/usr/$(get_libdir)/chromium/libffmpeg.so.${FFMPEG}" "${EPREFIX}/${YANDEX_HOME}/libffmpeg.so"
+
# yandex_browser binary loads libudev.so.0 at runtime
for icon in "${D}/${YANDEX_HOME}/product_logo_"*.png; do
next reply other threads:[~2024-03-09 10:24 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-09 10:24 Vitaly Zdanevich [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-03-21 16:49 [gentoo-commits] repo/proj/guru:dev commit in: www-client/yandex-browser/ Sergey Torokhov
2025-02-27 19:22 Sergey Torokhov
2024-12-30 20:40 Sergey Torokhov
2024-12-09 18:53 Sergey Torokhov
2024-11-08 22:05 Sergey Torokhov
2024-10-23 6:03 Sergey Torokhov
2024-09-21 17:49 Sergey Torokhov
2024-09-20 20:46 Sergey Torokhov
2024-09-04 17:46 Sergey Torokhov
2024-09-03 19:33 Sergey Torokhov
2024-08-23 20:19 Sergey Torokhov
2024-08-19 21:50 Sergey Torokhov
2024-08-03 21:14 Sergey Torokhov
2024-05-22 22:14 Sergey Torokhov
2024-05-16 19:05 Sergey Torokhov
2024-05-15 0:59 Julien Roy
2024-04-27 17:52 Sergey Torokhov
2024-03-11 10:55 David Roman
2024-03-10 7:41 Vitaly Zdanevich
2024-03-10 7:35 Vitaly Zdanevich
2024-03-09 3:22 Vitaly Zdanevich
2024-02-15 21:33 Sergey Torokhov
2024-02-09 9:44 Sergey Torokhov
2024-01-31 15:41 Vitaly Zdanevich
2024-01-01 2:46 Joe Kappus
2023-10-03 9:30 David Roman
2023-10-03 8:15 Vitaly Zdanevich
2023-10-03 8:03 Vitaly Zdanevich
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=1709979863.4fe7e5847d87118071d03671cff7ed766abfa928.zdanevich.vitaly@gentoo \
--to=zdanevich.vitaly@ya.ru \
--cc=gentoo-commits@lists.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