all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: ng0 <ng0@we.make.ritual.n0.is>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: guix-devel@gnu.org
Subject: Re: Tor Browser
Date: Fri, 05 Aug 2016 13:35:44 +0000	[thread overview]
Message-ID: <87fuqjmj7z.fsf@we.make.ritual.n0.is> (raw)
In-Reply-To: <87mvm355r3.fsf@gnu.org>

Ludovic Courtès <ludo@gnu.org> writes:

> ng0@we.make.ritual.n0.is skribis:
>
>> Ludovic Courtès writes:
>
> [...]
>
>>> I suppose TB contains a script that does all that, right?  Would it work
>>> to simply run it?  If it invokes wget/curl, then this needs to be
>>> replaced, but the rest should be fine.
>>
>> It's not that easy I'm afraid.
>> Currently they use a gitian build, as described in this README[0],
>> which the person maintaining the torbrowser ebuild for Gentoo out
>> of portage replicates and follows in parts.
>> It can't be followed completely, as `builders/tor-browser-bundle'
>> requires a checkout of gitian of the torproject.org
>>
>> So we have to look at what they do and recreate this build
>> procedure, there's no individual Makefile, the releases are
>> created in VMs.
>>
>> Dependencies are kept up to date here[1].
>>
>> This[2] is the script connecting/using gitian for gnu-linux releases.
>>
>> The Makefile just runs the corresponding scripts.
>
> Gitian is about building binaries.  There must be some script somewhere
> to apply the relevant patches to the source first, before one builds it,
> no?
>
>>> It’s unfortunate that there’s no ready-to-build TB tarball, that would
>>> simplify things for us.
>>
>> Yes.. But I think icecat suffers from the same problem, only that
>> icecat tarballs/binaries are built using a bash script applying
>> all that's needed to the firefox sources again.
>
> IceCat publishes source tarballs that, AIUI, are produced essentially by
> running a script that patches Firefox’s code base (same approach for
> Linux-libre.)
>
> Thanks,
> Ludo’.

There are the .mar files, which I suppose are the built source of
torbrowser, but I can't tell for sure since i can't find an upstream for
mar-tools. I guess it is Mozilla, but where is it available?

https://dist.torproject.org/torbrowser/6.0.3/

-- 
♥Ⓐ  ng0
Current Keys: https://we.make.ritual.n0.is/ng0.txt
For non-prism friendly talk find me on http://www.psyced.org

  parent reply	other threads:[~2016-08-05 13:35 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-23 10:41 patches question ng0
2016-06-23 11:09 ` Andreas Enge
2016-06-23 11:30   ` ng0
2016-06-23 20:14     ` Andreas Enge
2016-06-23 22:18       ` ng0
2016-06-23 13:23 ` ng0
2016-06-23 20:27   ` Andreas Enge
2016-06-24 12:09   ` Ludovic Courtès
2016-06-24 13:43     ` ng0
2016-06-24 15:48       ` Tor Browser Ludovic Courtès
2016-06-24 17:49         ` ng0
2016-06-26 10:05           ` Ludovic Courtès
2016-06-29 12:48             ` ng0
2016-06-30 10:29               ` Ludovic Courtès
2016-06-30 16:09                 ` ng0
2016-06-30 18:00                 ` ng0
2016-08-05 13:35                 ` ng0 [this message]
2016-08-06  4:05                   ` Alex Vong
2016-08-06 11:14                     ` ng0
2016-08-08  8:03                       ` Alex Vong
2016-08-10 20:01                         ` Mark H Weaver
2016-08-11  8:51                           ` 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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87fuqjmj7z.fsf@we.make.ritual.n0.is \
    --to=ng0@we.make.ritual.n0.is \
    --cc=guix-devel@gnu.org \
    --cc=ludo@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 external index

	https://git.savannah.gnu.org/cgit/guix.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.