gnome-shell/src/gnome-shell-extension-prefs.in

#!/bin/sh

if [ -z "$GI_TYPELIB_PATH" ]; then
    export GI_TYPELIB_PATH=@pkglibdir@
else
    export GI_TYPELIB_PATH=@pkglibdir@:$GI_TYPELIB_PATH
fi

if [ -z "$LD_LIBRARY_PATH" ] ; then
    export LD_LIBRARY_PATH=@pkglibdir@
else
    export LD_LIBRARY_PATH=@pkglibdir@:$LD_LIBRARY_PATH
fi

@GJS_CONSOLE@ -I @pkgdatadir@/js -c "const Main = imports.extensionPrefs.main; Main.main(ARGV);" "$@"
portability: use /bin/sh instead of /bin/bash There is nothing requiring bash specific features in this script, so just use /bin/sh which is portable amongst all Unices. https://bugzilla.gnome.org/show_bug.cgi?id=679847 2012-07-13 07:51:24 -04:00			`#!/bin/sh`
Add a new tool, 'gnome-shell-extension-prefs', which can configure extensions A new tool, 'gnome-shell-extension-prefs' can load a new entry point from extensions, 'prefs.js', which has an entry point to return a GTK+ widget. This allows extensions to have their own preferences dialog, without each extension needing to ship its own Python script and .desktop file. https://bugzilla.gnome.org/show_bug.cgi?id=668429 2012-01-18 21:21:56 -05:00
Fix typo in gnome-shell-extension-prefs Environment variables should be checked for zero length, instead of non-zero. This prevented the script to run correctly in a jhbuild shell for example. https://bugzilla.gnome.org/show_bug.cgi?id=693031 2013-02-01 13:33:20 -05:00			`if [ -z "$GI_TYPELIB_PATH" ]; then`
Add a new tool, 'gnome-shell-extension-prefs', which can configure extensions A new tool, 'gnome-shell-extension-prefs' can load a new entry point from extensions, 'prefs.js', which has an entry point to return a GTK+ widget. This allows extensions to have their own preferences dialog, without each extension needing to ship its own Python script and .desktop file. https://bugzilla.gnome.org/show_bug.cgi?id=668429 2012-01-18 21:21:56 -05:00			`export GI_TYPELIB_PATH=@pkglibdir@`
			`else`
			`export GI_TYPELIB_PATH=@pkglibdir@:$GI_TYPELIB_PATH`
			`fi`

Fix typo in gnome-shell-extension-prefs Environment variables should be checked for zero length, instead of non-zero. This prevented the script to run correctly in a jhbuild shell for example. https://bugzilla.gnome.org/show_bug.cgi?id=693031 2013-02-01 13:33:20 -05:00			`if [ -z "$LD_LIBRARY_PATH" ] ; then`
Add a new tool, 'gnome-shell-extension-prefs', which can configure extensions A new tool, 'gnome-shell-extension-prefs' can load a new entry point from extensions, 'prefs.js', which has an entry point to return a GTK+ widget. This allows extensions to have their own preferences dialog, without each extension needing to ship its own Python script and .desktop file. https://bugzilla.gnome.org/show_bug.cgi?id=668429 2012-01-18 21:21:56 -05:00			`export LD_LIBRARY_PATH=@pkglibdir@`
			`else`
			`export LD_LIBRARY_PATH=@pkglibdir@:$LD_LIBRARY_PATH`
			`fi`

			`@GJS_CONSOLE@ -I @pkgdatadir@/js -c "const Main = imports.extensionPrefs.main; Main.main(ARGV);" "$@"`