Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 670336 - =www-client/firefox-bin-63.0.1-r1 installs both /opt/firefox/firefox and /opt/firefox/firefox-bin
Summary: =www-client/firefox-bin-63.0.1-r1 installs both /opt/firefox/firefox and /opt...
Status: RESOLVED FIXED
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: Current packages (show other bugs)
Hardware: All Linux
: Normal normal (vote)
Assignee: Thomas Deutschmann (RETIRED)
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2018-11-04 23:01 UTC by Vyacheslav
Modified: 2020-10-04 18:10 UTC (History)
3 users (show)

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


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Vyacheslav 2018-11-04 23:01:09 UTC
I see in /opt/firefox two executable files: firefox and firefox-bin with the same sha256 hash.
Why is it? In /usr/bin/firefox-bin, we run /opt/firefox/firefox.
Comment 1 Thomas Deutschmann (RETIRED) gentoo-dev 2018-11-05 10:15:40 UTC
I don't know why Mozilla's build system creates "firefox" and "firefox-bin" all the time. When you search Mozilla's bugzilla you will find bugs like https://bugzilla.mozilla.org/show_bug.cgi?id=552864 or https://bugzilla.mozilla.org/show_bug.cgi?id=658850.

In general I would say we should backport https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=29945375567a11ba088d76b72d52bcdb54f1486a for firefox-bin. In this case also need to deal with *.sig file.

But when you view firefox-60.0.2 release for example (https://ftp.mozilla.org/pub/firefox/releases/60.0.2/linux-x86_64/en-US/) you will notice that "firefox" and "firefox-bin" binary are different. Not sure if this was a bug...
Comment 2 Vyacheslav 2018-11-05 10:48:03 UTC
I didn't know about file size for different versions. So, I think this is not a bug.
Comment 3 Thomas Deutschmann (RETIRED) gentoo-dev 2020-10-04 18:10:28 UTC
We still create both files to be compatible with upstream/bin package but we do a symlink for the second file.