Bug 1506935

Summary:	RFE: configure to read /etc/config.site?
Product:	[Fedora] Fedora	Reporter:	Pavel Raiskup <praiskup>
Component:	autoconf	Assignee:	Ondrej Dubaj <odubaj>
Status:	CLOSED WONTFIX	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	rawhide	CC:	extras-qa, kasal, mschmidt, praiskup, ttomecek
Target Milestone:	---	Keywords:	FutureFeature
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:	1506655	Environment:
Last Closed:	2021-10-06 11:42:43 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:	1506655
Bug Blocks:

Description Pavel Raiskup 2017-10-27 08:25:23 UTC

+++ This bug was initially created as a clone of Bug #1506655 +++
--- Additional comment from Pavel Raiskup on 2017-10-27 10:20:50 CEST ---
...
FTR, configure accepts also also /usr/etc/config.site, but that's still
under /usr.  Should be fixed upstream so that --sysconfdir affects the
"user-configurable" location.
...


Maybe, if /usr/share/config.site affects $sysconfdir, configure could go
and read $sysconfdir/config.site.

This all is just an idea.  I'm not sure whether it is realizable.

Comment 1 Fedora Admin user for bugzilla script actions 2021-07-01 15:22:10 UTC

This package has changed maintainer in Fedora. Reassigning to the new maintainer of this component.

Comment 2 Ondrej Dubaj 2021-10-04 09:34:33 UTC

AFAIK, --sysconfdir affects the "user-configurable" location in the current version 2.71. I actually do not understand what is the point of this tracker, can you please explain what is aimed ? If the idea is already orphaned, we can probably close this bug. Thanks.

Comment 3 Ondrej Dubaj 2021-10-06 11:42:43 UTC

According to the low priority of this request and as it did not bother any user for years, I am closing this tracker. If you think this issue should be handled and investigated, feel free to reopen it.