Unmaintained upstream. No one seems to use openmax. Removal in 30 days.
The bug has been referenced in the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=0a191b6345088191771fcaa4c20a8b43d30ad7b1 commit 0a191b6345088191771fcaa4c20a8b43d30ad7b1 Author: Matt Turner <mattst88@gentoo.org> AuthorDate: 2018-10-16 19:53:19 +0000 Commit: Matt Turner <mattst88@gentoo.org> CommitDate: 2018-10-16 19:53:53 +0000 profiles: Mask media-libs/libomxil-bellagio for removal Bug: https://bugs.gentoo.org/668826 Signed-off-by: Matt Turner <mattst88@gentoo.org> profiles/package.mask | 4 ++++ 1 file changed, 4 insertions(+)
This is pulled in by mesa[openmax], so it's not exactly unused. I don't know if it is of any use, but if you mask it you might want to fix mesa as well.
(In reply to tt_1 from comment #2) > This is pulled in by mesa[openmax], so it's not exactly unused. I don't know > if it is of any use, but if you mask it you might want to fix mesa as well. I package.use.mask'd mesa's openmax USE flag at the same time. Did I miss something?
If something had been missed, the automated visibility checks would have raised an alert. Mesa openmax does not necessarily require libomxil-bellagio, since 18.1 it can alternatively use tizonia (which is not in the tree yet).
Though this package does not have a arm keyword, it provides support for hardware acceleration of ffmpeg on a Raspberry Pi: https://github.com/legotheboss/YouTube-files/wiki/(RPi)-Compile-FFmpeg-with-the-OpenMAX-H.264-GPU-acceleration Yet media-video/ffmpeg doesn't provide a [omx] for --enable-omx ...
The package is obviously used. There are no other bugs related. Masking something that is not receiving updates /because it is stable/ is not reasonable.
(In reply to Gordon Pettey from comment #6) > The package is obviously used. There are no other bugs related. Masking > something that is not receiving updates /because it is stable/ is not > reasonable. It's not obvious to me. Perhaps you can provide some citation for your claim. Looking in the historical repo, USE=openmax was added to media-libs/mesa because it was there, not because of any user request. I can find no evidence that media-libs/libomxil-bellagio was ever the reverse dependency of any other package. FWIW, when it was added in bug 191149 the question "is there any app that uses it ?" was asked (bug 191149#c8) and the response was "Not that I know of." (bug 191149#c9) The reason you found no open bugs in a search is that I closed then as WONTFIX when I started this removal process. Here they are: https://bugs.gentoo.org/668252 https://bugs.gentoo.org/654720 https://bugs.gentoo.org/631238 Last upstream commit was 2011. It's dead, Jim. But I'm always happy to spend a bunch of time explaining my actions to upset users without all the facts!
(In reply to Gordon Pettey from comment #6) > The package is obviously used. There are no other bugs related. Masking > something that is not receiving updates /because it is stable/ is not > reasonable. If you're going to comment, you should probably Cc yourself so you see a reply (comment #7).
The bug has been closed via the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=923714fbaa0012c8095cfa7471eb57a44b5f9942 commit 923714fbaa0012c8095cfa7471eb57a44b5f9942 Author: Matt Turner <mattst88@gentoo.org> AuthorDate: 2018-11-15 16:31:20 +0000 Commit: Matt Turner <mattst88@gentoo.org> CommitDate: 2018-11-15 17:42:13 +0000 media-libs/libomxil-bellagio: Remove Closes: https://bugs.gentoo.org/668826 Signed-off-by: Matt Turner <mattst88@gentoo.org> media-libs/libomxil-bellagio/Manifest | 2 - ...mxil-bellagio-0.9.3-dynamicloader-linking.patch | 14 ------- .../files/libomxil-bellagio-0.9.3-gcc5.patch | 19 --------- .../libomxil-bellagio-0.9.3-parallel-build.patch | 16 -------- .../files/libomxil-bellagio-0.9.3-version.patch | 21 ---------- .../libomxil-bellagio-0.9.3.ebuild | 45 ---------------------- media-libs/libomxil-bellagio/metadata.xml | 16 -------- profiles/package.mask | 4 -- 8 files changed, 137 deletions(-)
(In reply to Pengcheng Xu from comment #5) > Though this package does not have a arm keyword, it provides support for > hardware acceleration of ffmpeg on a Raspberry Pi: > > https://github.com/legotheboss/YouTube-files/wiki/(RPi)-Compile-FFmpeg-with- > the-OpenMAX-H.264-GPU-acceleration > > Yet media-video/ffmpeg doesn't provide a [omx] for --enable-omx ... For what it's worth, on a RPi libomxil is provided by media-libs/raspberrypi-userland.
