Hello!
Isn't the 'strip' part of binutils? I think only solution would be to set conflict between binutils2.13 rpm and 2.18 rpm which is probably not good solution at all.
If the package has the same name it's automatically an update of the old package. Otherwise you must take care that the new gcc chain only use the new tools. From the things I heard on the mailinglist, are the binutils 2.18 stable and work together with gcc 2.95? If yes we can easily update just the binutils. Then there is no conflict at all :-)
Regards, Frank -- ATARI FALCON 060 // MILAN 060 ----------------------------- http://sparemint.org/ e-Mail: fnaumann@boerde.de