From: ptrcnull <ptrcnull@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: Chromium package contains non-free components (Widevine)
Date: Sun, 07 Mar 2021 00:52:05 +0100 [thread overview]
Message-ID: <20210306235205.0bmNUdJhcWPpV7-ZSyXMaVtC9Hd2xA3iVtCKz5Oef8E@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-29273@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 624 bytes --]
New comment by ptrcnull on void-packages repository
https://github.com/void-linux/void-packages/issues/29273#issuecomment-792119673
Comment:
I don't think the issue is about FSF or any other guidelines; it's just not cool that a supposedly open-source package downloads a backdoor from Google, considering that it's possible to disable it, as [Debian package maintainers](https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=%23960454) have been able to do it.
As far as I know, Michel's patch would allow users to still download Widevine via the `chromium-widevine` package, but makes it actually opt-in and transparent.
next prev parent reply other threads:[~2021-03-06 23:52 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-06 18:05 [ISSUE] " selfisekai
2021-03-06 18:44 ` ericonr
2021-03-06 22:09 ` selfisekai
2021-03-06 22:19 ` q66
2021-03-06 22:19 ` q66
2021-03-06 23:42 ` ptrcnull
2021-03-06 23:43 ` ptrcnull
2021-03-06 23:52 ` ptrcnull [this message]
2021-03-07 1:30 ` q66
2021-03-07 1:40 ` ericonr
2021-03-07 1:40 ` ericonr
2021-03-07 2:11 ` q66
2021-03-07 2:27 ` ericonr
2021-03-07 2:32 ` q66
2022-05-07 2:06 ` github-actions
2022-05-22 2:10 ` [ISSUE] [CLOSED] " github-actions
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=20210306235205.0bmNUdJhcWPpV7-ZSyXMaVtC9Hd2xA3iVtCKz5Oef8E@z \
--to=ptrcnull@users.noreply.github.com \
--cc=ml@inbox.vuxu.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.
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 NNTP newsgroup(s).