54412 – portage-2.0.50-r8.ebuild is non-FHS compliant

Bug 54412 - portage-2.0.50-r8.ebuild is non-FHS compliant

Summary: portage-2.0.50-r8.ebuild is non-FHS compliant

Status:	RESOLVED WORKSFORME

Alias:	None

Product:	Gentoo Linux
Classification:	Unclassified
Component:	New packages (show other bugs)
Hardware:	x86 Linux

Importance:	High normal (vote)
Assignee:	Portage team

URL:
Whiteboard:
Keywords:

Depends on:
Blocks:

Reported:	2004-06-19 05:39 UTC by dorian33
Modified:	2004-06-21 01:48 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 dorian33 2004-06-19 05:39:47 UTC

It is impossible to emerge the portage package when /var is mounted with 'noexec' option. The reason is /var/tmp/portage/portage-2.0.50-r8/work/portage-2.0.50-r8/src/sandbox-1.1/create-localdecls script.

Reproducible: Always
Steps to Reproduce:
1. mount /var with 'noexec'
2.
3.

Comment 1 Nicholas Jones (RETIRED) gentoo-dev

2004-06-21 01:48:58 UTC

You'd have a lot more problems than just portage...
You could never run a 'configure' in this case...
Nor could you run test cases for binaries and such.

You can move this directory with the PORTAGE_TMPDIR.