unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Marius Bakke <mbakke@fastmail.com>
To: Brett Gilio <brettg@posteo.net>, guix-devel@gnu.org
Subject: Re: FSDG status of chromium
Date: Wed, 26 Sep 2018 00:00:48 +0200	[thread overview]
Message-ID: <87o9clkzjj.fsf@fastmail.com> (raw)
In-Reply-To: <be4ccef7-6d54-5fa2-1a2e-bfc823615d52@posteo.net>

[-- Attachment #1: Type: text/plain, Size: 676 bytes --]

Brett Gilio <brettg@posteo.net> writes:

> On 09/25/2018 03:22 PM, Andreas Enge wrote:
>>
>> So at least it is apparently possible to get a working binary with only
>> free sources.
>>
>> Andreas
>>
>>
>
> Hi Andreas,
>
> Can you verify that the debian package is only working with free 
> sources, and not simply reiterating the misconception that the chromium 
> browser is licensed under BSD? By that, I mean going after what Bill was 
> saying of auditing every single component of the chromium browser?

I would like to know prior research on this subject.  Are parts of
Chromium considered non-free?  Is there a reason not to trust the BSD
license?

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 487 bytes --]

  reply	other threads:[~2018-09-25 22:00 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-09-25 13:29 FSDG status of chromium bill-auger
2018-09-25 17:22 ` Fwd: " Brett Gilio
2018-09-25 19:08 ` Marius Bakke
2018-09-25 20:22   ` Andreas Enge
2018-09-25 20:49     ` Marius Bakke
2018-09-25 21:30     ` Brett Gilio
2018-09-25 22:00       ` Marius Bakke [this message]
2018-09-25 23:36   ` bill-auger
2018-09-26  1:23     ` Marius Bakke
2018-09-26 19:02       ` bill-auger
2018-09-25 19:36 ` Clément Lassieur
2018-09-26  8:11   ` Andy Wingo
2018-09-26  8:41     ` Clément Lassieur
2018-09-26 18:57     ` bill-auger

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=87o9clkzjj.fsf@fastmail.com \
    --to=mbakke@fastmail.com \
    --cc=brettg@posteo.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).