Bug 251829
| Summary: | Mk/bsd.port.mk: .info files install to GNU_CONFIGURE_PREFIX, but packaged from PREFIX | ||
|---|---|---|---|
| Product: | Ports & Packages | Reporter: | Damjan Jovanovic <damjan.jov> |
| Component: | Ports Framework | Assignee: | Port Management Team <portmgr> |
| Status: | New --- | ||
| Severity: | Affects Some People | CC: | portmgr, ports-bugs, tcberner |
| Priority: | --- | Flags: | linimon:
maintainer-feedback?
(portmgr) |
| Version: | Latest | ||
| Hardware: | Any | ||
| OS: | Any | ||
Moin moin Do you have a port where this is an issue, and is it still relevant? mfg Tobias |
When GNU_CONFIGURE_PREFIX and PREFIX differ, .info files are installed to GNU_CONFIGURE_PREFIX: _LATE_CONFIGURE_ARGS="$${_LATE_CONFIGURE_ARGS} --infodir=${GNU_CONFIGURE_PREFIX}/${INFO_PATH}/${INFO_SUBDIR}" ; \ yet packaged from PREFIX instead: add-plist-info: .for i in ${INFO} @${LS} ${STAGEDIR}${PREFIX}/${INFO_PATH}/$i.info* | ${SED} -e s:${STAGEDIR}:@info\ :g >> ${TMPPLIST} .endfor This will not work, no matter what the value of INFO_PATH is. Neither can a custom --infordir be set for LATE_CONFIGURE_ARGS.