Hi Jesse,
Jesse Gibbons skribis:
> If anyone knows why freedink is packaged the way it is and thinks it
> is better that way, I want to know your reasons before I begin to
> attempt to fix this issue, because those reasons could lead me to a
> different approach.
I reviewed the initial
TL;DR The freedink package is defined in a complex way that breaks
guix's custom source build features and the GUI wrapper.
The freedink package wraps the freedink-engine and freedink-data
packages so the resulting executable bin/freedink runs the freedink
engine pointed at the output of
