1 |
2015-05-16 9:44 GMT+03:00 Alan McKinnon <alan.mckinnon@×××××.com>: |
2 |
> On 16/05/2015 07:52, gevisz wrote: |
3 |
>> 2015-05-15 20:30 GMT+03:00 Alexander Kapshuk <alexander.kapshuk@×××××.com>: |
4 |
>>> On Fri, May 15, 2015 at 9:04 AM, Gevisz <gevisz@×××××.com> wrote: |
5 |
>>>> |
6 |
>>>> On Fri, 15 May 2015 01:45:35 -0400 Gregory Woodbury <redwolfe@×××××.com> |
7 |
>>>> wrote: |
8 |
>>>> |
9 |
>>>>> I had a similar problem with some packages wanting virtual/ffmpeg and |
10 |
>>>>> it wouldn't take the -libav USE flag without adding a keyword for |
11 |
>>>>> ~amd64 on the virtual. |
12 |
>>>>> (yes, I am going the opposite way from you, but the cause seem the |
13 |
>>>>> same -- various USE flags are not yet adjusted in the stable |
14 |
>>>>> branches.) |
15 |
>>>>> |
16 |
>>>>> Perhaps we need to request "stabilization" for some of the newer |
17 |
>>>>> packages to solve this. |
18 |
>>>> |
19 |
>>>> Thank you for confirming that libav USE flag do not work not only for me. |
20 |
>>>> |
21 |
>>>> However, it would be interesting to hear what the Gentoo devs think about |
22 |
>>>> this issue. |
23 |
>>> |
24 |
>>> Portage news item No 19 has the answer you're looking for. |
25 |
>> |
26 |
>> No, it has not. |
27 |
>> |
28 |
>> As I have already written, I have libav USE flag in my /etc/portage/make.conf |
29 |
>> and still portage wants to merge media-video/ffmpeg |
30 |
>> |
31 |
>>>> eselect news read 19 |
32 |
>>>> 2015-04-16-ffmpeg-default |
33 |
>>>> Title FFmpeg default |
34 |
>>>> Author Ben de Groot <yngwin@g.o> |
35 |
>>>> Posted 2015-04-16 |
36 |
>>>> Revision 1 |
37 |
>>>> |
38 |
>>>> Since the choice between ffmpeg and libav has been made more |
39 |
>>>> explicit, there has been a lot of discussion about what the |
40 |
>>>> default implementation should be. It can be concluded that |
41 |
>>>> media-video/ffmpeg has wider support, and would be somewhat |
42 |
>>>> more convenient for most end-users. |
43 |
>>>> |
44 |
>>>> For this reason the default implementation has been switched |
45 |
>>>> back from media-video/libav to media-video/ffmpeg by removing |
46 |
>>>> the libav useflag from the base profile. |
47 |
>>>> |
48 |
>>>> If the libav useflag is already globally enabled or disabled |
49 |
>>>> in /etc/portage/make.conf, then no further action is required. |
50 |
>>>> |
51 |
>>>> Users who implicitly relied on libav being enabled in their |
52 |
>>>> profile, and who wish to continue using libav, should enable |
53 |
>>>> USE=libav in their /etc/portage/make.conf file. |
54 |
>> |
55 |
>> P.S. Trying to find out which packages currently depend on ffmpeg, |
56 |
>> I get the following: |
57 |
>> |
58 |
>> $ equery depends ffmpeg |
59 |
>> * These packages depend on ffmpeg: |
60 |
>> app-misc/tracker-1.2.5 (ffmpeg ? >=virtual/ffmpeg-9) |
61 |
>> media-libs/gegl-0.2.0-r2 (!libav ? media-video/ffmpeg:0) |
62 |
>> media-plugins/alsa-plugins-1.0.28 (ffmpeg ? |
63 |
>> virtual/ffmpeg[abi_x86_32(-)?,abi_x86_64(-)?,abi_x86_x32(-)?,abi_mips_n32(-)?,abi_mips_n64(-)?,abi_mips_o32(-)?,abi_ppc_32(-)?,abi_ppc_64(-)?,abi_s390_32(-)?,abi_s390_64(-)?]) |
64 |
>> media-plugins/gst-plugins-ffmpeg-0.10.13_p201211-r3 (!libav ? |
65 |
>>> =media-video/ffmpeg-1.2.6-r1:0[abi_x86_32(-)?,abi_x86_64(-)?,abi_x86_x32(-)?,abi_mips_n32(-)?,abi_mips_n64(-)?,abi_mips_o32(-)?,abi_ppc_32(-)?,abi_ppc_64(-)?,abi_s390_32(-)?,abi_s390_64(-)?]) |
66 |
>> media-plugins/gst-plugins-libav-1.2.4-r1 (!libav ? |
67 |
>>> =media-video/ffmpeg-1.2.6-r1:0[abi_x86_32(-)?,abi_x86_64(-)?,abi_x86_x32(-)?,abi_mips_n32(-)?,abi_mips_n64(-)?,abi_mips_o32(-)?,abi_ppc_32(-)?,abi_ppc_64(-)?,abi_s390_32(-)?,abi_s390_64(-)?]) |
68 |
>> media-sound/sox-14.4.1 (ffmpeg ? >=virtual/ffmpeg-0.9) |
69 |
>> media-video/vlc-2.1.5-r1 (!libav ? media-video/ffmpeg:0) |
70 |
>> (!libav ? >=media-video/ffmpeg-1.2:0) |
71 |
>> (!libav ? media-video/ffmpeg:0[vaapi]) |
72 |
>> virtual/ffmpeg-9-r1 |
73 |
>> (>=media-video/ffmpeg-1.2.6-r1:0[abi_x86_32(-)?,abi_x86_64(-)?,abi_x86_x32(-)?,abi_mips_n32(-)?,abi_mips_n64(-)?,abi_mips_o32(-)?,abi_ppc_32(-)?,abi_ppc_64(-)?,abi_s390_32(-)?,abi_s390_64(-)?,X?,encode?,gsm?,jpeg2k?,mp3?,opus?,sdl?,speex?,theora?,threads?,truetype?,vaapi?,vdpau?,x264?]) |
74 |
>> |
75 |
>> Interestingly enouth, when I try to find out why the tracker package |
76 |
>> needs ffmpeg, |
77 |
>> I get the following: |
78 |
>> |
79 |
>> $ equery uses tracker |
80 |
>> [ Legend : U - final flag setting for installation] |
81 |
>> [ : I - package is installed with flag ] |
82 |
>> [ Colors : set, unset ] |
83 |
>> * Found these USE flags for app-misc/tracker-1.2.5: |
84 |
>> U I |
85 |
>> - - cue : Enable cue sheet parsing |
86 |
>> + + exif : Add support for reading EXIF headers from |
87 |
>> JPEG and TIFF images |
88 |
>> - - ffmpeg : Enable ffmpeg/libav-based audio/video codec support |
89 |
>> - - firefox-bookmarks : Install bookmark data miner plugin for |
90 |
>> www-client/firefox and www-client/firefox-bin |
91 |
>> + + flac : Add support for FLAC: Free Lossless Audio Codec |
92 |
>> + + gif : Add GIF image support |
93 |
>> - - gsf : Enable gnome-extra/libgsf based data |
94 |
>> extractor and for ODT. |
95 |
>> + + gstreamer : Add support for media-libs/gstreamer (Streaming media) |
96 |
>> + + gtk : Add support for x11-libs/gtk+ (The GIMP Toolkit) |
97 |
>> - - iptc : Enable extraction of IPTC data from pictures |
98 |
>> + + iso : Enable extraction of metadata from ISO disk images |
99 |
>> + + jpeg : Add JPEG image support |
100 |
>> + + miner-fs : Enable tracker-miner-fs (required for |
101 |
>> filesystem indexing) |
102 |
>> + + mp3 : Add support for reading mp3 files |
103 |
>> + + nautilus : Enable tracker to integrate with |
104 |
>> gnome-base/nautilus by providing entries in its context menu |
105 |
>> - - networkmanager : Enable net-misc/networkmanager support |
106 |
>> + + pdf : Add general support for PDF (Portable |
107 |
>> Document Format), this replaces the pdflib and cpdflib flags |
108 |
>> - - playlist : Add support for playlists |
109 |
>> - - rss : Enable support for RSS feeds |
110 |
>> - - test : Workaround to pull in packages needed to run |
111 |
>> with FEATURES=test. Portage-2.1.2 handles this internally, so don't |
112 |
>> set it in |
113 |
>> make.conf/package.use anymore |
114 |
>> - - thunderbird : Install email data miner plugin for |
115 |
>> mail-client/thunderbird and mail-client/thunderbird-bin |
116 |
>> + + tiff : Add support for the TIFF image format |
117 |
>> - - upnp-av : Enable UPnP audio/video streaming support |
118 |
>> + + upower : Enable power management support |
119 |
>> + + vorbis : Add support for the OggVorbis audio codec |
120 |
>> + + xml : Add support for XML files |
121 |
>> - - xmp : Enable support for Extensible Metadata |
122 |
>> Platform (Adobe XMP) |
123 |
>> - - xps : Add support for XPS file format through |
124 |
>> app-text/libgxps. |
125 |
>> |
126 |
>> |
127 |
>> That, in my view, means that the tracker package really should not |
128 |
>> demand ffmpeg. |
129 |
>> |
130 |
> |
131 |
> |
132 |
> Just checking something. |
133 |
> |
134 |
> app-misc/tracker does NOT depends on ffmpeg. It depends on |
135 |
> virtual/ffmpeg, which libav satisfies. I think you are chasing a red |
136 |
> haerring with that one. |
137 |
> |
138 |
> Did you notice? |
139 |
|
140 |
Yes, you are right about the tracker package. |
141 |
|
142 |
However, portage wants to emerge media-video/ffmpeg-2.2.14 and |
143 |
|
144 |
$ equery depends media-video/ffmpeg-2.2.14 |
145 |
* These packages depend on media-video/ffmpeg-2.2.14: |
146 |
media-libs/gegl-0.2.0-r2 (!libav ? media-video/ffmpeg:0) |
147 |
media-plugins/gst-plugins-ffmpeg-0.10.13_p201211-r3 (!libav ? |
148 |
>=media-video/ffmpeg-1.2.6-r1:0[abi_x86_32(-)?,abi_x86_64(-)?,abi_x86_x32(-)?,abi_mips_n32(-)?,abi_mips_n64(-)?,abi_mips_o32(-)?,abi_ppc_32(-)?,abi_ppc_64(-)?,abi_s390_32(-)?,abi_s390_64(-)?]) |
149 |
media-plugins/gst-plugins-libav-1.2.4-r1 (!libav ? |
150 |
>=media-video/ffmpeg-1.2.6-r1:0[abi_x86_32(-)?,abi_x86_64(-)?,abi_x86_x32(-)?,abi_mips_n32(-)?,abi_mips_n64(-)?,abi_mips_o32(-)?,abi_ppc_32(-)?,abi_ppc_64(-)?,abi_s390_32(-)?,abi_s390_64(-)?]) |
151 |
media-video/vlc-2.1.5-r1 (!libav ? media-video/ffmpeg:0) |
152 |
(!libav ? >=media-video/ffmpeg-1.2:0) |
153 |
(!libav ? media-video/ffmpeg:0[vaapi]) |
154 |
virtual/ffmpeg-9-r1 |
155 |
(>=media-video/ffmpeg-1.2.6-r1:0[abi_x86_32(-)?,abi_x86_64(-)?,abi_x86_x32(-)?,abi_mips_n32(-)?,abi_mips_n64(-)?,abi_mips_o32(-)?,abi_ppc_32(-)?,abi_ppc_64(-)?,abi_s390_32(-)?,abi_s390_64(-)?,X?,encode?,gsm?,jpeg2k?,mp3?,opus?,sdl?,speex?,theora?,threads?,truetype?,vaapi?,vdpau?,x264?]) |
156 |
|
157 |
So, more general questions remain relevant. |
158 |
|
159 |
P.S. I guess that the situation has something to do with the fact |
160 |
that I have a multilib profile (on amd64) and have chosen |
161 |
to enable abi_x86_32 on per package base. |
162 |
|
163 |
Probably, after portage-tree update, portage cannot find the |
164 |
needed x86_32 libraries and decides to emerge media-video/ffmpeg |
165 |
instead. |
166 |
|
167 |
So, if I get no better suggestions, I will enable abi_x86_32 globally |
168 |
and try to update the world once more. |
169 |
|
170 |
If that will not work, I will remove the libav USE flag from |
171 |
/etc/portage/make.conf and try to update the world for the last time. |
172 |
|
173 |
Will report about the results later. |