Landry Breuil <lan...@rhaalovely.net> writes: > On Mon, Feb 08, 2016 at 02:53:16PM -0600, attila wrote: >> >> Landry Breuil <lan...@rhaalovely.net> writes: > > <snip> > >> > Have you tried leaving the .xpi files compressed in their respective >> > dirs at runtime (eventually unzipping/patching/rezipping) as you comment >> > in Makefile.inc line 68 ? Iirc this should also work and is 'nicer' to >> > the filesystem.. >> >> I finally just grokked in fullness what you were saying here (sorry, a >> bit slow). Given that I already have a start-tor-browser shell script >> in place to set things up we could instead switch to having .xpi files >> in distribution/extensions (or wherever) and unpack them when >> ~/.tor-browser is populated. I'm sorry I didn't get to it before now, >> maybe the rest of what I've done can be critiqued and I'll make this >> change and test it when I get my buildbox back. > > Fwiw, in TB 45 (and, i suppose, FX 45 but ours doesnt ship default > extensions) the bundled xpi's stay installed as xpi, and that works just > fine. There should be no need to unpack them in /usr/local, nor in the > user profile - if i got it right, you copy those extensions to the user > profile ? why ? >
I'm sorry for not responding sooner. The short summary of what we've
found from testing/debugging over the last few days (on amd64 only
sadly):
1. extension-overrides.js only works if you drop it into the user's
profiledir (~/.tor-browser/profile.default/preferences). I belive
this has to do with the order in which things happen at startup;
2. The four addons in www/tbb must be in the user's profiledir or they
won't be loaded (~/.tor-browser/profile.default/extensions). It
just doesn't work from anywhere under /usr/local/lib/tor-browser-5.5
that I could find;
3. I was confused and not naming the .xpi files with the appid, e.g.
https-everywhere-...@eff.org.xpi. This is why I was convinced that
.xpi files weren't working - they do indeed work as you said once
you name them properly, but only in the user's profdir.
Attached are updated ports that rework the way the extensions are
packaged. They now drop .xpi files into
/usr/local/tor-browser-5.5/distribution/extensions, as you asked. The
start-tor-browser script copies them as before, but just .xpi files
not whole directory trees. I've also ditched the idea of bothering to
build the https-everywhere .xpi and am grabbing the official one like
I do for noscript. All of a sudden this is a lot easier to maintain.
Don't know what I was thinking.
I realize ports lock is in effect so this can't make it in but I
wanted to respond to get some closure on what we have so far. The
packages we put up for testing have been updated:
http://mirrors.nycbug.org/pub/snapshots/packages/amd64/README-55.txt
We'll keep them up to date until we (hopefully) don't have to :-)
I'm now moving on to 5.5.2, which includes a major security update
(update to latest ESR to pick up Graphite fix).
Thanks for your help and patience.
> Landry
Pax, -A
--
http://haqistan.net/~attila | att...@stalphonsos.com | 0xE6CC1EDB
tbb-resub2.tgz
Description: updated submission: tor browser ports
