27159 – Fixing GNUstep access violations correctly

Bug 27159 - Fixing GNUstep access violations correctly

Summary: Fixing GNUstep access violations correctly

Status:	RESOLVED TEST-REQUEST

Alias:	None

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

Importance:	High blocker (vote)
Assignee:	Nick Hadaway

URL:
Whiteboard:
Keywords:

Depends on:
Blocks:

Reported:	2003-08-22 20:21 UTC by Zhen Lin
Modified:	2003-12-04 07:41 UTC (History)
CC List:	0 users

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

Attachments
gnustep.eclass 1.2.2 (gnustep.eclass,6.07 KB, text/plain) 2003-08-22 22:07 UTC, Zhen Lin	Details
View All 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 Zhen Lin 2003-08-22 20:21:36 UTC

Instead of hardcoding /root/GNUstep into the sandbox parameters, I've decided to
find out what GNUstep thinks is the home directory at runtime, and add that to
the sandbox parameters.

I found it quite interesting really... Under userpriv, HOME is set to
/var/tmp/portage/home; but, GNUstep insists that HOME is /root...

Comment 1 Zhen Lin 2003-08-22 22:07:50 UTC

Created attachment 16491 [details]
gnustep.eclass 1.2.2

Various improvements here and there, including un-sandboxing of the correct
GNUstep directories.

Also vastly improved is the autodetection of the source directory

Comment 2 Andrew Cooks (RETIRED) gentoo-dev

2003-12-04 07:41:31 UTC

This bug has been inactive for a long time. If I understand the version numbers correctly, we're currently at 1.6.0. Has the problem been fixed?

I'm resolving this as a TEST_REQUEST. Please reopen if the problem persists.