Summary: | portage 2.1: ebegin/eend messed up output | ||
---|---|---|---|
Product: | Portage Development | Reporter: | Harald van Dijk (RETIRED) <truedfx> |
Component: | Core | Assignee: | Portage team <dev-portage> |
Status: | RESOLVED FIXED | ||
Severity: | normal | Keywords: | InVCS, REGRESSION |
Priority: | High | ||
Version: | 2.1 | ||
Hardware: | All | ||
OS: | Linux | ||
See Also: | https://bugs.gentoo.org/show_bug.cgi?id=920327 | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Bug Depends on: | |||
Bug Blocks: | 115839 |
Description
Harald van Dijk (RETIRED)
2005-12-30 04:57:14 UTC
baselayout issue (I think). ebegin/eend are defined in /sbin/functions.sh. They really shouldn't be used from ebuilds though. > ebegin/eend are defined in /sbin/functions.sh
For ebuilds, they're defined in /usr/lib/portage/bin/isolated-functions.sh, actually, which is why it only fails from ebuilds/eclasses.
True.. using ebegin/eend in ebuilds/eclasses is fine, and noted here, they are broken in portage, not baselayout fixed by punting the current versions and re-importing the ones from baselayout Released in 2.1_pre4 |