From: ng0 <contact.ng0@cryptolab.net>
To: guix-devel@gnu.org
Subject: torbrowser
Date: Mon, 6 Mar 2017 15:14:59 +0000 [thread overview]
Message-ID: <20170306151459.wp2zlyoy6gre3q2w@abyayala> (raw)
I'm currently occupying the time where I don't study various things and
debug gnunet-service with packaging torbrowser.
So Gentoo (inofficially, 'torbrowser-overlay'[1]) uses the pre-build
archives found on dist.torproject.org in combination with a git checkout
and the torbrowser + firefox patches done by Gentoo devs[1.1].
NixOS in Nixpkgs[2] makes use of patchelf to just fix up the prebuild
variant found on dist.torproject.org.
I suspect that the way Nix 'fixes' this is a no-go for us.
My idea is now to just reconstruct what torproject does, from the git
checkout of torbrowser[3] and eventually later fix Guix specific issues
and fine tuning (freedom issues etc etc).
Cloning takes a rather long time, this is where Andy's shallow-clone
would be useful, which is where I ran into issue and delayed re-working
this for now. If someone is interested I can post the patch which
applied on master recently.
1: An overlay can be compared to what we have as 'GUIX_PACKAGE_PATH',
distributed in official and inofficial forms.
1.1: The raw data of the ebuild can be seen here, excluding eclasses:
https://data.gpo.zugaina.org/torbrowser/www-client/torbrowser/torbrowser-45.7.0_p650.ebuild
2: https://github.com/NixOS/nixpkgs/blob/3d104ab2b3e578cb4599b6fffbcc019b09547521/pkgs/tools/security/tor/torbrowser.nix
3: http://dccbbv6cooddgcrq.onion/tor-browser.git
next reply other threads:[~2017-03-06 14:06 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-06 15:14 ng0 [this message]
2017-03-06 15:47 ` torbrowser Ludovic Courtès
2017-03-06 17:26 ` torbrowser ng0
2017-03-06 16:06 ` torbrowser dian_cecht
2017-03-06 17:38 ` torbrowser ng0
2018-03-07 12:46 ` torbrowser ng0
2018-03-07 15:32 ` torbrowser Christopher Lemmer Webber
2018-03-08 7:24 ` torbrowser Catonano
2018-03-08 12:11 ` torbrowser ng0
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20170306151459.wp2zlyoy6gre3q2w@abyayala \
--to=contact.ng0@cryptolab.net \
--cc=guix-devel@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).