<anonymiss>Are there plans to get grsec features into guixsd? i know the linux-libre kernel can get patched with grsec because i stsrted using the hardened-gentoo with deblob (libre) set on gentoo, but i imagine it to be, if doable, a long project and one i don't feel ready for contributing atm
<civodul>roelj: dunno, just a "standard" 3-year old SSD, nothing fancy
<davexunit>so, here's a potentially crazy idea that I want to run past you folks:
<davexunit>starting from a store item closure, find and replace all store item references to use non-absolute paths and provide a wrapper script to setup the necessary environment variables to make it work.
<davexunit>there's a cool thing going down in January called the "Lisp Game Jam", and I'd like to use my game engine and provide binaries for those that just want to try my game without going through all the manual compilation.
<davexunit>I can easily make a guix package for the game.
<davexunit>but making a binary tarball that someone could just unpack in an arbitrary directory as an unprivileged user and run is an interesting challenge
<fps>and i think it worked for me after installing e.g. redshift
<lfam>I have to apologize for the state of the bug report I filed on python-urwid (22137). In Mutt, the attachment is rendered as the body of the message but it looks like in other places it is just an attachment on an empty message.
<sneek>alezost, civodul says: it would be good to see if anything's missing in our GRUB support that prevents you from using it and specifying the other OS to boot
<alezost>sneek: later tell civodul: about grub and dual boot: I don't really know, I didn't try the default GuixSD way of using grub because I don't like that it reinstalls grub after each system reconfiguring
<mark_weaver>gcc-toolchain includes 'gcc', 'binutils', 'glibc', and also something called 'ld-wrapper' which is needed to add the necessary rpaths so that the shared libraries can be found in their non-standard places.
<mark_weaver>and it's not always the case that you want something like 'ld-wrapper' to automatically add those rpaths for you.
<shao>ah okay. yeah now I remember reading something about using a chroot thing
<Digit>i still have much docs to read to understanding, but time to stop [(for a break too)] n ask for pointers... how far away am i with this so far? first guix packaging attempt (first any packaging attempt), cdrkit http://dpaste.com/2NHVM84 am i even close?
<davexunit>Digit: provided the build system doesn't need much massaging, it looks like you're on the right track!
<fhmgufs>At the moment I'm building guix again (After I did a binary installation, I wanted to build it myself now. Is it normal, that it takes so long to build (or whatever it's doing) the package definitions (GUILEC: gnu/packages/*.go)?
<lfam>fhmgufs: The first time will probably take a little while. Subsequent runs will only need to recompile the updated modules so it will go faster.
<mark_weaver>fhmgufs: yes, it's normal. btw, make sure to pass --localstatedir=/var to configure when building guix from source code.
<alezost>fps: by default Guix repl is started as a server, so the second one is trying to be started on the same port. You can either (setq guix-use-guile-server nil) or change `guix-default-port' to another value for the second instance
<alezost>civodul: I can rollback with a bit of manual work: I have an entry in my grub.cfg with some system generation number, so if I want to switch to a previous generation, I just edit this number directly in grub, and boot to it
<fps>i guess i can leave the guix build environment first, but that shouldn't hurt either, right?
<wingo>davexunit: is /etc the right place for the .pem? would an administrator be able to update the .pem in place or would they have to use the guix configuration mechanism, and if they had to use guix would it be ok?
<wingo>i could put it in /var if that were the right thing
<davexunit>wingo: for state like that, I think /var/lib might be better.
<davexunit>to replace it they could use whatever they wanted, because this is stateful stuff that guix itself doesn't manage.
<wingo>davexunit: you assume an administrator would like to manage this file outside of guix