146879 – special env-update variables should not be hard coded

Bug 146879 - special env-update variables should not be hard coded

Summary: special env-update variables should not be hard coded

Status:	RESOLVED FIXED

Alias:	None

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

Importance:	High enhancement (vote)
Assignee:	Portage team

URL:	http://thread.gmane.org/gmane.linux.g...
Whiteboard:
Keywords:	InVCS

Depends on:
Blocks:	147007 149110
	Show dependency tree

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 Zac Medico gentoo-dev

2006-09-08 13:46:42 UTC

I'm not sure where we should keep these variables (profiles?), but having them hard coded in portage is certainly bad.

Comment 1 Zac Medico gentoo-dev

2006-09-09 12:44:18 UTC

Hmm, portage_const.INCREMENTALS is another one that we may want to define via the profiles.

Comment 2 Zac Medico gentoo-dev

2006-09-15 00:14:40 UTC

In svn r4452 I've added support for SPACE_SEPARATED and COLON_SEPARATED in /etc/env.d/ so that hard coded values are not required.

Comment 3 Zac Medico gentoo-dev

2006-09-15 20:30:58 UTC

This has been released in 2.1.2_pre1.