FIREFOX DEVELOPER EDITION 44 INSTALL
FIREFOX DEVELOPER EDITION 44 SERIES
FIREFOX DEVELOPER EDITION 44 DOWNLOAD

Inside of it we must create the sktop file and place this content inside of it: Name=Firefox Developer EditionĮxec=/home/egdoc/.local/bin/firefox-dev %u

The directory which hosts per-user desktop launchers is ~/.local/share/applications. desktop launcher, in order to integrate the application in our desktop environment application launcher. We should now be able to launch the application from our terminal: $ firefox-devĪnother thing we may want to do is to create a. We will name the link firefox-dev in order to distinguish it form the standard Firefox binary: $ ln -s ~/.local/opt/firefox/firefox ~/.local/bin/firefox-dev At this point we must create a symbolic link to the Firefox developer edition binary inside the ~/.local/bin directory. The file is sourced when we use an interactive login shell, so to make the changes effective we must logout and loginĪgain. profile has a fallback if it doesn’t exists): PATH=$/.local/bin' bash_profile is used by the bash shell, which uses. profile file, depending on the shell we are using (. PATH, we can simply append the following line in our. local directory is created inside each user’s home directory, and it’s meant to contain per-user executables. You can see that the /home/egdoc/.local/bin directory is appended to my PATH. usr/local/bin:/usr/local/sbin:/usr/bin:/usr/sbin:/home/egdoc/.local/bin

To check the content of the variable we can simply expand it:

FIREFOX DEVELOPER EDITION 44 SERIES

The value of the PATH variable is a series of directory names separated by a :, where applications are searched by default when they are invoked without specifying their absolute location. For convenience we want to add this binary to our PATH. We can then move the application directory: $ mv firefox ~/.local/opt Adding the Firefox binary to our PATHĪt this point, the Firefox developer edition binary should be now ~/.local/opt/firefox/firefox. The directory doesn’t exist by default, therefore we must create it: $ mkdir -p ~/.local/opt There is not a standard per-user equivalent of this directory, so we will arbitrarily use ~/.local/opt as destination. By convention, self contained, global-installed applications are placed in the /opt directory.

FIREFOX DEVELOPER EDITION 44 INSTALL

In this tutorial we will install the application for our user only. The next step consists into placing the Firefox directory somewhere more appropriate in our filesystem. If everything go as planned, in the directory from which we executed the command, we will find a new “firefox” directory. To perform an extraction, -verbose (optional) to make the name of the extracted files be printed on the terminal when they are extracted, -preserve-permissions to preserve the files permissions, and -bzip2 to specify how the tarball should be decompressed. We used the latter with some options: -extract If not otherwise specified, curl writes its output to stdout (standard output), so we use a pipe | to redirect said output and use it as the standard input ( stdin) of the tar application.

FIREFOX DEVELOPER EDITION 44 DOWNLOAD

We invoked curl using the -location option which is needed to make curl follow redirections, and providing the download URL. | tar -extract -verbose -preserve-permissions -bzip2 All we have to do is to run the following command: $ curl -location We can download the application also from the command line, using the curl utility if we combine it with tar via a pipe, we can extract the tarball “on the fly”.

Firefox developer edition 44