The lafilefixer outputs and einfo that suggests I run a command. It lists thousands of la files. I think the output of einfo should contain the command used to create that list of files. I'll attach a patch for the ebuild. Example of ebuild's einfo output: `` * If you want to fix all your .la files, something like this will work: * lafilefixer /usr/lib/gcc/x86_64-pc-linux-gnu/3.4.6/32/libffi.la * /usr/lib/gcc/x86_64-pc-linux-gnu/3.4.6/32/libobjc.la * /usr/lib/gcc/x86_64-pc-linux-gnu/3.4.6/32/libstdc++.la * /usr/lib/gcc/x86_64-pc-linux-gnu/3.4.6/32/libsupc++.la * /usr/lib/gcc/x86_64-pc-linux-gnu/3.4.6/32/libg2c.la'' ... Corresponding desired output: `` * If you want to fix all your .la files, something like this will work: * lafilefixer $(find /usr/lib* -name '*.la' -type f)'' P.S., I was refered to dev-util/lafilefixer by http://blog.flameeyes.eu/2009/04/18/some-details-about-our-old-friends-the-la-files#comment-5236 . I'm probably breaking rules by giving CC to loki_val, but he asked for patches in his einfo...
Created attachment 188924 [details, diff] causes the ebuild to avoid expanding $() This change is too self explanatory for a patch ;-)
+ 20 Apr 2009; Peter Alfredsen <loki_val@gentoo.org> lafilefixer-0.0.1: + Properly escape. Thanks to Nathan Brink <ohnobinki@ohnopublishing.net> of + bug 266817 for beating some sense into me with a shovel. +
