Re: Bug#1030683: gnome-shell-extensions-extra: unmaintainable
Hi Jeremy
On 2/9/23 13:15, Jeremy Bícha wrote:
> I am lowering the severity of this bug to allow these extensions to
> reach Debian 12.
thanks you, that is very reasonable as it gives us a bit more time.
please let me re-iterate that I'm perfectly fine with whatever consensus
is reached between ftp-master and gnome-team.
even letting it migrate now, if the consensus is different later on, it
can always be removed before the release.
> I do still think this is RC for Unstable because of
> how it breaks user experiences when new GNOME major releases (like 43
> to 44) happen but that won't happen for Stable.
how about this: if the package would depend on (e.g.) 'gnome-shell >> 43
<< 44', then your requirement would be satisfied, right? and it would be
my burden as the maintainer that I'll need to ensure that all individual
extensions work with 43 at the same time.
the the more technical things, please note that I'm entirely neutral to
whatever way it's going to be packaged.. just providing some inputs.
> You are micro-optimizing. [...] But I do not foresee Debian ever having 75
> source packages for GNOME Shell extensions.
data point: just noticed that gimp-plugin-registry is also bunding the
extensions like this package.
> Does Debian have the latest version of the vertical-workspaces
> extension? It's not possible to answer that with this combined
> package.
for the binary package: would a versioned provides satisfy this case?
> The maintainer did not use multiple tarballs here (which admittedly is
> a bit complicated to set up initially).
right, didn't want to do "all of the things at once" :)
> GNOME, the upstream maintainer for gnome-shell-extensions, has a right
> to define what is GNOME.
totally agree; hence the questions for suggestions - happy to rename it
to whatever suits best.
> All extensions need a minor change for compatibility. Some extensions
> will need major changes. You will force the maintainer of this package
> to either drop incompatible extensions with no warning to people
> running Unstable or Testing, or hold back all the bundled extensions
> because one or more are not yet compatible.
...or (for completness sake) needing me to fix them myself :)
Regards,
Daniel
Reply to: