276384 - 1.7.5 linux install shell doesn't put directory where mozilla script looks

Status: RESOLVED EXPIRED

(SeaMonkey :: Installer, defect)

Description

[Joanna]

running the install as it came out of the box, mozilla got stuck in /usr/local,
but then the script it generates looks in /usr/local/lib/mozilla-1.7.5

This is annoying, and maybe terminally confusing to the underinformed.

By the way, I'm on suse and but nothing but mozilla is in /usr/local.  Most
stuff is in /opt, including the dist. of mozilla suse comes with.

Comment 1

[Andrew Schultz]

the script only uses /usr/local/lib/mozilla-1.7.5 if the script can't find it
(which should work fine.  Did it install to /usr/local/ or /usr/local/mozilla/?
 And then you're executing /usr/local/mozilla/mozilla?  Do you have
MOZILLA_FIVE_HOME set?

Comment 2

[Joanna]

(In reply to comment #1)
> the script only uses /usr/local/lib/mozilla-1.7.5 if the script can't find it
> (which should work fine.  Did it install to /usr/local/ or /usr/local/mozilla/?
>  And then you're executing /usr/local/mozilla/mozilla?  Do you have
> MOZILLA_FIVE_HOME set?

I think it went into /usr/local/mozilla -- I didn't change any defaults.  I
didn't have mozilla_five_home set.  I think I moved the shell to wherever suse
had had the old shell (I'm travelling now & on my mac and anyway wound up
backing out that upgrade so I can't really check.)  But the main thing was I
would have exected the shell to have had the pathnames it searched set to where
it installed the stuff, but in fact it had them set to a different path, but
still one that nothing I or suse did would have chosen.

Comment 3

[Andrew Schultz]

> I think I moved the shell to wherever suse had had the old shell

Don't do that.  The script looks for the rest of Mozilla in the same directory
where it's located.  If you want to put the mozilla script in the PATH, do this

ln -s /usr/local/mozilla/mozilla /some/other/dir/

the issue with the directory in the script is that it's generated at
compile-time, and then the user can pick any directory to install into.  So
depending on those matching is bad.  /usr/local/lib/mozilla-1.7.5 would be the
install directory if you did "make install" after building Mozilla.

resolving as INVALID -- this is not a Mozilla bug

Comment 4

[Joanna]

Oh come on.  It should be totally trivial to either get the path right instead
of off by one directory name or to make it produce an error that says not to
move the shell.  This is absolutely a bug, though only a trivial one in a shell
script.  why have paths in the damn thing at all if they are set to the wrong place?

This is merely a thing about professionalsim, I know I shouldn't be critical
since I'm not contributing code, but I honestly think your product is better
than this!

Comment 5

[Gervase Markham [:gerv]]

This is an automated message, with ID "auto-resolve01".

This bug has had no comments for a long time. Statistically, we have found that
bug reports that have not been confirmed by a second user after three months are
highly unlikely to be the source of a fix to the code.

While your input is very important to us, our resources are limited and so we
are asking for your help in focussing our efforts. If you can still reproduce
this problem in the latest version of the product (see below for how to obtain a
copy) or, for feature requests, if it's not present in the latest version and
you still believe we should implement it, please visit the URL of this bug
(given at the top of this mail) and add a comment to that effect, giving more
reproduction information if you have it.

If it is not a problem any longer, you need take no action. If this bug is not
changed in any way in the next two weeks, it will be automatically resolved.
Thank you for your help in this matter.

The latest beta releases can be obtained from:
Firefox:     http://www.mozilla.org/projects/firefox/
Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html
Seamonkey:   http://www.mozilla.org/projects/seamonkey/

Comment 6

[Gervase Markham [:gerv]]

This bug has been automatically resolved after a period of inactivity (see above
comment). If anyone thinks this is incorrect, they should feel free to reopen it.