[Slackbuilds-users] dead data in tor-browser

Thomas Morper thomas at beingboiled.info
Thu Jan 14 21:58:21 UTC 2016

On Thu, 14 Jan 2016, Willy Sudiarto Raharjo wrote:

> when you run tor-browser from your local account, the source will be
> copied to your home directory as well and your user will use it
> instead of the one in /opt.

Have a look at the "tor-browser" script... the private installation in the 
user's home directory is made by unpacking the archive stored in the 
/opt/tor-browser directory, e.g. tor-browser-linux64-5.0.6_en-US.tar.xz.

The SlackBuild script correctly stores the source archive, but first it 
unpacks the source archive and moves everything to /opt. This is wrong.
The resulting /opt/Browser (and /opt/start-tor-browser.desktop) is 150MB 
of dead data. These files are not used for anything. In fact they're not 
even readable by a user.

A correct tor-browser.SlackBuild should look like this:


(needs a copy of mozicon128.png and a bit more refinement)


More information about the SlackBuilds-users mailing list