On Friday 27 January 2006 03:17, Paul de Vrieze wrote: > On Thursday 26 January 2006 19:53, Mike Frysinger wrote: > > On Thursday 26 January 2006 11:06, Paul de Vrieze wrote: > > > Sometimes when calling the strip option > > > of install. A strip wrapper prevents this broken behaviour once and for > > > all. It could even be written to show a big fat warning. > > > > i know ... it isnt uncommon to see like `install -s` or `$(STRIP)` in > > packages and those need to be removed > > > > while this is a neat idea (catching those people who do `install -s`), > > i'm not sure it'd work as there isnt a clean way to detect whether it's > > the package calling `strip` or the ebuild/portage ... you could try > > passing info via an env var, but that's no fun :) > > Well, portage uses prepstrip to do stripping. As such this prepstrip script > could take care not to use the wrong strip binary. Shouldn't be hard to do > even without hardcoding the path to the strip binary.
it does ... but in case it cant find a fully qualified strip binary (CHOST-strip), it will fall back to plain old `strip` > For ebuilds calling strip, I see no reason why they would. If at some point > it is found necessary, it would be easy to have an estrip command to do > this. even ebuilds shouldnt be calling strip they can call `prepstrip <files or dirs>` -mike -- gentoo-dev@gentoo.org mailing list
