Summary: | [Future EAPI] fix econf() --libdir inconsistency | ||
---|---|---|---|
Product: | Portage Development | Reporter: | RB <aoz.syn> |
Component: | Enhancement/Feature Requests | Assignee: | Package Manager Specification <pms> |
Status: | RESOLVED NEEDINFO | ||
Severity: | normal | ||
Priority: | High | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
See Also: | https://bugs.gentoo.org/show_bug.cgi?id=466732 | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Bug Depends on: | |||
Bug Blocks: | 174380, 466732, 468810 |
Description
RB
2008-09-30 20:03:49 UTC
Could you point to a specific package? Looking at the PMS, econf respects '--prefix' here (not sure why not --exec-prefix as well...). I'd say that should be 'good enough' to solve this -- request the packages that install to / specify --prefix explicitly. Let me check, it's demonstrably been years since I poked at this. I do know this was from when I was packaging things myself and had discussed this with someone on #g-portage who asked me to submit this bug. Thanks to Anthony for finding these bugs, saves me having to spin back up and figure out where I had been (and what machine I was working on) 5 years ago. This is Algorithm 9 in PMS: http://dev.gentoo.org/~ulm/pms/5/pms.html#x1-135002r9 I don't see why it would be inconsistent. If the ABI variable is set, then --libdir=${prefix}/${libdir} is passed to configure. ${prefix} is equal to ${EPREFIX}/usr unless the caller overrides it with --prefix. If ABI is not set, then libdir should be the default, which according to GNU coding standards is $(exec_prefix)/lib. If the package uses something different then it should be fixed upstream. No progress. Closing. |