1/ See Bug 117057 for broken deps (the ebuild doesn't state what it needs, but just tons of stuff that will make it bomb out when installed). 2/ pkg_setup() plain doesn't make any sense. It checks whether the above mentioned blockers are installed (!?) and if not, it removes some files supposedly installed by them - what's the point in this I simply fail to see. Those ebuilds are already all blocked, so the user if forced to unmerge them before emerging this crazy thing. 3/ Tarballs don't belong to ${FILESDIR}, additionally they are not used in those ebuilds at all - there's just some commented-out stuff doing 'tar -xjf' in src_install (!?). 4/ Why does this depend on an uspecified version of app-shells/bash goes beyond me. Huh...
Ha, good luck with that. The maintainer's usual response to complains for the last years has always been that there have been no complains so everything is all right. (For his last stunt, compare bug 29388 comment 171 and his response in bug 29388 comment 178) Not only does he refuse to add basic error checks, in addidtion to 1..4 above the motif-config ebuild is prone to other problems due to non-robust shell constructs. See also bug 117458 comment 6 ... 14 for reasons why the whole motif-config concept can't work as advertised (some of the more patient motif experts in here will have more detailed information, although I think they may have given up on the issue and moved on a long time ago)
Created attachment 97018 [details] proof everything is fine. motif support in gentoo is better then anywhere else. anyway, here is the picture of a banana.
*** Bug 159143 has been marked as a duplicate of this bug. ***
If you have issues with >=motif-config-0.10-r2 then file a *new* bug. Thanks.
