The v0.10.0 ebuild fails to update the pmk.conf due to lack of quoting. Failure to correctly set the prefix breaks external usage, and even the pmk tools themselves. A simple example would be pmkpc: ~/test $ pmkpc --cflags pango Error : cannot open '/usr/local/lib/pkgconfig' directory : No such file or directory. Error : 'pango-config' not found. There is an ugly, but almost usable workaround for this specific case: ~/test $ PKG_CONFIG_PATH=/usr/lib/pkgconfig/ pmkpc --cflags pango Error : cannot open '/usr/local/lib/pkgconfig' directory : No such file or directory. -I/usr/include/pango-1.0 -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include and the general case can be mostly avoided with a local pmk.conf and the -o option to pmk. The patch fixes the pmksetup call, and removes the output redirection which masks the failure. One imagines that is the reason this bug wasn't caught when the package was bumped.
Created attachment 113321 [details, diff] pmk-fix_pmksetup_calls.patch
Thank you James. I bumped the version to 0.10.1 and added your fix with some minor modifications.
