From 4e02eae70e292382adc1a2108ccf3b2423262479 Mon Sep 17 00:00:00 2001 From: Jan Tojnar Date: Fri, 26 Apr 2024 23:12:01 +0200 Subject: doc/gnome: Use `wrapGApps*` hook for referring to the hook family --- doc/build-helpers/special/fhs-environments.section.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'doc/build-helpers/special') diff --git a/doc/build-helpers/special/fhs-environments.section.md b/doc/build-helpers/special/fhs-environments.section.md index 918d1e8c2951d..b87bb97278576 100644 --- a/doc/build-helpers/special/fhs-environments.section.md +++ b/doc/build-helpers/special/fhs-environments.section.md @@ -57,4 +57,4 @@ You can create a simple environment using a `shell.nix` like this: Running `nix-shell` on it would drop you into a shell inside an FHS env where those libraries and binaries are available in FHS-compliant paths. Applications that expect an FHS structure (i.e. proprietary binaries) can run inside this environment without modification. You can build a wrapper by running your binary in `runScript`, e.g. `./bin/start.sh`. Relative paths work as expected. -Additionally, the FHS builder links all relocated gsettings-schemas (the glib setup-hook moves them to `share/gsettings-schemas/${name}/glib-2.0/schemas`) to their standard FHS location. This means you don't need to wrap binaries with `wrapGAppsHook`. +Additionally, the FHS builder links all relocated gsettings-schemas (the glib setup-hook moves them to `share/gsettings-schemas/${name}/glib-2.0/schemas`) to their standard FHS location. This means you don't need to wrap binaries with `wrapGApps*` hook. -- cgit 1.4.1