Mozilla man page gives wrong location of mozilla-bin

RESOLVED WONTFIX

Status

SeaMonkey
Build Config
RESOLVED WONTFIX
15 years ago
8 years ago

People

(Reporter: Aleksey Nogin, Unassigned)

Tracking

Firefox Tracking Flags

(Not tracked)

Details

(URL)

(Reporter)

Description

15 years ago
The Mozilla man page (see xpfe/bootstrap/mozilla.man.in) references
@libdir@/mozilla/mozilla-bin. Instead, it should refer to
@mozilla-five-home@/mozilla-bin.
(Reporter)

Updated

15 years ago
Depends on: 94220

Comment 1

14 years ago
Moving all of rudman's bugs to me, the new owner of Doc: User.
Assignee: rudman → rlk
QA Contact: rudman → stolenclover

Comment 2

14 years ago
Daniel, can you reassign this bug elsewhere? This has nothing to do with help
documentation. Maybe mozilla.org -> Webmaster?
(Reporter)

Comment 3

14 years ago
What's a man page if not a user help documentation? And it definitely has
nothing to do with the mozilla.org web site!

Comment 4

14 years ago
-> owner and QA of bug 94220
Assignee: rlk → cls
Severity: trivial → normal
Component: User → Build Config
Product: Documentation → Browser
QA Contact: stolenclover → granrosej
Version: unspecified → Trunk

Comment 5

14 years ago
Fwiw, the manpage references the default location chosen when using 'make
install'.   A note should probably be added that MOZILLA_FIVE_HOME can be used
to override that location.
Assignee: cls → leaf

Updated

13 years ago
Assignee: leaf → cmp
Product: Browser → Seamonkey

Comment 6

12 years ago
Mass reassign of open bugs for chase@mozilla.org to build@mozilla-org.bugs.
Assignee: chase → build

Comment 7

11 years ago
Mass re-assign of bugs that aren't on the build team radar, so bugs assigned to build@mozilla-org.bugs reflects reality.

If there is a bug you really think we need to be looking at, please *email* build@mozilla.org with a bug number and explanation.
Assignee: build → nobody

Comment 8

8 years ago
We can't know where people specifically install it, we can just use our default location there. Nothing we specifically can fix here.
Status: NEW → RESOLVED
Last Resolved: 8 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.