Summary: | isolated-functions.sh has wrong location for eapi.sh | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Justin Lecher (RETIRED) <jlec> |
Component: | Current packages | Assignee: | Portage team <dev-portage> |
Status: | RESOLVED INVALID | ||
Severity: | normal | ||
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Justin Lecher (RETIRED)
2014-09-18 06:41:16 UTC
From NEWS: portage-2.2.13 ------------- * PORTAGE_{BIN,PYM}_PATH variables. If you want to call internal portage tools, you need to query PORTAGE_BIN_PATH and PORTAGE_PYM_PATH, use them and re-export them. /usr/lib64/portage/python2.7/isolated-functions.sh: source "${PORTAGE_BIN_PATH:-/usr/lib/portage/bin}/eapi.sh" but eapi.sh /usr/lib/portage/python2.7/eapi.sh so it should be source "${PORTAGE_BIN_PATH:-/usr/lib/portage/python2.7/}/eapi.sh" (In reply to Justin Lecher from comment #2) > /usr/lib64/portage/python2.7/isolated-functions.sh: > > source "${PORTAGE_BIN_PATH:-/usr/lib/portage/bin}/eapi.sh" > > but eapi.sh > > /usr/lib/portage/python2.7/eapi.sh > > so it should be > > source "${PORTAGE_BIN_PATH:-/usr/lib/portage/python2.7/}/eapi.sh" No, it should be: source "${PORTAGE_BIN_PATH}/eapi.sh" But we didn't fix all of it yet since it's mostly irrelevant. |