Github messages for voidlinux
 help / color / mirror / Atom feed
From: ahesford <ahesford@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: New package: uutils-0.0.24
Date: Mon, 05 Feb 2024 12:39:02 +0100	[thread overview]
Message-ID: <20240205113902.CC6B324B47@inbox.vuxu.org> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-48534@inbox.vuxu.org>

[-- Attachment #1: Type: text/plain, Size: 1110 bytes --]

New comment by ahesford on void-packages repository

https://github.com/void-linux/void-packages/pull/48534#issuecomment-1926785723

Comment:
This package is misnamed. Normally it should be `coreutils`, which obviously conflicts, so maybe `uutils-coreutils` is a better choice.

I find the documentation very opaque, either because it's missing critical information or because I'm looking for critical information on a phone. The documentation I did find says that "uutils includes a multi-call binary from which the utils can be invoked", but does not say that uutils *is comprised of* a multi-call binary. This makes it sound like the multi-call binary is an optional component of a package that also provides individual commands.

Please confirm that the single executable installed by this package *is* the multi-call executable and can (should) be run similarly to busybox. In particular, I want to ensure that running `/usr/bin/coreutils` won't "helpfully" do something destructive like unpack a bunch of commands or make a bunch of symlinks that would interfere with the system `coreutils` package.

  parent reply	other threads:[~2024-02-05 11:39 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-05  5:18 [PR PATCH] " caughtquick
2024-02-05  5:31 ` caughtquick
2024-02-05  5:38 ` oreo639
2024-02-05  5:39 ` oreo639
2024-02-05  5:40 ` oreo639
2024-02-05  5:42 ` oreo639
2024-02-05  5:50 ` caughtquick
2024-02-05  5:50 ` caughtquick
2024-02-05  5:59 ` oreo639
2024-02-05  6:00 ` oreo639
2024-02-05  6:00 ` oreo639
2024-02-05  6:03 ` oreo639
2024-02-05  6:03 ` oreo639
2024-02-05  6:04 ` oreo639
2024-02-05  6:11 ` oreo639
2024-02-05  6:15 ` oreo639
2024-02-05  6:16 ` oreo639
2024-02-05  6:16 ` oreo639
2024-02-05 11:39 ` ahesford [this message]
2024-02-05 16:29 ` caughtquick
2024-05-06  1:46 ` github-actions

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=20240205113902.CC6B324B47@inbox.vuxu.org \
    --to=ahesford@users.noreply.github.com \
    --cc=ml@inbox.vuxu.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;
as well as URLs for NNTP newsgroup(s).