Bug 1360752 - [rfe] provide a way to read out $basearch
[rfe] provide a way to read out $basearch
Product: Fedora
Classification: Fedora
Component: dnf-plugins-core (Show other bugs)
Unspecified Unspecified
unspecified Severity unspecified
: ---
: ---
Assigned To: Michael Mráka
Fedora Extras Quality Assurance
Depends On:
  Show dependency treegraph
Reported: 2016-07-27 07:59 EDT by Gerd v. Egidy
Modified: 2016-07-29 10:57 EDT (History)
9 users (show)

See Also:
Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2016-07-29 10:57:41 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Gerd v. Egidy 2016-07-27 07:59:00 EDT
Description of problem:

Currently there is no proper way for the user or a script to read out the content of the $basearch variable used by dnf, e.g. in the repo defintion files in /etc/yum.repos.d/

Using "uname -m" doesn't work, it returns e.g. "armv7l" while the proper $basearch is "armhfp".

This was already a problem with yum:
But the solutions provided there don't work with dnf anymore and do not look like stable interfaces to me.

I think "dnf config-manager --dump" should also output basearch.

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1. dnf config-manager --dump | grep basearch

Actual results:

Expected results:
basearch = armhfp
Comment 1 Michael Mráka 2016-07-27 08:28:30 EDT
Created new option for this:

 dnf config-manager --dump-variables

you can combine it with --dump if want both variables and configuration options.

Comment 2 Gerd v. Egidy 2016-07-27 08:55:04 EDT
wow, that was fast. Thank you.
Comment 3 Igor Gnatenko 2016-07-29 10:57:41 EDT
Merged as part of DNF 2.0 release.

Note You need to log in before you can comment on or make changes to this bug.