52830 – Perforce /etc/env.d environment variables are wrong / not required

Bug 52830 - Perforce /etc/env.d environment variables are wrong / not required

Summary: Perforce /etc/env.d environment variables are wrong / not required

Status:	VERIFIED TEST-REQUEST

Alias:	None

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

Importance:	High trivial (vote)
Assignee:	Stuart Herbert (RETIRED)

URL:
Whiteboard:
Keywords:

Depends on:
Blocks:

Reported:	2004-06-02 16:44 UTC by Steve Pole
Modified:	2005-02-17 03:23 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 Steve Pole 2004-06-02 16:44:31 UTC

after emerging the Perforce scm server and its tools onto an x86 2004.1 gentoo system using 'emerge perforce', the environment variables set in /etc/env.d/50perforce IMO are nonsense:
PATH=/opt/perforce/bin
ROOTPATH=/opt/perforce/bin;/opt/perforce/sbin
MANPATH=/opt/perforce/man

p4d, p4web & p4ftpd are installed to /usr/sbin, so ROOTPATH should point there, shouldn't it ? The man pages are stored in /usr/share/man, so MANPATH doesn't even have to be modified.



Reproducible: Always
Steps to Reproduce:
1. do 'emerge perforce'
2. look at output of emerge
3. compare /etc/env.d/50perforce with what's on your harddrive

Actual Results:  
I submitted a bug report.


happy to supply that on request

Comment 1 Stuart Herbert (RETIRED) gentoo-dev

2004-06-26 15:00:08 UTC

Fixed in -r1.

Comment 2 Stuart Herbert (RETIRED) gentoo-dev

2005-02-17 03:23:15 UTC

Closing old bug.