From: Liliana Marie Prikler <liliana.prikler@gmail.com>
To: Leo Famulari <leo@famulari.name>
Cc: 52109@debbugs.gnu.org,
Maxim Cournoyer <maxim.cournoyer@gmail.com>,
zimoun <zimon.toutoune@gmail.com>,
Giovanni Biscuolo <g@xelera.eu>, kiasoc5 <kiasoc5@disroot.org>,
Foo Chuan Wei <chuanwei.foo@hotmail.com>
Subject: [bug#52109] [PATCH] gnu: Add unrar-free.
Date: Fri, 13 Jan 2023 06:19:19 +0100 [thread overview]
Message-ID: <84b1430354267a6db5c76c1470ab7e932924e2c3.camel@gmail.com> (raw)
In-Reply-To: <Y8CSohf7OZt/Yzs8@jasmine.lan>
Am Donnerstag, dem 12.01.2023 um 18:07 -0500 schrieb Leo Famulari:
> On Thu, Jan 12, 2023 at 09:29:09PM +0100, Liliana Marie Prikler
> wrote:
> > Now, I hope I'm not exaggerating when I say that most computer
> > users use libarchive-based (un)archiving tools already. [3]
> > Having observed this, I see little meaning in having a frontend,
> > which per its name promises to open archives that their existing
> > tooling can't handle, only to then reveal that it was the existing
> > tooling all along. If it didn't have the name that suggested it
> > was able to do that, no one would expect it to, and upon
> > encountering an archive that libarchive can't handle, they could go
> > "well, fuck those rar guys, I have better things to do", or they
> > could try and figure out what's wrong and contribute a fix (not
> > that a fix is easily contributed given the nature of this bug, but
> > somewhere along their journey they'd notice that rar is proprietary
> > garbage and not fault libarchive too hard for not handling it).
> > Because unrar-free does have a name that suggests it's able to
> > unrar those things, however, they will inevitably feel wronged no
> > matter what and rather think "well, fuck unrar-free, I want
> > unrar-nonfree".
>
> In order to understand your points better, I'd like to summarize them
> in my own words. Please tell me if I get it wrong.
>
> Your objections to the inclusion of this package are that:
>
> 1) We already have a package with equivalent functionality
> 2) The name of this package, unrar-free, might lead users to choose a
> nonfree program due to similarity. Concretely, the nonfree program is
> called "unrar".
>
> Is that correct?
For the equivalence relation of "both being able to open the same
archives", yes. Obviously, unrar-free has a different CLI – that's is
whole shtick, after all – but I'd argue that this doesn't matter,
because the people who prefer CLI over GUI know how to read manpages.
Cheers
next prev parent reply other threads:[~2023-01-13 5:20 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
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 [this message]
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=84b1430354267a6db5c76c1470ab7e932924e2c3.camel@gmail.com \
--to=liliana.prikler@gmail.com \
--cc=52109@debbugs.gnu.org \
--cc=chuanwei.foo@hotmail.com \
--cc=g@xelera.eu \
--cc=kiasoc5@disroot.org \
--cc=leo@famulari.name \
--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).