unofficial mirror of guix-patches@gnu.org 
 help / color / mirror / code / Atom feed
From: Liliana Marie Prikler <liliana.prikler@gmail.com>
To: 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 07:22:17 +0100	[thread overview]
Message-ID: <f546642dcdb8f249a48c34443d4c7be666419ad6.camel@gmail.com> (raw)
In-Reply-To: <86sfgg1z6i.fsf@gmail.com>

Am Mittwoch, dem 11.01.2023 um 23:31 +0100 schrieb zimoun:
> Hi all,
> 
> On Tue, 10 Jan 2023 at 11:47, Maxim Cournoyer
> <maxim.cournoyer@gmail.com> wrote:
> 
> > What we are discussing here is whether there's a problem or not
> > with the FSDG and the name 'unrar-free'.  Given the argument that
> > 'unrar-free' package could steer users toward 'unrar' non-free
> > (which is not available in Guix) is a bit of a stretch (as you
> > admitted), I don't think it's ground to refuse its inclusion in
> > Guix.
> 
> 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.
> 
> 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.  Now potentially, there's an
argument to be had that unrar-free acts as a "drop-in replacement" for
scripts, Makefiles etc. that assume the presence of the non-free unrar,
i.e. when you assume that you're bound to unrar's CLI.  But(!)
libarchive already liberates you from that very CLI – perhaps not by
offering the exact same interface (which for the record unrar-nonfree
also doesn't), but by offering a program that can open some of the
archives (on top of handling zip, tar, etc.).  As for the actually
supported archives, they're the same for both CLIs, so no real
liberation is happening on that front.

Somewhat ironically, if unrar-free was using its own experimental
libarchive that has some patches it wishes to upstream, which improve
the handling of some RAR quirks, I wouldn't be as opposed to including
it.  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?",
cue people sending each other advice on a certain channel dedicated to
non-free software.

Cheers





  reply	other threads:[~2023-01-12  6:23 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 [this message]
2023-01-12  7:36                   ` Giovanni Biscuolo
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=f546642dcdb8f249a48c34443d4c7be666419ad6.camel@gmail.com \
    --to=liliana.prikler@gmail.com \
    --cc=52109@debbugs.gnu.org \
    --cc=chuanwei.foo@hotmail.com \
    --cc=kiasoc5@disroot.org \
    --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).