4836 – Portage doesn't always follow PORTDIR

Bug 4836 - Portage doesn't always follow PORTDIR

Summary: Portage doesn't always follow PORTDIR

Status:	RESOLVED FIXED

Alias:	None

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

Importance:	High minor (vote)
Assignee:	Daniel Robbins (RETIRED)

URL:
Whiteboard:
Keywords:

Depends on:
Blocks:

Reported:	2002-07-10 19:44 UTC by Mark A. Wicks
Modified:	2011-10-30 22:17 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 Mark A. Wicks 2002-07-10 19:44:35 UTC

The path '/usr/portage' is hard-coded into several of the scripts in
/usr/lib/portage.  This means that the PORTDIR environment variable
isn't consistently honored by portage.  For example, "emerge search"
won't follow PORTDIR.  I discovered this when I ran our of space and had to move
my portage tree.  I realize that a symlink will work around this,
so it's a minor bug.  But shouldn't I should be able to move my portage tree or
have multiple trees without using symlinks? And besides, hard-coded paths in
multiple places are a bad idea.

Comment 1 Daniel Robbins (RETIRED) gentoo-dev

2002-07-11 02:23:48 UTC

Will be fixed in portage 2.0.12; thanks :)

Comment 2 Andrzej Sawula 2004-07-09 04:14:21 UTC

I am afraid this bug raised its ugly head again. I ran into the exact same symptoms after moving the /usr/portage directory to another partition and setting PORTDIR accordingly. portage version was 2.0.50-r8. Making the symlink from /usr/portage to the new location solved the problem, of course...