gnomeExtensions: Some more cleanup#124315
Conversation
54180b9 to
f47472a
Compare
This comment has been minimized.
This comment has been minimized.
There was a problem hiding this comment.
Yes it very probably is. Nevertheless, this is the "official" name, and thus the name of the automatically packaged extension ¯_(ツ)_/¯
There was a problem hiding this comment.
I would not consider that an official name – it is not used anywhere other than the slug on the extension portal website AFAICT.
|
Regarding passthru, I just recently realized that the manually packaged extensions simply expose |
There was a problem hiding this comment.
This also sounds like something we should not need.
There was a problem hiding this comment.
So my point is, the manually packaged extensions must somehow match the automatically packaged ones in order for overriding to work.
There was a problem hiding this comment.
Could we do it in the other direction – rename the automatically packaged extension instead? Since the names are arbitrary, we might as well use ones that make sense.
There was a problem hiding this comment.
Middle ground: I'd like to keep the pname the same, but I'd be fine with renaming the attribute name of the extensions (pname is almost worthless anyways).
The most promising approach at implementing this would be to key all manually packaged extensions with their UUID as well, so that I can first do the merge/override, and then give them proper names.
There was a problem hiding this comment.
pname is what Repology uses so we should keep it somewhat canonical and reasonable.
I would say the easiest would be adding a section for changing bad slugs in extensionRenames.nix. But adding detection of duplicates based on UUID would be useful when people add a new manually packaged extension so that they choose a correct name.
|
Pushed the fix for the accidental rename as 571d540. |
f47472a to
534187c
Compare
|
Second try, I almost started from scratch. No renames just yet, as they are less important with the improved merging. Personally, I'd like to rename all folders of the manually packaged extensions to use their UUID instead of their pname, but let me know what you think about this first. |
5b8fba9 to
7bbc495
Compare
|
So I went ahead and removed all manual packages that looked like the usual generic boilerplate. @chkno @jtojnar @emanueleperuffo @svsdep @hedning @tu-maurice @benley @Mdsp9070 @ericdallo @alesguzik @eduardosm @jonafato your extensions are affected. Please have a look and comment if any of them can not simply be replaced by the automatic packaging. |
139aeab to
0071880
Compare
1c4c1bd to
1565c24
Compare
|
Let's summarize the discussion so far because the next time I'll have forgotten most of it:
|
90c868b to
37d6219
Compare
37d6219 to
cd67fa3
Compare
cd67fa3 to
5fd0864
Compare
…he others Their keys are now not used directly. Instead, we go the standard route of mapping to the UUID in order to apply the rename procedure. This makes sure the manual override always does the correct thing, and also gives us more consistency overall.
It was never actually referenced anywhere, so technically it was never packaged …
5fd0864 to
3c85c0c
Compare
jtojnar
left a comment
There was a problem hiding this comment.
LGTM. Thanks for bearing with me.
|
Thanks for all the reviews |
Motivation for this change
remove-dropdown-arrows, because it's old and obsolete.Things done
sandboxinnix.confon non-NixOS linux)nix-shell -p nixpkgs-review --run "nixpkgs-review wip"./result/bin/)