unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: ng0 <ng0@n0.is>
To: guix-devel@gnu.org
Subject: Re: torbrowser
Date: Wed, 7 Mar 2018 12:46:01 +0000	[thread overview]
Message-ID: <20180307124601.fjjvtkjw4ppcqxxk@abyayala> (raw)
In-Reply-To: <20170306173858.5k7xydt7eduqyc2q@abyayala>

ng0 transcribed 1.7K bytes:
> On 17-03-06 08:06:52, dian_cecht@zoho.com wrote:
> > On Mon, 6 Mar 2017 15:14:59 +0000
> > ng0 <contact.ng0@cryptolab.net> 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).
[snip]
(Don't consider this "necro-bumping".)

The maintainer of the ebuild for Gentoo in the torbrowser-overlay
just gave me the last missing pieces of information for building torbrowser.
Recent commit message subjects in the upstream torbrowser repository
make me assume there will be no issues for integration into Guix master.
As long as the final build ressembles what I have talked about with them
we can even name it torbrowser and have the official design.

I hope to be done with this by summer, but you never know with browser.
But it's just a Firefox ESR deriv., so (ideally) it should just be a matter
of 1 or 2 weekends.
-- 
A88C8ADD129828D7EAC02E52E22F9BBFEE348588
https://n0.is/~ng0

  reply	other threads:[~2018-03-07 12:46 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-06 15:14 torbrowser ng0
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     ` ng0 [this message]
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=20180307124601.fjjvtkjw4ppcqxxk@abyayala \
    --to=ng0@n0.is \
    --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).