From mboxrd@z Thu Jan 1 00:00:00 1970 From: ng0 Subject: Re: torbrowser Date: Mon, 6 Mar 2017 17:38:58 +0000 Message-ID: <20170306173858.5k7xydt7eduqyc2q@abyayala> References: <20170306151459.wp2zlyoy6gre3q2w@abyayala> <20170306080652.796452a2@khaalida> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:57722) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ckvWk-0000no-Le for guix-devel@gnu.org; Mon, 06 Mar 2017 11:30:27 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1ckvWh-0003py-Ge for guix-devel@gnu.org; Mon, 06 Mar 2017 11:30:26 -0500 Received: from latitanza.investici.org ([2001:888:2000:56::19]:63209) by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1ckvWh-0003pS-7K for guix-devel@gnu.org; Mon, 06 Mar 2017 11:30:23 -0500 Content-Disposition: inline In-Reply-To: <20170306080652.796452a2@khaalida> List-Id: "Development of GNU Guix and the GNU System distribution." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org Sender: "Guix-devel" To: dian_cecht@zoho.com Cc: guix-devel@gnu.org On 17-03-06 08:06:52, dian_cecht@zoho.com wrote: > On Mon, 6 Mar 2017 15:14:59 +0000 > ng0 wrote: > > My idea is now to just reconstruct what torproject does, from the git > > checkout of torbrowser and eventually later fix Guix specific > > issues and fine tuning (freedom issues etc etc). > > Would it be possible to grab the patches Torbrowser uses against > Firefox and simply try to apply them to IceCat? I don't know exactly > what version of FF Icecat and Torbrowser build off of, but if that > could work it might make life a bit easier. > > Alternativly, maybe applying the icecat patches to Torbrowser might > work, too. > > Not really. Icecat is just too old, and the firefox version torbrowser is based on is not compatible with the one icecat uses. I would not want the extra work to backport patches. So far, I haven't investigated all possible ways, it seems too much work to cherry-pick what torbrowser does to firefox. as they seem to maintain all in the repository it could work out to just build from there. Their release workflow (not automated but well documented) includes pulling in from firefox, so there has to be firefox code in the repository. The time and effort to base this on icecat is not worth it... unless someone wants to start an icecat-torbrowser which *closely* tracks torbrowser and does not become so unresponsive to bugs/issues like icecat currently is. And in both cases, the browser I assemble, and in the not-existing case of a blend of torbrowser,I want to compare against upstream releases to see how much we would differ and how much it'll affect fingerprinting etc. This difference will go into the description, as it can't be described as a 1:1 port of torbrowser.