Bug 1300413 - [packaging] please split pcs to separate RPMs for CLI and GUI
Summary: [packaging] please split pcs to separate RPMs for CLI and GUI
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: pcs
Version: 7.2
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Tomas Jelinek
QA Contact: cluster-qe@redhat.com
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-01-20 17:39 UTC by Jan Pokorný [poki]
Modified: 2020-12-15 07:39 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-12-15 07:39:44 UTC
Target Upstream Version:

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 1176018 0 urgent CLOSED pcs/pcsd should be able to configure pacemaker remote 2021-02-22 00:41:40 UTC
Red Hat Bugzilla 1341114 0 low CLOSED [packaging] pcs should mark known (existing or not) %config files in the spec (/etc/sysconfig/pcsd, /var/lib/pcsd/tokens... 2021-02-22 00:41:40 UTC

Internal Links: 1176018 1341114

Description Jan Pokorný [poki] 2016-01-20 17:39:28 UTC 
Having some 2000 files in a single package is little bit too much.
Moreover, there are people that do not require (or want to have installed)
GUI at all.

Please, do a reasonable split to RPMs for:
- CLI
- non-GUI part of pcsd
- GUI part of pcsd

I believe this is possible (using reasonable cross-dependencies)
and would spare disk space and attack surface for people that
do not care about GUI at all.  There are few SRPMs of pcs size
that don't offer finer granularity deployment-wise.
Comment 1 Jan Pokorný [poki] 2016-01-20 17:51:22 UTC 
+ trademarked logos could be factored out to a subpackage on its own
to allow for wider share of pcs on distros not associated with RH.
Comment 4 RHEL Program Management 2020-12-15 07:39:44 UTC 
After evaluating this issue, there are no plans to address it further or fix it in an upcoming release.  Therefore, it is being closed.  If plans change such that this issue will be fixed in an upcoming release, then the bug can be reopened.
Note You need to log in before you can comment on or make changes to this bug.