Ricardo Wurmus <rek...@elephly.net> writes:
> Mark H Weaver <m...@netris.org> writes:
>
>> Ricardo Wurmus <rek...@elephly.net> writes:
>>
>>> arandr doesn’t work as it needs “xrandr” at runtime. I tried to patch
>>> the sources to replace the path to the “xrandr” binary with a full store
>>> item path, but this wasn’t quite as pretty as I hoped as the arandr
>>> sources don’t define the path once but directly assemble command line
>>> strings in several places. Propagating “xrandr” is the cleaner solution
>>> in my opinion.
>>
>> How about making a wrapper for arandr that sets PATH to find xrandr?
>
> Patch attached:
>
> From 28f0dc229bdba3e53bd101e5acf5e93e4ff7907e Mon Sep 17 00:00:00 2001
> From: Ricardo Wurmus <rek...@elephly.net>
> Date: Sat, 27 Feb 2016 12:00:20 +0100
> Subject: [PATCH] gnu: arandr: Add "xrandr" to inputs.
>
> * gnu/packages/xdisorg.scm (arandr)[inputs]: Add "xrandr".
> [arguments]: Add build phase "make-xrandr-available" to ensure "xrandr"
> executable is found at runtime.
Looks good to me. Please push.
Thanks!
Mark
