234157 – sys-apps/portage: setting BUILD_PREFIX does not work

Bug 234157 - sys-apps/portage: setting BUILD_PREFIX does not work

Summary: sys-apps/portage: setting BUILD_PREFIX does not work

Status:	RESOLVED FIXED

Alias:	None

Product:	Portage Development
Classification:	Unclassified
Component:	Core (show other bugs)
Hardware:	All Linux

Importance:	High normal (vote)
Assignee:	Portage team

URL:
Whiteboard:
Keywords:	InVCS

Depends on:
Blocks:	210077 216231
	Show dependency tree

Reported:	2008-08-07 08:12 UTC by Stephan Springer
Modified:	2008-12-05 02:49 UTC (History)
CC List:	0 users

See Also:
Package list:
Runtime testing required:	---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.

Description Stephan Springer 2008-08-07 08:12:28 UTC

The man-page make.conf(5) as well as several places in the Wiki and the online documentation state that I can set BUILD_PREFIX to some directory to override the default "${PORTAGE_TMPDIR}/portage".  But that doesn't work, such a setting is simply ignored, regardless of whether I set it in /etc/make.conf or in the environment.  All I can do is change PORTAGE_TMPDIR, but that changes more than I want.

I guess the reason is that the value is just hardcoded in line 3919 of /usr/lib64/portage/pym/portage.py.  So either fix it there or change all the documentaion, please.

I'm currently using sys-apps/portage-2.1.4.4 on amd64.

Comment 1 Zac Medico gentoo-dev

2008-08-09 20:27:52 UTC

Thanks, I've removed it from the man page for the time being since it's not intended to be configurable.

Comment 2 Zac Medico gentoo-dev

2008-08-10 13:23:10 UTC

This is released in 2.2_rc7.