>I think it was only really intended for scanning %post/%postun-type >scriptlets, which are generally very easy to parse. I can think of several ways to use that facility besides just those scriptlets. If the ability to resolve internal function calls vs external executables was solid, we could easily augment rpmbuild. I have updated sh2rpms so that it works around problem #3 I mentioned before. If it finds a known interpreter, it simply makes the interpreter its requirement. You can get the updated copy from: http://www.web-insights.net/sh2rpms I also uploaded the script that searches for shell script problems. It has been corrected to handle interpreters by skipping over those files. Give it a try like so: ./find_sh4errors /usr/bin Download from here: http://www.web-insights.net/find_sh4errors It could also easily be included into rpmbuild where you pass it the build root directory. Happy bug hunting... >I think at one point there was even a hook in rpm to make use of it -- whether >that is still around but disabled, or gone altogether, I don't know. I thought it was just a matter of clipping into a macro. I haven't taken that step yet, but I thought it was easy to do from various things I've read. -Steve Grubb __________________________________ Do you Yahoo!? Yahoo! Mail is new and improved - Check it out! http://promotions.yahoo.com/new_mail
