When installing mtx, it sets an environment variable in /etc/env.d/95mtx, which is TAPE=/dev/tapes/tape0/generic. This influences tar not to use it's standard input when no archive is specified when extracting, but the file mentioned in this TAPE enviroment variable. All of a sudden, some ebuilds fail to unpack their sources (at least blackdown-jdk, took me weeks to find this), because they use "cat archive | tar -jxp". Suggested fix: Let tar always use it's standard input for reading archives, not depending on the TAPE environment, or of course let all ebuilds specify where to extract the archive from...
i just looked through the two ebuilds in portage and they dont seem to install an env.d entry anymore ... if you `emerge mtx` and then do `qpkg -f /etc/env.d/95mtx`, what do you see ?
Indeed, the new mtx doesn't install an environment file anymore. So the solution for the record: emerge sync, emerge mtx :-)
