2011/2/22 Jeff Johnson <n3...@mac.com>: > Note that there's literally no frigging reason known > to the human race why RPM needs to supply absolute paths > to every bleeping uglix executable on all possible > platfomrs "protably" in spite of FHS and linux vendor > induced rearrangements. > > The proper (and entirely consistent with uglix tool box paradigms) > is to use PATH and write build recipes assuming that PATH is set > correctly. > > Its also not too hard to generate the macro settings dynamically, > using which and some simple echo's. Its just *INSANE* to > track all these paths into @rpm5.org CVS with vendor peculier > "Have it your own way!" configuration delivered as drop-in > through One Size Fits All Uglixes (with a whopping amount > of AutoFu pain). > > There's only a handful of toolchain related (I'm talking > CPU-VENDOR-OS-GNU-gcc > here) that are usefully configured in macros. > > grep == grep *shrug* > > But you might want to noodle up the script using > which/echo that dynamically generates a list > of absolute paths to executables that you deem > important instead. I personally try avoid use of these macros myself, but there's always someone who will compulsively use them, and for those the notion of the paths of those being broken are rather hard to contend.. ;)
-- Regards, Per Øyvind ______________________________________________________________________ RPM Package Manager http://rpm5.org Developer Communication List rpm-devel@rpm5.org
