unofficial mirror of guix-patches@gnu.org 
 help / color / mirror / code / Atom feed
From: Giovanni Biscuolo <g@xelera.eu>
To: Liliana Marie Prikler <liliana.prikler@gmail.com>,
	zimoun <zimon.toutoune@gmail.com>,
	Maxim Cournoyer <maxim.cournoyer@gmail.com>
Cc: kiasoc5 <kiasoc5@disroot.org>,
	52109@debbugs.gnu.org, Foo Chuan Wei <chuanwei.foo@hotmail.com>
Subject: [bug#52109] [PATCH] gnu: Add unrar-free.
Date: Thu, 12 Jan 2023 08:36:05 +0100	[thread overview]
Message-ID: <87y1q8mcgq.fsf@xelera.eu> (raw)
In-Reply-To: <f546642dcdb8f249a48c34443d4c7be666419ad6.camel@gmail.com>

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

Hello everybody,

Liliana Marie Prikler <liliana.prikler@gmail.com> writes:

> Am Mittwoch, dem 11.01.2023 um 23:31 +0100 schrieb zimoun:

[...]

>> I agree with Maxim’s arguments.  From my point of view, unrar-free
>> respects FSDG – and since it is present in Trisquel, I assume this
>> understanding of FSDG is shared – to some extent.

I also agree with _both_ Maxim arguments:

1. unrar-free is FSDG compliant, and I cannot see how this can be
defined "point of view" :-)

2. 'unrar-free' potentially steering users toward 'unrar' (non-free)
cannot be used as an argument to refuse 'unrar-free' inclusion in Guix

Liliana please reply to this two specific points, in particular please
tell us if you judge 'unrar-free' not to be FSDG compliant

>> Even, I would say the Liliana’s opposite argument: it liberates user
>> from the non-free unrar by offering a free alternative.  And it is
>> the case for all the free re-implementations, no?
> From my point of view, it really doesn't.

[...]

> But as it stands right now, I see it as little more than a piece of
> software that makes people go "but how do I get the _real_ unrar?",

(I don't understand "cue people": is it a misprint?)

OK I think you explained this argument very well and this goes under
point 2. above: 'unrar-free' potentially steering users toward 'unrar'
non-free

I'd say that all liberated versions of non-free software could make
people go "how do I get the _real_ one", no?  For example Guix
distributed browsers are lacking EME implementation (no DRM loading) and
some other non-free "extensions" giving problems to users trying to use
certain web services; we have ungoogled-chromium and I know people
asking "how do I get the real Chrome"?

> cue people sending each other advice on a certain channel dedicated to
> non-free software.

So, if I understand your last point, the problem you see is that
"unrar-free" (alone?) steers people to send each other advice on
channels including non-free software: could this be a reason not to
include a FSDG compliant software in Guix?

...or it's just it's name containing 'unrar'?

Cheers

-- 
Giovanni Biscuolo

Xelera IT Infrastructures

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

  reply	other threads:[~2023-01-12  7:37 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-25 15:19 [bug#52109] [PATCH] gnu: Add unrar-free Foo Chuan Wei
2021-11-25 19:49 ` Liliana Marie Prikler
2023-01-04  0:57   ` Maxim Cournoyer
2023-01-04  5:32     ` kiasoc5 via Guix-patches via
2023-01-04 19:41       ` Liliana Marie Prikler
2023-01-04 20:21         ` Maxim Cournoyer
2023-01-06 17:46           ` Liliana Marie Prikler
2023-01-10 16:47             ` Maxim Cournoyer
2023-01-11 22:31               ` zimoun
2023-01-12  6:22                 ` Liliana Marie Prikler
2023-01-12  7:36                   ` Giovanni Biscuolo [this message]
2023-01-12 20:29                     ` Liliana Marie Prikler
2023-01-12 21:54                       ` Maxim Cournoyer
2023-01-12 23:07                       ` Leo Famulari
2023-01-13  5:19                         ` Liliana Marie Prikler
2023-01-13 15:20                       ` [bug#52109] How to resolve? (Re: [bug#52109] [PATCH] gnu: Add unrar-free.) Simon Tournier
2023-01-13 18:18                         ` Liliana Marie Prikler
2023-01-16  9:46                           ` Simon Tournier
2023-01-16 13:56                             ` Liliana Marie Prikler
2023-01-16 16:38                               ` Simon Tournier
2023-01-21 16:09                                 ` [bug#52109] Mention bsdcat, bsdcpio and bsdtar in description of libarchive zimoun
2023-01-21 17:59                                   ` Liliana Marie Prikler
2023-01-21 20:02                                     ` Maxim Cournoyer
2023-01-22 15:09                                     ` zimoun
2023-01-22 17:44                                       ` Liliana Marie Prikler
2023-01-22 19:36                                         ` Maxim Cournoyer
2023-01-23  7:45                                         ` zimoun
2023-01-23 19:29                                           ` Liliana Marie Prikler
2023-01-21 20:00                                   ` Maxim Cournoyer
2023-01-22 14:56                                     ` zimoun
2023-01-22 19:27                                       ` Maxim Cournoyer
2023-01-12 12:54                   ` [bug#52109] [PATCH] gnu: Add unrar-free Leo Famulari
2023-01-12 20:49                     ` Liliana Marie Prikler
2023-01-04 22:32         ` kiasoc5 via Guix-patches via
2023-01-13 18:29 ` bug#52109: " Leo Famulari

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=87y1q8mcgq.fsf@xelera.eu \
    --to=g@xelera.eu \
    --cc=52109@debbugs.gnu.org \
    --cc=chuanwei.foo@hotmail.com \
    --cc=kiasoc5@disroot.org \
    --cc=liliana.prikler@gmail.com \
    --cc=maxim.cournoyer@gmail.com \
    --cc=zimon.toutoune@gmail.com \
    /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).