0

I'm working on a project trying to identify components installed on a linux distribution (for instance Alpine) using built in package managers.

bash-5.0# apk list

usl-1.1.22-r3 x86_64 {musl} (MIT) [installed]
bash-5.0.0-r0 x86_64 {bash} (GPL-3.0-or-later) [installed]
libproc-3.3.15-r0 x86_64 {procps} (GPL-2.0 LGPL-2.1+) [installed]
su-exec-0.2-r0 x86_64 {su-exec} (MIT) [installed]
**libc-utils-0.7.1-r0 x86_64 {libc-dev} (BSD) [installed]**

using commands like apk list, we get basic metadata information like component, semantic versions and installed architectures, but in cases where the upstream libraries come from a noarch scheme, they adapt to the architecture of the system on which the package is installed.

Is there any way to actually find out what the upstream architecture is from the package manager utilities?

Consider libc-utils as an example package, which is a noarch package, but gets installed as a x86_64 package on the system.

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Browse other questions tagged or ask your own question.