Emerging dev-tex/xcolor-2.11 yields: * QA Notice: Symbolic link /usr/share/texmf-site/doc/latex/xcolor/xcolor2.pdf points to /usr/share/doc/xcolor-2.11/xcolor2.pdf which does not exist. * QA Notice: Symbolic link /usr/share/texmf-site/doc/latex/xcolor/xcolor4.dvi points to /usr/share/doc/xcolor-2.11/xcolor4.dvi which does not exist. * QA Notice: Symbolic link /usr/share/texmf-site/doc/latex/xcolor/xcolor.pdf points to /usr/share/doc/xcolor-2.11/xcolor.pdf which does not exist. * QA Notice: Symbolic link /usr/share/texmf-site/doc/latex/xcolor/xcolor1.dvi points to /usr/share/doc/xcolor-2.11/xcolor1.dvi which does not exist. * QA Notice: Symbolic link /usr/share/texmf-site/doc/latex/xcolor/xcolor3.dvi points to /usr/share/doc/xcolor-2.11/xcolor3.dvi which does not exist. This is most likely due to my FEATURES=nodoc. Reproducible: Always
Created attachment 351210 [details] emerge --info
We couldn't possibly begin to take into account the effects of sys-apps/portage features (such as FEATURES=nodoc / INSTALL_MASK and so on) on the things ebuilds actually install.