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: kiasoc5 <kiasoc5@disroot.org>, Giovanni Biscuolo <g@xelera.eu>,
	Foo Chuan Wei <chuanwei.foo@hotmail.com>,
	52109@debbugs.gnu.org, zimoun <zimon.toutoune@gmail.com>
Subject: [bug#52109] Mention bsdcat, bsdcpio and bsdtar in description of libarchive
Date: Sun, 22 Jan 2023 14:36:18 -0500	[thread overview]
Message-ID: <87edrm1hvx.fsf@gmail.com> (raw)
In-Reply-To: <54d6f7d65b6ece07dcd758449fd833f3290f44a4.camel@gmail.com> (Liliana Marie Prikler's message of "Sun, 22 Jan 2023 18:44:45 +0100")

Hi Liliana,

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

> Am Sonntag, dem 22.01.2023 um 16:09 +0100 schrieb zimoun:
>> Hi,
>> 
>> On Sat, 21 Jan 2023 at 18:59, Liliana Marie Prikler
>> <liliana.prikler@gmail.com> wrote:
>> 
>> > > Please find attach the patch. :-)  If it appears to you fine,
>> > > could you merge it?
>> > 
>> > Hmm, I fear that this line doesn't do much except helping folk to
>> > grep for "bsdtar" et al.  Should we perhaps explain in a sentence
>> > or two what those commands do?
>> 
>> It is not ’grep’ but “guix search” so it is only an internal SEO. ;-)
>> 
>> From my point of view, some explanations about what these commands do
>> are done by the man pages.
>> 
>> Well, this trivial patch is just a quick workaround at 2 levels. 
>> One, because Guix File Search [1] is almost done but not very popular
>> yet.
> Fair enough.
>
>> Two, because this libarchive should be split into 2 different
>> packages or outputs: one for the library itself and another for the
>> commands.
>> 
>> 1: <https://yhetil.org/guix/87pmd1r8kt.fsf@gmail.com>
> Splitting libarchive outputs is sadly a core-updates change, but we
> could hide the existing one and add a user-facing one with the split if
> that's what you desire.  I don't think adding a package for just the
> tools has merits.
>
>> However, if a table containing what these utilities do seems
>> appropriated, here the description from the Debian package
>> ’libarchive-tools’:
>> 
>> --8<---------------cut here---------------start------------->8---
>> The bsdtar program is the default system 'tar' program used on
>> FreeBSD. bsdtar uses the libarchive library as a backend which does
>> all of the work for reading and writing archives in various formats.
>> 
>> The bsdcpio program is the default system 'cpio' program used on
>> FreeBSD. bsdcpio uses the libarchive library as a backend which does
>> all of the work for reading and writing archives in various formats
>> 
>> The bsdcat program reads archived data from files or from its
>> standard input and uses the libarchive library to decompresses it to
>> its standard output. It may be used for viewing the contents of
>> archives or for passing it to other tools for further processing.
>> --8<---------------cut here---------------end--------------->8---
> I think these could be shortened as follows:
>
> This package/the 'bin' output also provides
> @itemize
> @item @command{bsdtar} and @command{bsdcpio} to pack/unpack archives
> like @command{tar} and @command{cpio} respectively, and
> @item @command{bsdcat} to concatenate files like @command{cat} does,
> while transparently unpacking archives.
> @end itemize

Like Simon, I think just mentioning the commands solve the lack of
discovery problem that they reported about these commands; the details
themselves can be further looked up by users via the manpages or --help
output, since the above description wouldn't provide much more than what
can be guessed already.  I pushed Simon's suggested change.

-- 
Thanks,
Maxim




  reply	other threads:[~2023-01-22 19:37 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
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 [this message]
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=87edrm1hvx.fsf@gmail.com \
    --to=maxim.cournoyer@gmail.com \
    --cc=52109@debbugs.gnu.org \
    --cc=chuanwei.foo@hotmail.com \
    --cc=g@xelera.eu \
    --cc=kiasoc5@disroot.org \
    --cc=liliana.prikler@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).