From: voidlinux-github@inbox.vuxu.org
To: ml@inbox.vuxu.org
Subject: [ISSUE] pax-utils as a dependency to base-minimal in musl edition
Date: Mon, 16 Sep 2019 08:05:34 +0200 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-14489@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1418 bytes --]
New issue by am11 on void-packages repository
https://github.com/void-linux/void-packages/issues/14489
Description:
### System
* xuname:
`Void 4.9.184-linuxkit x86_64-musl GenuineIntel uptodate rF`
* package:
base-minimal
### Expected behavior
A base installation of Void Linux, in both glibc and musl-libc editions, has the tool called ldconfig, which helps applications and other tools to find out which system libraries are installed.
`ldconfig` does pretty much nothing on musl-libc based systems. The alternative is scanelf for musl-libc, which pax-utils package provides.
In minimal Alpine Linux installation, pax-utils is included. The expectation from Void Linux (musl-libc edition) is also to have pax-utils as part of minimal install (docker scenario).
### Actual behavior
There is no usable tools available in base-minimal for system-library introspection.
### Steps to reproduce the behavior
glibc case
```sh
docker run -it voidlinux/voidlinux dash # glibc edition
ldconfig -NvX
# lists the installed system libraries
```
musl-libc
```sh
docker run -it voidlinux/voidlinux-musl dash # glibc edition
ldconfig -NvX
# returns nothing
# it's pretty much a no-op on musl, alternative is 'scanelf'
scanelf
dash: 2: scanelf: not found
xbps-install -S
xbps-install pax-utils
scanelf --ldpath -BF '%f'
# lists the installed system libraries
```
next reply other threads:[~2019-09-16 6:05 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-16 6:05 voidlinux-github [this message]
2019-09-28 22:57 ` voidlinux-github
2019-09-28 22:58 ` voidlinux-github
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=gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-14489@inbox.vuxu.org \
--to=voidlinux-github@inbox.vuxu.org \
--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).