%% head -n1 /usr/share/getopt/getopt-test.tcsh #!/bin/tcsh %% qfile getopt-test.tcsh sys-apps/util-linux (/usr/share/getopt/getopt-test.tcsh) [ebuild R ] sys-apps/util-linux-2.14.2 USE="unicode -crypt -loop-aes -nls -old-linux (-selinux) -slang (-uclibc)" 0 k
It is actually all of these: %% qfile * sys-apps/util-linux (/usr/share/getopt/getopt-test.tcsh) sys-apps/util-linux (/usr/share/getopt/getopt-test.bash) sys-apps/util-linux (/usr/share/getopt/getopt-parse.tcsh) sys-apps/util-linux (/usr/share/getopt/getopt-parse.bash) and it is only a problem because they are executable. If portage installs executable files, then it should be able to run them, right?
sigh, obviously not the bash ones. My bad.
no, the installation of the files doesnt mean util-linux should require all of these shells. they arent used by util-linux; they're only there to let people writing custom code to import them. i.e. they're convenience helpers. i dont see any "tcsh" USE flag, and i dont see much point in adding one for these two small files that dont cause problems.