(add FPC PR) |
(go live) |
||
Line 1: | Line 1: | ||
<!-- The actual name of your proposed change page should look something like: Changes/Your_Change_Proposal_Name. This keeps all change proposals in the same namespace --> | <!-- The actual name of your proposed change page should look something like: Changes/Your_Change_Proposal_Name. This keeps all change proposals in the same namespace --> | ||
Line 23: | Line 17: | ||
== Current status == | == Current status == | ||
[[Category: | [[Category:ChangeReadyForWrangler]] | ||
<!-- When your change proposal page is completed and ready for review and announcement --> | <!-- When your change proposal page is completed and ready for review and announcement --> | ||
<!-- remove Category:ChangePageIncomplete and change it to Category:ChangeReadyForWrangler --> | <!-- remove Category:ChangePageIncomplete and change it to Category:ChangeReadyForWrangler --> | ||
Line 65: | Line 59: | ||
** make `gnome-shell` `Provides: gnome-shell(api) == MAJOR_VER` to make the implementation of the generator easier | ** make `gnome-shell` `Provides: gnome-shell(api) == MAJOR_VER` to make the implementation of the generator easier | ||
** Get this package pulled in by `redhat-rpm-config` | ** Get this package pulled in by `redhat-rpm-config` | ||
** Optionally get this into `epel-rpm-macros` for EPEL 10 | |||
** Provide a COPR for other developers to test | ** Provide a COPR for other developers to test | ||
Revision as of 18:04, 19 December 2024
GNOME Shell extension Dependency Generator
Summary
Implement a dependency generator for GNOME Shell extensions that would make the binary RPM depend on the correct versions of GNOME Shell
Owner
- Name: Michel Lind, Neal Gompa
- Email: michel@michel-slm.name, ngompa13@gmail.com
Current status
- Targeted release: Fedora Linux 42
- Last updated: 2024-12-19
- [Announced]
- [<will be assigned by the Wrangler> Discussion thread]
- FESCo issue: <will be assigned by the Wrangler>
- Tracker bug: <will be assigned by the Wrangler>
- Release notes tracker: <will be assigned by the Wrangler>
Detailed Description
GNOME Shell extensions ship with a metadata.json
that lists the supported versions of GNOME Shell. This data is currently unused when packaging an extension, unless the package maintainer explicitly transfer this information to the spec -- and then keeps it up to date.
With this Change Proposal implemented, the binary RPM would automatically declare its dependency on the right versions of GNOME Shell, ensuring that we will discover after mass rebuild if some extensions need to be updated because they will FTI.
Feedback
Benefit to Fedora
This will result in an improved user experience for our users, because extensions that install are now more likely to work.
It will also help extension packagers, as they get early signal that an extension needs to be updated, by getting a FTI bug not long after the mass rebuild is complete.
Scope
- Proposal owners:
- Implement a dependency generator and package it as
gnome-shell-extension-rpm-macros
- make
gnome-shell
Provides: gnome-shell(api) == MAJOR_VER
to make the implementation of the generator easier - Get this package pulled in by
redhat-rpm-config
- Optionally get this into
epel-rpm-macros
for EPEL 10 - Provide a COPR for other developers to test
- Implement a dependency generator and package it as
- Other developers:
- Test your package by explicitly adding the new dependency generator package as a
BuildRequires
and dropping theRequires
ongnome-shell
- If that works, once the new package is in Fedora and pulled in by
redhat-rpm-config
, you may (but do not have to) drop theRequires
ongnome-shell
as it will be redundant
- Test your package by explicitly adding the new dependency generator package as a
- Release engineering: #Releng issue number
- Policies and guidelines: FPC #1425
This should only land after implementation is done
- Trademark approval: N/A (not needed for this Change)
- Alignment with the Fedora Strategy:
Upgrade/compatibility impact
N/A. This change would be transparent to packagers and end-users - it will allow packagers to clean up their spec by removing the explicit Requires
on gnome-shell
but that is optional
Early Testing (Optional)
Do you require 'QA Blueprint' support? N
How To Test
Extension packagers will be able to test against the COPR containing the new dependency generator
User Experience
Dependencies
This requires changes to gnome-shell
and optionally redhat-rpm-config
. The former significantly eases implementation, as it allows a 1:1 mapping between the version listed in metadata.json
and what we express in the binary RPM. The latter is required to make this transparent to other packagers; if that change does not go through this becomes a self-contained change and extension maintainers can opt in by BR-ing the package
Contingency Plan
- Contingency mechanism: (What to do? Who will do it?)
If the dependency generator turns out to be very buggy, we can stop pulling it in redhat-rpm-config
- Contingency deadline:
Beta freeze
- Blocks release? No
Documentation
N/A