The executables which should be installed in /usr/share/gutenprint are instead libtool's shell scripts. /usr/share/gutenprint/bjc-unprint: Bourne shell script text executable /usr/share/gutenprint/escp2-weavetest: Bourne shell script text executable /usr/share/gutenprint/pcl-unprint: Bourne shell script text executable /usr/share/gutenprint/run-weavetest: Bourne shell script text executable /usr/share/gutenprint/testdither: Bourne shell script text executable /usr/share/gutenprint/unprint: Bourne shell script text executable As an example, /usr/share/gutenprint/unprint starts out with: #! /bin/sh # unprint - temporary wrapper script for .libs/unprint # Generated by ltmain.sh - GNU libtool 1.5.24 (1.1220.2.455 2007/06/24 02:13:29) # # The unprint program cannot be directly executed until all the libtool # libraries that it depends on are installed. # # This wrapper script should never be moved out of the build directory. # If it is, it will not operate correctly. The ebuild uses this to install the executables which go in /usr/share/gutenprint: exeinto /usr/share/gutenprint doexe test/{unprint,pcl-unprint,bjc-unprint,parse-escp2,escp2-weavetest,run-testdither,run-weavetest,testdither} Hense the bug. I don't know whether the build process changed recently, ie whether that ebuild idiom used to work.
are these files actually used for anything? they appear to be part of the package's test suite.
