| Summary: | PRELINK_PATH variable hard-coded in ebuild, instead of using /etc/prelink_path.conf | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | Gavin <colonel_dolphin> |
| Component: | New packages | Assignee: | Stefan Jones (RETIRED) <cretin> |
| Status: | RESOLVED INVALID | ||
| Severity: | normal | ||
| Priority: | High | ||
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
emake is incorrect for test suite grep PRELINK_PATH /etc/env.d/* etc/env.d/60gstreamer-0.8:PRELINK_PATH_MASK=/usr/lib/gstreamer-0.8 /etc/env.d/60prelink:PRELINK_PATH_MASK="/lib/modules:/usr/lib/locale:/usr/lib/wine:/usr/lib/valgrind:*.la:*.png:*.py:*.pl:*.pm:*.sh:*.xml:*.xslt:*.a:*.js" /etc/env.d/60prelink:PRELINK_PATH="" So you can edit the files like any other default configuration files. Not sure what you mean about PRELINK_PATH hardcoded, etc-update and config-preotact in portage works? The make test does run is you add test to your FEATURES see bug #100147 for current errors! |
I've been maintaining my own prelink ebuild for over a year now, because the Gentoo stock prelink ebuild hard-codes PRELINK_PATH and does not run the testsuite that ships with prelink. It would be great if the stock Gentoo ebuild didn't hard code the variable (e.g. pull its value from somewhere in /etc) and applied the testsuite: cd ${S}/testsuite emake check Reproducible: Always Steps to Reproduce: 1. 2. 3.