Summary: | no way to request binaries not to get strip'ed from in an ebuild | ||
---|---|---|---|
Product: | Portage Development | Reporter: | Sandy McArthur <Sandy> |
Component: | Unclassified | Assignee: | Geert Bevin <gbevin> |
Status: | RESOLVED FIXED | ||
Severity: | enhancement | CC: | hallski |
Priority: | Low | ||
Version: | unspecified | ||
Hardware: | x86 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Sandy McArthur
2002-01-24 03:22:33 UTC
I'm not sure if there are. Earlier if you set DEBUG="yes" it didn't strip. but that is not on a per-package level. The fix is to make sure that all our "do" commands and "prep" commands respect "DEBUG". I think this may be the case, but I'm assigning to Bevin to check for sure. In the meantime, try setting DEBUG="yes" and see if that fixes it and if so post a follow-up to this bug. Good news: putting `export DEBUG="yes"` in you ebuild will skip the strip process. I was a little worried that exporting DEBUG would cause any packages merged with the one I didn't want stripped would not get striped either but it seems DEBUG doesn't leak into other ebuild scripts. Note: Simply putting DEBUG="yes" with out the export did not prevent stripping. |