unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: Adonay Felipe Nogueira via <help-guix@gnu.org>
To: help-guix@gnu.org
Subject: Re: Vanilla Firefox recipe?
Date: Sun, 24 May 2020 10:54:53 -0300	[thread overview]
Message-ID: <9077d3bf-1f83-6e08-341d-7f7be5387f42@hyperbola.info> (raw)
In-Reply-To: <20200512192319.GA918@E5400>


[-- Attachment #1.1: Type: text/plain, Size: 2805 bytes --]

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.
> 

-- 
* Ativista do software livre
	* https://libreplanet.org/wiki/User:Adfeno
	* Membro dos grupos avaliadores de
		* Software (Free Software Directory)
		* Distribuições de sistemas (FreedSoftware)
		* Sites (Free JavaScript Action Team)
	* Não sou advogado e não fomento os não livres
* Sempre veja o spam/lixo eletrônico do teu e-mail
	* Ou coloque todos os recebidos na caixa de entrada
* Sempre assino e-mails com OpenPGP
	* Chave pública: vide endereço anterior
	* Qualquer outro pode ser fraude
	* Se não tens OpenPGP, ignore o anexo "signature.asc"
* Ao enviar anexos
	* Docs., planilhas e apresentações: use OpenDocument
	* Outros tipos: vide endereço anterior
* Use protocolos de comunicação federadas
	* Vide endereço anterior
* Mensagens secretas somente via
	* XMPP com OMEMO
	* E-mail criptografado e assinado com OpenPGP


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 213 bytes --]

  reply	other threads:[~2020-05-24 14:18 UTC|newest]

Thread overview: 11+ 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 [this message]
2020-05-25 20:17       ` 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

  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=9077d3bf-1f83-6e08-341d-7f7be5387f42@hyperbola.info \
    --to=help-guix@gnu.org \
    --cc=adfeno@hyperbola.info \
    /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 read-only IMAP folder(s) and NNTP newsgroup(s).