Running euse -i <flag> with an empty /etc/portage/package.use/ directory I get a lot of the following errors: cat: '/etc/portage/package.use/*': No such file or directory For example: $ euse -i offensive global use flags (searching: offensive) ************************************************************ [- ] offensive - Enable potentially offensive items in packages local use flags (searching: offensive) ************************************************************ cat: '/etc/portage/package.use/*': No such file or directory [- ] offensive app-admin/sudo: Let sudo print insults when the user types the wrong password [- ] 1.8.28_p1-r2 [gentoo] [- ] 1.8.29-r2 [gentoo] [- ] 1.8.30_beta1 [gentoo] [- ] 9999 [gentoo] cat: '/etc/portage/package.use/*': No such file or directory [- ] offensive games-fps/eduke32: Install the Duke Nukem 3D XXX Pack. [- ] 20190919.8133-r1 [gentoo] cat: '/etc/portage/package.use/*': No such file or directory [- ] offensive sci-chemistry/gromacs: Enable gromacs partly offensive quotes [+ B] (0/2018.7) 2018.7 [gentoo] [+ B] (0/2018.8) 2018.8 [gentoo] [+ B] (0/2018.9999) 2018.9999 [gentoo] [+ B] (0/2019.2) 2019.2 [gentoo] [+ B] (0/2019.3) 2019.3 [gentoo] [+ B] (0/2019.4) 2019.4 [gentoo] [+ B] (0/2019.9999) 2019.9999 [gentoo] [+ B] (0/2020_beta1) 2020_beta1 [gentoo] [+ B] (0/9999) 9999 [gentoo] These errors occur when the /etc/portage/package.use/ directory is empty, which is the default case since the stage3 tarball starts you off that way: $ tar tpf stage3-amd64-20191204T214502Z.tar.xz | grep '/etc/portage/package.use' ./etc/portage/package.use/ $ I guess most people probably have a non-empty /etc/portage/package.use/ directory or use a /etc/portage/package.use file instead. But the fact that the default case is an empty directory, I figured a fix should be applied. I have opened a pull request with a potential fix: https://github.com/gentoo/gentoolkit/pull/8
