From: Dennis Schridde <devurandom@gmx.net>
To: gentoo-dev@lists.gentoo.org
Cc: "Hanno Böck" <hanno@gentoo.org>
Subject: Re: [gentoo-dev] Package up for grabs: app-arch/unar
Date: Mon, 09 Dec 2019 19:56:40 +0100 [thread overview]
Message-ID: <2294526.RmF9JxlU36@ernie> (raw)
In-Reply-To: <20191209130302.21b25d9b@computer>
[-- Attachment #1: Type: text/plain, Size: 1059 bytes --]
On Montag, 9. Dezember 2019 13:03:02 CET Hanno Böck wrote:
> It's an archive unpacker written in objective C, which makes it
> dependency-heavy (particularly requires gcc compiled with objc).
> I originally got interested because it was the only free unpacker
> capable of handling modern rar archives. However libarchive does that
> these days, so I don't see a strong need for unar any more.
Thanks for that hint!
app-arch/unar currently seems to be the only free choice for kde-apps/
kdeutils-meta-19.08.3[rar]:
rar? ( || (
app-arch/rar
app-arch/unrar
app-arch/unar
) )
Does anyone know, does kde-apps/ark (for which kdeutils-meta depends on the
rar implementations) also support app-arch/libarchive for RAR files? Is any
useflag needed to get RAR support in libarchive?
If kde-apps/ark does support unpacking RAR files with app-arch/libarchive,
could it please be added to that dependency list? Then app-arch/unar could be
removed from my system.
--Dennis
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 659 bytes --]
next prev parent reply other threads:[~2019-12-09 19:22 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-09 12:03 [gentoo-dev] Package up for grabs: app-arch/unar Hanno Böck
2019-12-09 18:56 ` Dennis Schridde [this message]
2019-12-10 10:36 ` Hanno Böck
-- strict thread matches above, loose matches on Subject: below --
2024-02-17 9:52 David Seifert
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=2294526.RmF9JxlU36@ernie \
--to=devurandom@gmx.net \
--cc=gentoo-dev@lists.gentoo.org \
--cc=hanno@gentoo.org \
/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