Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Bug 1406560

Summary: split out GTK+ support to the subpackage
Product: Red Hat Enterprise Linux 7 Reporter: Honza Silhan <jsilhan>
Component: libpeasAssignee: Igor Gnatenko <ignatenko>
Status: CLOSED DEFERRED QA Contact: Desktop QE <desktop-qa-list>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 7.3CC: bbreard, ignatenko, jreznik, klember, lfriedma, tpelka, walters
Target Milestone: rcKeywords: Reopened
Target Release: 7.3   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-01-19 17:01:35 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: 1410135    

Description Honza Silhan 2016-12-20 23:12:52 UTC 
would it be possible to split the package same as in Fedora 26 [1] to not require whole gtk by default.

[1] http://pkgs.fedoraproject.org/cgit/rpms/libpeas.git/commit/?id=dd1b72dd88584e339686a2c1c985a04a883ea212
Comment 4 Honza Silhan 2017-01-10 12:51:57 UTC 
Note: the repackaging will not break current components depending on libpeas as they require gtk explicitly when they really need it.
Comment 5 Kalev Lember 2017-01-12 14:02:56 UTC 
I suspect we may find a few apps that use PeasGtk through gobject-introspection/Python and would need to have the new libpeas-gtk dependency manually added. Would probably be a good idea to try to find out what apps (if any) are doing that before pushing the libpeas/libpeas-gtk split out.
Comment 6 Kalev Lember 2017-01-12 14:39:10 UTC 
I looked through of all the packages in F25 that require libpeas python loaders and apparently they all explicitly link with libpeas-gtk as well. Only thing that stuck out where dependencies might need updating is gtkd. gtkd is neither in RHEL nor EPEL though, so it shouldn't block changing this in RHEL.

I'll go and merge the libpeas/libpeas-gtk split that Igor did to F25 now, so that it can get a bit testing.
Comment 7 Bastien Nocera 2017-01-12 16:22:56 UTC 
This is too invasive a change for 7.3 when a rebase is due in 7.4. See bug 1387015.
Comment 8 Red Hat Bugzilla Rules Engine 2017-01-12 16:23:03 UTC 
Development Management has reviewed and declined this request. You may appeal this decision by reopening this request.
Comment 11 Bastien Nocera 2017-01-18 13:31:02 UTC 
Reassigning to Igor who's going to handle this for 7.3.z.
Comment 13 Igor Gnatenko 2017-01-18 14:22:35 UTC 
1. All of packages which needs GTK+ they link by SONAME, so during update
   it will be just pulled automatically.
2. All of packages which require Python loader are requiring GTK+ support,
   so nothing will break.
    
We can't split Python loader into different subpackage because this will require modifications of existing packages.