Re:Re: native-search-paths search-path-specification do not work in glib-or-gtk-build-system
At 2022-02-27 18:58:37, "Maxime Devos" wrote: >tumashu schreef op zo 27-02-2022 om 18:52 [+0800]: >> I want to include CAJA_EXTENSION_DIRS setup in ~/.guix- >> profile/etc/profile file, >> and the below code seem to do not work in glib-or-gtk-build-system > >The native-search-path will only have effect once there's actually a >caja extension in ~/.guix-profile/lib/caja/extensions-2.0. Try >installing caja and caja-extensions in the same profile. by the way, if my system-config enable mate-1.24 desktop type. when I install a different version mate in my home, for example 1.26, which one will be use when I enter my deskop by slim? > >Greetings >maxime.
Re:Re: native-search-paths search-path-specification do not work in glib-or-gtk-build-system
works, thanks very much. -- 发自我的网易邮箱手机智能版 - Original Message - From: "Maxime Devos" To: tumashu , guix Sent: Sun, 27 Feb 2022 11:58:37 +0100 Subject: Re: native-search-paths search-path-specification do not work in glib-or-gtk-build-system tumashu schreef op zo 27-02-2022 om 18:52 [+0800]: >I want to include CAJA_EXTENSION_DIRS setup in ~/.guix- > profile/etc/profile file, > and the below code seem to do not work in glib-or-gtk-build-system The native-search-path will only have effect once there's actually a caja extension in ~/.guix-profile/lib/caja/extensions-2.0. Try installing caja and caja-extensions in the same profile. Greetings maxime.
Re: native-search-paths search-path-specification do not work in glib-or-gtk-build-system
tumashu schreef op zo 27-02-2022 om 18:52 [+0800]: > I want to include CAJA_EXTENSION_DIRS setup in ~/.guix- > profile/etc/profile file, > and the below code seem to do not work in glib-or-gtk-build-system The native-search-path will only have effect once there's actually a caja extension in ~/.guix-profile/lib/caja/extensions-2.0. Try installing caja and caja-extensions in the same profile. Greetings maxime. signature.asc Description: This is a digitally signed message part
native-search-paths search-path-specification do not work in glib-or-gtk-build-system
Hello:
I want to include CAJA_EXTENSION_DIRS setup in ~/.guix-profile/etc/profile
file,
and the below code seem to do not work in glib-or-gtk-build-system
(native-search-paths
(list (search-path-specification
(variable "CAJA_EXTENSION_DIRS")
(files (list "lib/caja/extensions-2.0")))
Any other steps are needed?
cat ~/.guix-profile/etc/profile
# Source this file to define all the relevant environment variables in Bash
# for this profile. You may want to define the 'GUIX_PROFILE' environment
# variable to point to the "visible" name of the profile, like this:
#
# GUIX_PROFILE=/path/to/profile ; \
# source /path/to/profile/etc/profile
#
# When GUIX_PROFILE is undefined, the various environment variables refer
# to this specific profile generation.
export
PATH="${GUIX_PROFILE:-/gnu/store/fial9qbkh215hydkdshw7m025m0hz741-profile}/bin:${GUIX_PROFILE:-/gnu/store/fial9qbkh215hydkdshw7m025m0hz741-profile}/sbin${PATH:+:}$PATH"
export
XDG_DATA_DIRS="${GUIX_PROFILE:-/gnu/store/fial9qbkh215hydkdshw7m025m0hz741-profile}/share${XDG_DATA_DIRS:+:}$XDG_DATA_DIRS"
export
XCURSOR_PATH="${GUIX_PROFILE:-/gnu/store/fial9qbkh215hydkdshw7m025m0hz741-profile}/share/icons${XCURSOR_PATH:+:}$XCURSOR_PATH"
export
GUIX_GTK3_PATH="${GUIX_PROFILE:-/gnu/store/fial9qbkh215hydkdshw7m025m0hz741-profile}/lib/gtk-3.0${GUIX_GTK3_PATH:+:}$GUIX_GTK3_PATH"
export
GST_PLUGIN_SYSTEM_PATH="${GUIX_PROFILE:-/gnu/store/fial9qbkh215hydkdshw7m025m0hz741-profile}/lib/gstreamer-1.0${GST_PLUGIN_SYSTEM_PATH:+:}$GST_PLUGIN_SYSTEM_PATH"
export
GDK_PIXBUF_MODULE_FILE="${GUIX_PROFILE:-/gnu/store/fial9qbkh215hydkdshw7m025m0hz741-profile}/lib/gdk-pixbuf-2.0/2.10.0/loaders.cache"
export
FCITX_ADDON_DIRS="${GUIX_PROFILE:-/gnu/store/fial9qbkh215hydkdshw7m025m0hz741-profile}/lib/fcitx5${FCITX_ADDON_DIRS:+:}$FCITX_ADDON_DIRS"
export
HGEXTENSIONPATH="${GUIX_PROFILE:-/gnu/store/fial9qbkh215hydkdshw7m025m0hz741-profile}/lib/python3.9/site-packages/hgext3rd${HGEXTENSIONPATH:+:}$HGEXTENSIONPATH"
export
GIT_EXEC_PATH="${GUIX_PROFILE:-/gnu/store/fial9qbkh215hydkdshw7m025m0hz741-profile}/libexec/git-core"
export
INFOPATH="${GUIX_PROFILE:-/gnu/store/fial9qbkh215hydkdshw7m025m0hz741-profile}/share/info${INFOPATH:+:}$INFOPATH"
export
EMACSLOADPATH="${GUIX_PROFILE:-/gnu/store/fial9qbkh215hydkdshw7m025m0hz741-profile}/share/emacs/site-lisp${EMACSLOADPATH:+:}$EMACSLOADPATH"
The below is caja's define:
(define-public caja
(package
(name "caja")
(version "1.26.0")
(source
(origin
(method url-fetch)
(uri (string-append "mirror://mate/" (version-major+minor version) "/"
name "-" version ".tar.xz"))
(sha256
(base32
"1m0ai2r8b2mvlr8bqj9n6vg1pwzlwa46fqpq206wgyx5sgxac052"
(build-system glib-or-gtk-build-system)
(arguments
(list
#:configure-flags #~(list "--disable-update-mimedb")
#:tests? #f ; tests fail even with display set
#:phases
#~(modify-phases %standard-phases
(add-before 'check 'pre-check
(lambda _
;; Tests require a running X server.
(system "Xvfb :1 &")
(setenv "DISPLAY" ":1")
;; For the missing /etc/machine-id.
(setenv "DBUS_FATAL_WARNINGS" "0"))
(native-inputs
(list pkg-config
intltool
`(,glib "bin")
xorg-server
gobject-introspection))
(inputs
(list exempi
gtk+
gvfs
libexif
libnotify
libsm
libxml2
mate-desktop
startup-notification))
(native-search-paths
(list (search-path-specification
(variable "CAJA_EXTENSION_DIRS")
(files (list "lib/caja/extensions-2.0")
(home-page "https://mate-desktop.org/;)
(synopsis "File manager for the MATE desktop")
(description
"Caja is the official file manager for the MATE desktop.
It allows for browsing directories, as well as previewing files and launching
applications associated with them. Caja is also responsible for handling the
icons on the MATE desktop. It works on local and remote file systems.")
;; There is a note about a TRADEMARKS_NOTICE file in COPYING which
;; does not exist. It is safe to assume that this is of no concern
;; for us.
(license license:gpl2+)))
Shepherd socket activation
Brendan Tildesley writes: > I'll have another go at making the Pipewire service soon. The last > issue I ran into is that since Guix doesn't use systemd, there is > no socket activation support that Pipewire can use, so I wasn't sure > how to launch it. We can add socket activation in its simplest form to Shepherd. Shepherd will only have to create socket files and listen for activity; on activity it starts an associated service. We don’t need to have it pass sockets or do anything fancy. I’m not a fan of how systemd uses only conventions to associate the socket service with the service that should be activated. In the Shepherd we could define a separate one-shot service that creates the socket (and has Shepherd listen on it), which names other services that would be activated by activity on the socket. -- Ricardo
