<zamfofex>ride: I have recently (finally) installed Guix SD on an actual computer, and I decided to do GUI things by myself, as opposed to relying on existing packages. I installed IceCat, and it did not have any fonts, instead displaying blocks with the code point values inside them, even for ASCII characters. I fixed that by installing the DejaVu font
<apteryx>in the simplest case suppose your project is happy with the version of its dependencies in a given Guix revision. Then you just need to fix a single hash of Guix to cristalize them (guix describe -f channels > channels.scm).
<apteryx>where it gets tricky is if you need packages from different Guix revisions. This is currently achievable via Guix inferiors, but yes, you'll have to grep the history to discover which Guix hash contains what you want.
<cheers>i may try to whip up a flakes-esque tool for guix, when i find the time :)
<zamfofex>I wonder how feasible it would be to get package suggestions when typing the name for a program that isn’t installed, kinda like in Ubuntu.
<bqv>zamfofex: so a command-not-found helper. Yes, nixos has one, so guix easily could
<marusich>Anyone have trouble building "guix build --no-grafts -d email@example.com" recently? I get an error like "You need openssl to run this test." I don't want to substitute it, but there are substitutes available for it, which makes me wonder why I can't build it but the build farm can...
<rekado_>apteryx: you can ‘weaponize’ procrastination. In my case, I procrastinate on things that I should do by doing other things. It’s just a matter of putting meaningful tasks in the those slots on the TODO list that would be picked when procrastinating on the top priority task.
<gnutec>rekado, Just doesn't record. But is perfect now.
<gnutec>rekado, I did know about "peek". But is 7,3 MB against 1,2 MB from Simple Screen Record. I'll take a look.
*profmakx discovers the risc64 qemu bootloader, tries making a disk image
<nij>Hello! I'm new to this place :) I tried Nix before and quite liked the idea. But I left as there was much work to do and I didn't like the language. I recently got into Lisp, and found Guix. I'm interested again. Before I dive into the playground.. I'd like to clear some of my concerns.
<nij>1. Rumor has been that Guix has a much smaller community, and there are more restrictions (e.g. hard to get non-free software). Do you find yourself switching to different package manager quite often?
<nij>2. I'm on arch. Can I use Guix just as a package manager, and expect it to completely replace pacman/aur-helper? If so, what would be a practical way to start? If not.. would I be using both systems at the same time..?
<nij>3. How to handle python (or ruby, go, haskell.. etc.) packages (i.e. those that you get from pip install)?
<PotentialUser-80>Is it possible to cross-compile a BeagleBone Black installation image on a x86_64 computer?
<nij>4. What will I lose if I use Guix as a package manager but not the whole OS?
<atw>1. I think you have to answer that one for yourself by asking how well will free drivers work on your hardware. Heads up that in this and other official forums, it's desired that discussion stay on free software
<atw>3. many python, ruby, go, and haskell packages are available in guix. You're free to use Guix to do development in those languages, but if an eg python library is not packaged in Guix, you may end up packaging it yourself (but this is usually very easy thanks to importers). Alternatively you can keep using eg Stack for Haskell. Whatever works for you!
<lispmacs>nij: hi, I use Guix as my full system on my home and work desktop PCs. I just wanted to mention some downsides to Guix on, say, Debian: (1) when I tried that in the past, development of code became rather complicated due to interaction between libraries installed in the traditional paths, and libraries I had installed through guix. (2) if you use Guix as your full system, it makes a lot of cool system configuration
<lispmacs>easy to do through minor edits to your system configuration file, and running the "system reconfigure" command
<nij>atw: Thanks.. and not yet. I'm just worrying to be hopping from different packaging systems..
<atw>"--root=FILE [...] Make FILE a symlink to the result, and register it as a garbage collector root." if I were to do this, how would I undo it? How would I unregister FILE as a GC root?
<ruffni>i am trying to set up a guix StandaloneVM in QubesOS. Qubes warns about having to manually configure a StandaloneVM for networking to work correctly. i managed to bring up the link (ping 184.108.40.206 works just fine) but i'm having trouble resolving hostnames. any pointers? i'm running the `guix-system-install-1.1.0.x86_64-linux.iso`
<mbakke>ruffni: if you configured networking manually, you probably also have to manually update /etc/resolv.conf with a working name server
<sakalli>hi *. a couple of hours into guix on top of arch. when you install packages 'imperitavely', does it generate a file or can one export one, that declares the current state of the installed packages. ie. what would be the way to restore a profile?
<lispmacs[work]>sakalli: I'm checking in the documentation to see if there is a way to generate a manifest file from a profile
<lispmacs[work]>I do things the other way around. If I need a new package I just add it to my manifest file. If I need a package short term or on an evaluation basis, I use `guix environment --adhoc <package>'
<lispmacs[work]>sakalli: I'm not seeing a way to generate a manifest file from a profile; I seem to recall asking about this once but can't recall what I was told. One can do `guix package -l' to get a description of all the changes you have made to your profile, which would be helpful in building your Manifest file
<lfam>Then it's likely a transient networking failure, ruffni
<lfam>Wow, we should really do something about the linux-libre sources. I think that currently they are built 4 times
<atw>thanks mroh, the guix gc page in the manual has some helpful info I hadn't read before. I may make a contribution to state explicitly that roots created with --root can be unregistered by deleting them
<efraim>I like the idea of python-minimal for the build system