local installation of icecat/tor-browser executable tarball

11 réponses [Dernière contribution]
chaosmonk

I am a member!

I am a translator!

Hors ligne
A rejoint: 07/07/2017

A frequent question here is what to do with an Icecat or Tor Browser
executable tarball. I find myself repeatedly describing how to make
these browsers appear in menus and be launchable from the terminal, so
to save myself and others some time I have created some scripts for this
task.

https://notabug.org/chaosmonk/mozilla-tarball-install

northernarcher
Hors ligne
A rejoint: 12/24/2014

I will try this when I have more time, but it seems you are doing gods work.

loldier
Hors ligne
A rejoint: 02/17/2016

Great work! I appreciate. For Icecat, good.

However, Tor Browser Bundle need not be "installed". Extract the tarball on your desktop or a USB stick, and you're good.

tor.png tor2.png
chaosmonk

I am a member!

I am a translator!

Hors ligne
A rejoint: 07/07/2017

On 02/13, name at domain wrote:
> Great work! I appreciate. For Icecat, good.
>
> However, Tor Browser Bundle need not be "installed". Extract the tarball
> on your desktop or a USB stick, and you're good.

By "install" i mean "extract to an out-of-the-way directory and create
symlinks to the binary and .desktop file so that for the end user
everything works as if it had been installed from the package manager."
This approach could work with any Firefox derivative distributed as an
executable tarball, including Firefox itself, but I focused on Tor
Browser and Icecat because they are FSDG-compliant.

loldier
Hors ligne
A rejoint: 02/17/2016

Tor Browser can be registered (this will add an entry in the menu) by running this command in the Tor Browser Bundle directory.

./start-tor-browser.desktop --register-app

registerapp.png
chaosmonk

I am a member!

I am a translator!

Hors ligne
A rejoint: 07/07/2017

> ./start-tor-browser.desktop --register-app

Good to know. Does this also add the binary to the user's path so it can
be launched from a terminal?

loldier
Hors ligne
A rejoint: 02/17/2016

Apparently not. Can't see any success with either 'tor-browser' or 'start-tor-browser' (in a terminal).

GrevenGull
Hors ligne
A rejoint: 12/18/2017

How do I know if it's an executable tarball or a source tarball?

chaosmonk

I am a member!

I am a translator!

Hors ligne
A rejoint: 07/07/2017

> How do I know if it's an executable tarball or a source tarball?

The executable tarballs contain the architecture (i.e. gnulinux-i686 or
gnulinux-x96_64) in the file name.

GrevenGull
Hors ligne
A rejoint: 12/18/2017

Right. In the last step:

$ ./install-from-tarball /path/to/tarball

should "tarball" in ".install-from-tarball" be exchanged for the filename of the tarball? Like:

$ ./install-from-tor-browser-linux64-8.5.4_en-US.tar.xz /path/to/tor-browser-linux64-8.5.4_en-US.tar.xz

or not? Like this:

$ ./install-from-tarball /path/to/tor-browser-linux64-8.5.4_en-US.tar.xz

Just wondering if the "unboldness" of the word "tarball" in the guide has any meaning to it :)

chaosmonk

I am a member!

I am a translator!

Hors ligne
A rejoint: 07/07/2017

> $ ./install-from-tarball /path/to/tarball
>
> should "tarball" in ".install-from-tarball" be exchanged for the filename of
> the tarball? Like:
>
> $ ./install-from-tor-browser-linux64-8.5.4_en-US.tar.xz
> /path/to/tor-browser-linux64-8.5.4_en-US.tar.xz

"/path/to/tarball" should be replaced with location of the tarball. So,
if it's in your Downloads directory you should do

$ ./install-from-tarball ~/Downloads/tor-browser-linux64-8.5.4_en-US.tar.xz

> Just wondering if the "unboldness" of the word "tarball" in the guide has
> any meaning to it :)

No, that's just how notabug is rendering the markdown file.

GrevenGull
Hors ligne
A rejoint: 12/18/2017

Thank you!