And ffmpeg is the only pkg which depends on openjpeg in my system
hp ffmpeg # equery d openjpeg
* These packages depend on openjpeg:
media-video/ffmpeg-2.2.3-r1 (jpeg2k ? >=media-libs/openjpeg-1.5.0:0[abi_x86_32(-)?,abi_x86_64(-)?,abi_x86_x32(-)?,abi_mips_n32(-)?,abi_mips_n64(-)?,abi_mips_o32(-)?])
So, media-libs/openjpeg-1.5.0 and media-libs/openjpeg-1.5.1 and event media-libs/openjpeg-2.0.0 can satisfy ffmpeg-2.2.3-r1.ebuild jpeg2k use flag, why portage just pickup media-libs/openjpeg-1.5.1-r1 which require a keyword change?
Porage I am using is
sys-apps/portage-2.3.6-r8, and I am use stable branch, *not the current branch*.
Question
AlfredChen
Recently, portage pop up keyword changes needed for some pkg, but it seems it is not reasonable for me.
Let's take openjpeg for example here, highlight in blod
From the ebuild file we can see
And ffmpeg is the only pkg which depends on openjpeg in my system
check the version of openjpeg in portage tree
So, media-libs/openjpeg-1.5.0 and media-libs/openjpeg-1.5.1 and event media-libs/openjpeg-2.0.0 can satisfy ffmpeg-2.2.3-r1.ebuild jpeg2k use flag, why portage just pickup media-libs/openjpeg-1.5.1-r1 which require a keyword change?
Porage I am using is
sys-apps/portage-2.3.6-r8, and I am use stable branch, *not the current branch*.
Thanks.
BR Alfred
Link to comment
Share on other sites
5 answers to this question
Recommended Posts