Bug 1095727

Summary: Remove dependency on erlang-wx from erlang-reltool
Product: [Fedora] Fedora Reporter: Peter Lemenkov <lemenkov>
Component: erlangAssignee: Peter Lemenkov <lemenkov>
Status: CLOSED WONTFIX QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: rawhideCC: erlang, lemenkov, rhbugs, s
Target Milestone: ---Keywords: FutureFeature
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2026-03-07 13:41:25 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:    
Bug Blocks: 784693, 1161922    

Description Peter Lemenkov 2014-05-08 12:33:40 UTC
Subj

Comment 1 Jaroslav Reznik 2015-03-03 15:47:26 UTC
This bug appears to have been reported against 'rawhide' during the Fedora 22 development cycle.
Changing version to '22'.

More information and reason for this action is here:
https://fedoraproject.org/wiki/Fedora_Program_Management/HouseKeeping/Fedora22

Comment 2 Peter Lemenkov 2026-03-07 13:40:50 UTC
Closing this ticket. The original motivation was to enable a trimmed-down Erlang runtime without GUI dependencies (wx/wxWidgets) for server-oriented deployments like CentOS/EPEL.

Since then, the situation has changed significantly:

1. We now ship a full Erlang distribution in CentOS via the Messaging SIG, so the "no GUI deps" constraint no longer applies to the primary use case.

2. Splitting these packages into base and -gui subpackages would add significant spec complexity and ongoing maintenance burden for a use case nobody has requested in over 10 years.

3. These applications (debugger, dialyzer, et, observer, reltool) are tightly coupled to wx in upstream OTP — separating the GUI components cleanly would require ongoing downstream effort with each Erlang release.

No external requests or duplicates have been filed since 2014. If a need arises in the future, this can be revisited.