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