<Apteryx>After investigating man-db sources a bit, I know for sure that to generate the manpages db files (*.dir), we have to pass $MANPATH as an argument.
<kadintrooper>I get a stack overflow when trying to import any nix pkgs
<Apteryx>The man_db.conf file is still used (despite the warning saying that it won't be used since MANPATH is set) to lookup the "catpaths" where database files go; but there are no matching entries in that file so it seems to default to writing the database file in-place (at the locations of found manpages).
<Apteryx>I guess this could be OK, since the manpaths resolve to a profile instance in the store. If I implemented a profile hook to generate these, it seems it would be OK.
<Apteryx>Could someone point me to where we keep our profile hooks code?
<kadintrooper>So how do I install a package from a definition I made? I run guix package -f (My file with definition) and it appears to have completed successfully, no output.
<Apteryx>kadintrooper: You could set GUIX_PACKAGE_PATH to the root directory of your package definitions. And then you should be able to install by name: "guix package -i your_package"
<kadintrooper>I'm trying to install neofetch, but I'm getting error: no code for module neofetch
<Apteryx>neofetch being your own package definition?
<Apteryx>kadintrooper: So far I get the same result as you (ERROR: no code for module (neofetch)). Also, when I try to lint (C-c . l) it throws: <unnamed port>:472:16: In procedure module-lookup: Unbound variable: use-modules.
<snape>yes, but you still need to generate grub.cfg
<efraim>other issues i can recall ATM are both mozjs files bundle a modified double-precision that doesn't support aarch64, which means no gnome/xfce, and libevent suffers from the same failure as armhf
<kekistani>so how do i generate a grub config without first installing an os copy of grub?
<Apteryx>If I rename the module to "my-packages.scm", then "guix lint neofetch" works.
<snape>kekistani: I don't know, but it is not a problem if it is installed :)
<Apteryx>kadintrooper: Forget what I said about GUILE_LOAD_PATH, and try to use only GUIX_PACKAGE_PATH (as civodul pointed out it was unnecessary to use GUILE_LOAD_PATH).
<Apteryx>kadintrooper: I got it working from here with just export "GUIX_PACKAGE_PATH=$HOME/src/my-guix-packages", where my-guix-packages is a folder containing my-packages.scm which contains your code (neofetch package definition).
<kekistani>I understand the boot process a bit better after skimming some documentation.
<wingo>i just commented out the entirety of that file :P
<jest_a_prank>If I encrypt entire partition by using LUKS and use it as a root partition, should I separate `/boot` for GRUB? or GRUB will know that kernel is in a encrypt partition and ask for the passphrase to decrypt?
<brendyn>Isn't grub it's self in /boot? it cant decrypt its self while it is encrypted surely 0.o
<jest_a_prank>I thought grub bootloader on MBR (meaning, not on /boot) asks the pw for `/boot`, and guixSD manual doesn't say any thing about it.
<brendyn>ah ok. anyway, i think there is currently a lack of support for full disk encryption in GuixSD. See the mailing list
<jest_a_prank>Just before few minutes, I'd finished installing GuixSD on my laptop and rebooted and realized that I forgot to mount /dev/sda1 that was supposed to be mount on /mnt/boot. But surprisingly, GRUB asked for a passphrase and successfuly loaded the kernel.
<lime_>Do I still have to deal with the 'dependancies' section
<snape>jest_a_prank: GRUB supports full disk encryption (without a seperated /boot)
<lime_>My degree is cyber security but I'm finding people don't trust academics
<wingo>heh yeah, could be. lots of prejudices and pattern-matching out there :)
<lime_>So I'm of to find a nice open source community to take me in
<wingo>i think guix folks are nice, there's new energy and some more seasoned people; not perfect, has its rough edges, definitely needs a lot of direction from the contributor, but pretty good i think.
<lime_>Guess looking up guile would be a good place to start
<lime_>Don't think anything is perfect, in free software, business or academia . Just making the best of what we've got.
<wingo>sooooo, someone recently imported a lot of kde packages, but didn't actually land them upstream yet. a good start would be to take one of them that doesn't depend on any other kde packages -- that only depends on things already in guix -- and get that landed in guix.
<wingo>sign up to guix-devel for that discussion and introduce yourself with a basic idea of the plan, just so people know and don't step on your toes
<wingo>the first package should be pretty easy in content (the content is already there) but the mechanics of getting a patch in are a bit involved
<wingo>so see the "contributing" section of the manual
<paroneayea>lime_: either it has no passphase and someone could take it, or I'd have to enter a passphrase multiple times still, or I'd have a way to splat my passphrase across multiple decryption runs, in which case I wouldn't need the usb key anyway
<lfam>That issue where Python could not build on older kernels also manifests for libressl, but there is no upstream fix and it's not a very expensive build for users to do locally, so I've left it alone for now.
<lime_>I assume that's how to get the latest guix code?
<lfam>lime_: That updates the copy of Guix used by the user that runs `guix pull`. So, you get the new package definitions, but it doesn't update packages that you've installed. If you're familiar with Debian, it's similar to `apt-get update`, but per-user
<lfam>In general, the Shepherd is at a very early stage compared to systemd, but it does work and people are using GuixSD
<lfam>Exactly what "systemd" is, is a bit nebulous. Some things performed by systemd are not done by Shepherd, but they are still integrated into the GuixSD system and configured declaratively. So, a systemd system and GuixSD both seek to offer a system with a unified interface, but the Shepherd does less than systemd.