<blu_>I'm trying to write xorg-configuration-file (a gexp defined in xorg service) out to an actual file in /etc/X11 from my operating system config, but I seem to have no idea what I'm doing. Any ideas how this should work?
<blu_>it's a computed-file actually** but that contains a gexp which I presume I need to gexp->file on
<ng0>btw: I might or might not get the chance to introduce some people to GuixSD (among other systems) if my hackerspace participates in this GNU/Linux Desktop Day the Linux Foundation has announced for next month
<thomasd>but maybe some more tools for source code manipulation during the buid could be useful
<efraim>Normally multiline means patch, its what I ended up with for onionshare with patching the setup.py
<thomasd>also inserting something is more complicated than it should be, I thnk
<thomasd>I've done it by looking for the line before/after which I want to insert using substitute*, and then adding that line again in the substitute, + what I want to insert. (not sure this is more light-weight than adding a patch ;-) )
<Petter>efraim: I don't see a patch in onionshare, only substitutes.
<efraim>Oh, I must've taken the patch out during one of the upgrades
<Petter>You don't happen to have it, or another example, nearby? I'm looking for a complete process of writing and applying a patch in a recipe.
<Petter>So far all i see are (patches (search-patches...
<efraim>(patches (search-patches is how the patch gets applied
<efraim>The easiest way I've found for writing patches is to take the source tarball, unpack it, git init, git add ., git commit -m 'start', and then hack in my patch
<Petter>I see. Are the patches then stored somewhere as files?
<ng0>gnu/packages/patches OR/AND in the topdir of GUIX_PACKAGE_PATH
<ng0>so I have a file without a version name which is downloaded in a package definition as an input. does this mean it ends up with just the name in the store, like /gnu/store/hashthing-foo.extension?