From: Chris Hofstaedtler <zeha@debian.org>
To: "Iván Ezequiel Rodriguez" <ivanrwcm25@gmail.com>
Cc: util-linux@vger.kernel.org
Subject: Re: [RFC] pack/unpack: generic archive creation and extraction utilities
Date: Thu, 13 Aug 2026 18:09:32 +0200 [thread overview]
Message-ID: <an3rySqcIaOIlkTU@zeha.at> (raw)
In-Reply-To: <20260813144535.79126-1-ivanrwcm25@gmail.com>
* Iván Ezequiel Rodriguez <ivanrwcm25@gmail.com> [260813 16:45]:
>I realize an optional libarchive dependency may itself be an important
>consideration, so feedback on whether that would be a fundamental
>obstacle would also be very welcome.
>
>Before attempting to adapt anything to util-linux conventions or
>preparing patches, I'd like to know whether commands with this scope
>are something the project would consider in principle.
Purely with my Debian hat on: please put this either into libarchive
or just a new tool. Adding a dependency from util-linux to
libarchive is (from my PoV) not a great idea, especially when the
tools can easily live in another place.
IIRC libarchive's "tar" can already unpack zips and so on...
Best,
Chris
prev parent reply other threads:[~2026-08-13 16:09 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-13 14:45 [RFC] pack/unpack: generic archive creation and extraction utilities Iván Ezequiel Rodriguez
2026-08-13 16:09 ` Chris Hofstaedtler [this message]
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=an3rySqcIaOIlkTU@zeha.at \
--to=zeha@debian.org \
--cc=ivanrwcm25@gmail.com \
--cc=util-linux@vger.kernel.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