You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: pkgs/desktops/gnome/extensions/README.md
+14-9Lines changed: 14 additions & 9 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,26 +1,31 @@
1
1
# GNOME Shell extensions
2
2
3
-
All extensions are packaged automatically. They can be found in the `pkgs.gnomeXYExtensions` for XY being a GNOME version. The package names are the extension’s UUID, which can be a bit unwieldy to use. `pkgs.gnomeExtensions` is a set of manually curated extensions that match the current `gnome.gnome-shell` versions. Their name is human-friendly, compared to the other extensions sets. Some of its extensions are manually packaged.
3
+
All extensions are packaged automatically. They can be found in the `pkgs.gnomeXYExtensions` for XY being a GNOME version. The package names are the extension’s UUID, which can be a bit unwieldy to use. `pkgs.gnomeExtensions` is a set of manually curated extensions that match the current `pkgs.gnome-shell` versions. Their name is human-friendly, compared to the other extensions sets. Some of its extensions are manually packaged.
4
4
5
5
## Automatically packaged extensions
6
6
7
7
The actual packages are created by `buildGnomeExtension.nix`, provided the correct arguments are fed into it. The important extension data is stored in `extensions.json`, one line/item per extension. That file is generated by running `update-extensions.py`. Furthermore, the automatic generated names are dumped in `collisions.json` for manual inspection. `extensionRenames.nix` contains new names for all extensions that collide.
8
8
9
9
### Extensions updates
10
10
11
-
For everyday updates,
11
+
#### For everyday updates,
12
12
13
13
1. Run `update-extensions.py`.
14
14
2. Update `extensionRenames.nix` according to the comment at the top.
15
15
16
-
For GNOME updates,
16
+
#### To package the extensions for new GNOME version,
17
17
18
-
1. Add a new `gnomeXYExtensions` set
19
-
2. Remove old ones for GNOME versions we don’t want to support any more
20
-
3. Update `supported_versions` in `./update-extensions.py` and re-run it
21
-
4. Change `gnomeExtensions` to the new version
22
-
5. Update `./extensionsRenames.nix` accordingly
23
-
6. Update `all-packages.nix` accordingly (grep for `gnomeExtensions`)
18
+
1. Add a new `gnomeXYExtensions` set in `default.nix`.
19
+
2. Update `all-packages.nix` accordingly. (grep for `gnomeExtensions`)
20
+
3. Update `supported_versions` in `update-extensions.py`.
21
+
4. Follow the [For everyday updates](#for-everyday-updates) section.
22
+
23
+
#### For GNOME updates,
24
+
25
+
1. Follow the [To package the extensions for new GNOME version](#to-package-the-extensions-for-new-gnome-version) section if required.
26
+
2. Update `versions_to_merge` variable in `./update-extensions.py`.
27
+
3. Run `update-extensions.py --skip-fetch`, and update `extensionRenames.nix` according to the comment at the top.
28
+
4. Update `gnomeExtensions` in `default.nix` to the new versions.
0 commit comments