| 1 |
> USE="-cups bindist fontconfig X a52 aac acpi avx avx2 asf x264 |
| 2 |
> bash-completion -bluetooth branding bzip2 java -cairo crypt curl doc |
| 3 |
> -emacs exif ffmpeg ftp gimp gif gpm gzip hddtemp -ipv6 -kde -gnome |
| 4 |
> -gnome-keyring -emacs -gtk -qt3 -gt4 -qt5 fat ntfs opengl truetype |
| 5 |
> xorg jack jpeg jpeg2k matroska nmap mmx mp3 mp4 mpeg xv xcomposite |
| 6 |
> multilib png pdf spell ssh posix pulseaudio rss sse sse2 sse3 sse4_1 |
| 7 |
> ssl systemd svg threads tiff -xemacs -zsh-completion" |
| 8 |
|
| 9 |
You will want to reconsider your enabling of bindist and doc. |
| 10 |
|
| 11 |
bindist is enabled by default in stage3 tarballs due to a bug [1] in |
| 12 |
catalyst. It is known to cause numerous issues, and is not useful for |
| 13 |
end-user systems. |
| 14 |
|
| 15 |
doc generally enables generation of documentation end-users will not |
| 16 |
require, like developer docs and complete project websites for offline |
| 17 |
reference. If you find yourself requiring documentation for a specific |
| 18 |
package, you are better off enabling the doc useflag for that specific |
| 19 |
package in /etc/portage/package.use . Doc generation pulls in many |
| 20 |
otherwise unneccesary dependencies in order to generate the |
| 21 |
documentation, and is known to cause many circular dependencies due to |
| 22 |
eg. documentation generating software needing itself to generate its own |
| 23 |
documentation. |
| 24 |
|
| 25 |
A general piece of advice: You might not want to set a long string of |
| 26 |
USE flags globally immediately in your first install, rather pick a |
| 27 |
profile and adjust flags when/if the defaults don't suit you. Always |
| 28 |
use '-a' with emerge to review the use flags on packages to be |
| 29 |
installed. |
| 30 |
|
| 31 |
1: https://bugs.gentoo.org/473332 |
| 32 |
|
| 33 |
-- |
| 34 |
eroen |
Archives