unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: ludo@gnu.org (Ludovic Courtès)
To: guix-devel@gnu.org
Subject: Tor Browser
Date: Fri, 24 Jun 2016 17:48:49 +0200	[thread overview]
Message-ID: <87por637vi.fsf_-_@gnu.org> (raw)
In-Reply-To: <20160624134357.GA30727@shadowwalker> (ng0@we.make.ritual.n0.is's message of "Fri, 24 Jun 2016 13:43:57 +0000")

ng0 <ng0@we.make.ritual.n0.is> skribis:

> On 2016-06-24(02:09:39PM+0200), Ludovic Courtès wrote:

[...]

>> > (define-public firefox
>> >   (package
>> >     (name "firefox")
>> >     (version "45.2.0esr")
>>
>> What is the goal here?
>>
>> Guix proper can provide IceCat (which modifies Firefox to comply with
>> trademark rules, to comply with the GNU FSDG¹, and to enhance privacy),
>> maybe Tor Browser (assuming it complies with the FSDG as well), but not
>> stock Firefox (unless the trademark issue and FSDG violations are
>> resolved.)
>
> Writing a base for torbrowser

Great!  Then I think you don’t need to worry about Firefox at all.
Maybe TB uses Firefox’s source and then patches it, but that doesn’t
mean we need a Firefox package.

>> Besides, I think it should be possible to (inherit icecat) rather than
>> duplicate all the recipe.
>
> True, but between 38.8 and 45.2.0 things change, patches can not be reused,
> and the reason I gave above.

Then use the Firefox 45 source as a starting point.

> I am more willing to maintain another fork of firefox than to
> wait for icecat to be recent enough to be usable as a base for
> a torbrowser package.

I think there’s a misunderstanding: if Guix provides Tor Browser, then
it should provide precisely Tor Browser, not Firecat or Icefox with 20
patches.  :-)

> Additionally I was about to get in contact with torproject and
> ask about possible trademark/confusion issues on their side,
> the unsent email:

I think we do not need to bother them.  AFAIK, we can use the name “Tor
Browser” just fine, so there’s no reason to invent another name or
anything.

The only issue that needs to be addressed (but again, we don’t need to
bother the Tor folks with that) is whether Tor Browser is FSDG-compliant
(concretely, whether it recommends non-free software, for instance.)

HTH!

Ludo’.

  reply	other threads:[~2016-06-24 15:48 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       ` Ludovic Courtès [this message]
2016-06-24 17:49         ` Tor Browser 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
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

  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=87por637vi.fsf_-_@gnu.org \
    --to=ludo@gnu.org \
    --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).