all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Christopher Lemmer Webber <cwebber@dustycloud.org>
To: guix-devel@gnu.org
Subject: Re: Vanilla Firefox recipe?
Date: Tue, 26 May 2020 13:34:02 -0400	[thread overview]
Message-ID: <87mu5uwqgl.fsf@dustycloud.org> (raw)
In-Reply-To: <87o8qawqr7.fsf@dustycloud.org>

(An obvious win from this also being that we will be able to have more
Guix users running, on average, a more up-to-date on security browser
more often.)

Christopher Lemmer Webber writes:

> [moving from help-guix to guix-devel]
>
> On help-guix this exchange occured when discussing trying to install
> Vanilla Firefox... two things struck me:
>
>  - Firefox's source code is itself free, but it doesn't follow the FSDG
>    (An assertion was made that Firefox was itself nonfree software,
>    but this seems like an inaccurate characterization.  I agree it
>    doesn't follow the FSDG, however.)
>  - It is probably possible, with minimal changes, to resolve that.
>
> So this page explains the problem:
>
>   https://libreplanet.org/wiki/List_of_software_that_does_not_respect_the_Free_System_Distribution_Guidelines
>
> "Problem: Recommends non-free addons and plugins; automatically downloads cisco's binary h.264 codecs"
>
> I agree the latter is a problem.  The former is kind of maybe a problem,
> but mostly because it isn't clear that it's happening to the user.
>
> However, I wonder if, with a matter of just two patches, this could be
> resolved:
>
>  - Patch out the automatic download of Cisco's h.264 plugin.
>  - Add a warning banner *above* the extensions page, or simply switch it
>    to the same one that Icecat already uses.
>
> Is that all that's necessary, then, to get "vanilla Firefox" in Guix?
> It strikes me that with those two changes, the criteria would be met.
>
> (Yes, I know that IceCat also provides LibreJS and some other plugins,
> and that's nice to have, but Guix already ships several other browsers
> that do not have those plugins, so this does not seem to be a strict
> impediment and I don't think it should be either.  We could change the
> default Firefox homepage to point at one that recommends installing some
> of these plugins, if that would be helpful.)
>
>  - Chris
>
>
> Christopher Lemmer Webber writes:
>
>> I'm not sure it's really accurate to categorize asking for a vanilla
>> copy of firefox, which might not comply with the FSDG, as nonfree
>> software.  The primary issue with Firefox that makes it qualify as
>> "nonfree" is that the add-ons tool brings you to something that might
>> guide a user towards nonfree software right?  Thus I think this isn't
>> exactly correct framing, since firefox itself isn't nonfree?  There is a
>> difference if I, as a user, install Firefox as free software, and I am
>> aware of the issue with the default extensions kit, and end up
>> installing no nonfree software on my computer, right?
>>
>> Am I missing something?  What makes Firefox itself nonfree (which I
>> think is not quite the same thing as not compliant with the FSDG)?
>>
>>
>> Adonay Felipe Nogueira via writes:
>>
>>> I came late to this issue, but I think this should have been posted on
>>> development mailing list. It's not good if we use the general help list
>>> to foster non-free software like Firefox or those which are third-party
>>> package managers with no default repository explicitly commited to
>>> following the GNU FSDG.
>>>
>>> Furthermore, to ease the sides of both the thread starter and the
>>> community, I'm taking a simplification in that I'm considering the use
>>> of such non-free software for purpose of developing or improving a free
>>> replacement. That means I'm not discussing the merit of whether the
>>> question should or shouldn't have been answered the way it was.
>>>
>>> One must be remind though, that the GNU FSDG isn't only about the
>>> packages distributed (software, documentation, text fonts, etc), but
>>> also about the community, and this is one of the things that keep Debian
>>> out of the list of free system distributions.
>>>
>>> Em 12/05/2020 16:23, Efraim Flashner escreveu:
>>>> On Mon, May 11, 2020 at 10:31:02PM +0200, Guillaume Le Vaillant wrote:
>>>>>
>>>>> Christopher Lemmer Webber <cwebber@dustycloud.org> skribis:
>>>>>
>>>>>> Anyone have a package definition (or channel) for a recent vanilla
>>>>>> firefox?
>>>>>>
>>>>>> I understand the decision to prefer distributing Icecat instead in Guix
>>>>>> proper, but I need a more recent version of things... I suspect others
>>>>>> sometimes do too.  I have a feeling at least someone in the community
>>>>>> has written such a definition... would you mind sharing?
>>>>>>
>>>>>> Thanks!
>>>>>>  - Chris
>>>>>
>>>>> Hi,
>>>>>
>>>>> There is a channel at
>>>>> https://forge.monarch-pass.net/warrah/warrah-nonfsdg with a package
>>>>> definition for Firefox 74.0.1. I haven't tested it though.
>>>>
>>>> Other options include using the now official flatpak copy of firefox. If
>>>> you do go that route make sure to use the '--user' flag for flatpak so
>>>> it doesn't segfault while trying to write to /var/lib/flatpak.
>>>>



  reply	other threads:[~2020-05-26 17:36 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-11 19:10 Vanilla Firefox recipe? Christopher Lemmer Webber
2020-05-11 20:31 ` Guillaume Le Vaillant
2020-05-12 19:23   ` Efraim Flashner
2020-05-24 13:54     ` Adonay Felipe Nogueira via
2020-05-25 20:17       ` Christopher Lemmer Webber
2020-05-26 17:27         ` Christopher Lemmer Webber
2020-05-26 17:34           ` Christopher Lemmer Webber [this message]
2020-05-26 17:45           ` Leo Famulari
2020-05-27  4:33           ` Carlo Zancanaro
2020-05-27 11:53             ` Christopher Lemmer Webber
2020-05-26 20:27         ` Ludovic Courtès
2020-05-27  5:16         ` Why Mozilla Firefox is nonfree? (was: Vanilla Firefox recipe?) Dmitry Alexandrov
2020-05-27 17:31           ` Adonay Felipe Nogueira via
2020-05-28  5:11             ` X-Content-Filtered-By: Mailman/MimeDel 2.1.23 Dmitry Alexandrov
2020-05-27 14:26         ` Vanilla Firefox recipe? Tobias Geerinckx-Rice
2020-05-25 20:44       ` Tobias Geerinckx-Rice

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=87mu5uwqgl.fsf@dustycloud.org \
    --to=cwebber@dustycloud.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 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.