unofficial mirror of guix-patches@gnu.org 
 help / color / mirror / code / Atom feed
From: Maxim Cournoyer <maxim.cournoyer@gmail.com>
To: Liliana Marie Prikler <liliana.prikler@gmail.com>
Cc: 52109@debbugs.gnu.org, Foo Chuan Wei <chuanwei.foo@hotmail.com>
Subject: [bug#52109] [PATCH] gnu: Add unrar-free.
Date: Tue, 03 Jan 2023 19:57:35 -0500	[thread overview]
Message-ID: <87358rxgjk.fsf_-_@gmail.com> (raw)
In-Reply-To: <ada21a5577d7b4489409e234e880735bc49f2697.camel@gmail.com> (Liliana Marie Prikler's message of "Thu, 25 Nov 2021 20:49:27 +0100")

Hi Liliana,

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

> Hi,
>
> Am Donnerstag, den 25.11.2021, 15:19 +0000 schrieb Foo Chuan Wei:
>> * gnu/packages/compression.scm (unrar-free): New variable.
>> [...]
>> +    (inputs
>> +     `(("libarchive" ,libarchive)))
>> [...] 
>> This program is a simple command-line front-end to libarchive
> Does this program handle anything that libarchive does not already
> have?  libarchive already ships its own command line utility (bsdtar),
> plus there's other frontends with less confusing names available.  The
> only use-case for "unrar-free" would be to inevitably push people
> towards the non-free unrar when it inevitably fails to upack that one
> of several weird rar files [1].

Since the program uses libarchive, it would think it supports the same
features as libarchive itself.  Its value is in providing a simpler to
use front-end CLI.

While I appreciate your concern, I don't think it is a problem to have
unrar-free in GNU Guix; it is free software and respects the GNU FSDG,
as far as I can tell.

Thoughts?

-- 
Thanks,
Maxim




  reply	other threads:[~2023-01-04  0:58 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 [this message]
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
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=87358rxgjk.fsf_-_@gmail.com \
    --to=maxim.cournoyer@gmail.com \
    --cc=52109@debbugs.gnu.org \
    --cc=chuanwei.foo@hotmail.com \
    --cc=liliana.prikler@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).