Hello,
I'm attempting to build and install a package definition for this program:
https://github.com/milgra/sov
Following the examples in the Guix manual, and so far so good, except that
build tests fail with this output after running `guix package --install-from-
file=sov.scm`:
> Fontconfig error: No writable cache directories
I'm still inexperienced with Guile Scheme & writing custom package definitions,
and I'm not sure how to fix this. I've attached the .scm file for reference.
Maybe I've done something wrong along the way?
(define-module (config packages sov)
#:use-module (gnu packages)
#:use-module (gnu packages build-tools)
#:use-module (gnu packages cmake)
#:use-module (gnu packages fontutils)
#:use-module (gnu packages freedesktop)
#:use-module (gnu packages gl)
#:use-module (gnu packages image)
#:use-module (gnu packages llvm)
#:use-module (gnu packages ninja)
#:use-module (gnu packages pkg-config)
#:use-module (gnu packages xdisorg)
#:use-module (guix build-system meson)
#:use-module (guix git-download)
#:use-module ((guix licenses) #:prefix license:)
#:use-module (guix packages)
#:use-module (guix utils))
;;(define-public sov
(let ((version "0.94")
(revision "0")
(commit "5beff04194dd675db121c13dec738bc0711b0107"))
(package
(name "sov")
(version (git-version version revision commit))
(source (origin
(method git-fetch)
(uri (git-reference
(url "https://github.com/milgra/sov/";)
(commit commit)))
(file-name (git-file-name name version))
(sha256
(base32
"0k39pr83yqpzmbk0a8a302gxmsdgpjdlvm2dijyp2yvjdn3xl0i6"))))
(build-system meson-build-system)
(native-inputs
(list clang meson ninja cmake pkg-config fontconfig))
(inputs
(list libpng freetype libglvnd glew wayland wayland-protocols libxkbcommon))
(home-page "https://github.com/milgra/sov/";)
(synopsis "An overlay that shows schemas for all workspaces to make navigation in sway easier.")
(description "Sway overview is an overview application for the sway tiling window manager. Tiling window managers are about simplicity so by default they don't have any kind of overview feature. It is okay under five workspaces because you can just remember where specific windows were opened but over 5 workspaces it can get really complicated. Sway overview draws a schematic layout of all your workspaces on each output. It contains all windows, window titles and window contents. Thumbnail based overview solutions can become confusing quickly when the thumbnails become too small to recognize, sway overview won't. The common usage of Sway overview is to bound its appereance to the desktop switcher buttons with a little latency. Sway overview can be structured via html, styled via css.")
(license license:gpl3)))
;;)
