<apteryx>but if you are not developping and just one access to guix from geiser, it's probably better to add the location of the guix as installed in your profile already, at .config/guix/current/share/guile/site/2.2
<wdkrnls>why wouldn't I just want to duplicate the %load-path from guix-repl?
<trzcdev>I wish I had a good question, but I'm in that overwhelmed phase of learning something new. My goal is to package an application. I've done the hello-world and, of course, that works. For a non-trivial software, I'm trying to package the nomacs image editor.
<trzcdev>This is part of the "swimming in it". I'm getting lost in the documentation. The most cohesive thing I've been able to follow is the blog post "A packaging tutorial for guix". This, I believe, is the source of the hello-world.scm build script.
<trzcdev>I've modified that and will post it momentarily. (Talking on my host whereas the script is in a VM)
<trzcdev>When I try using it via ~guix package --install-from-file=build-nomacs.scm~, it fails and the logs say that it can't find CMakeLists.txt
<trzcdev>The source code does contain a CMakeLists.txt, but it's in a subdirectory to project. I'm guessing the error is a pathing issue.
<trzcdev>And this is where I'm at an impass. I'm not sure how to proceed. I've been swimming in the Guix documentation, Section 6.2, as well as the aforementioned "Packaging tutorial for Guix". It seems like the cmake-build-system variable is what I'll need to modify, using some #:configure-flag.
<Dynamicmetaflow>era maestro antes en la escuela public, ensenando como programar en ingles y espanol.. aunque habia un poco de problema con estudiantes que acaban de llegar al pais por la mayor parte podian entender el codigo
<roptat>abcdw, I run the guix system on a cubietruck (cubieboard 3)
<roptat>I think it won't boot on a raspi because of nonfree firmware required to boot, but there are other arm boards supported
<abcdw>roptat, I'm ok with other arm boards. Do you have a config or blog post about guixsd installation process on arm board? I think it should be similar to x86_64, but the article or config will be helpful anyway.
<roptat>abcdw, in the case of my board, I had to first install a foreign distro and use it as if it were a guix installer system (so manually installing guix with guix system init)
<roptat>I don't have a blog post about that though...
<nckx>It's the path to the libraries, which often is ‘/lib’. OK, so that snippet assumes that libgtk-frdp-0.1.so and libgovf-0.1.so can be found in /gnu/store/r2zs8d4b3s1y60mxi8j18zww2421314n-gnome-boxes-3.32.1/lib/.
<nckx>media-manager.vala:224: Error connecting to Tracker: Failed to load SPARQL backend: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.freedesktop.Tracker1 was not provided by any .service files
<apteryx>rekado: ah, the meta command is called 'run-IN-store', not 'run-WITH-store'. I'm just an idiot.
<nckx>Dynamicmetaflow: It's ready enough for -patches after cleaning (propagated → inputs, no lonely brackets, just hard-code the name in URLs instead of using NAME, maybe find/write a slightly longer description, …). It doesn't have to be perfect or do fancy things like ‘run’. There's always v2.
<rekado>once that’s done and core-updates has been built and merged into the “master” branch we can do the 3.32 upgrade.
<rekado>if you want to get started on this now you could create a new branch that’s based on the latest commit of core-updates, but rebuilding everything takes quite some time, so I’d suggest waiting until core-updates has been merged into “master”
<rekado>this should have happened a while ago, but problems always pushed back the merge date…
<Dynamicmetaflow>I will wait, this gives time to study the code that's already there and read up on logs and changes to 3.32
<rekado>we still have a bunch of unsolved problems before core-updates can be merged, including a broken Java bootstrap (kinda solved but ugly) and a verification problem with the reduced GCC bootstrap.
<rekado>it’s going to be at least another two weeks, I reckon.
<Dynamicmetaflow>Well, I'm in no rush there's plenty for me to study and learn and I can hopefully package other things the community needs
<Dynamicmetaflow>I think I remember running into a wikipedia at some point that had a list of packages people wanted packaged or requested
<Dynamicmetaflow>rekado: gnome-boxes doesn't display icons, I noticed an error about it not having the hicolor-icon-theme and I added it as a native-input and now the icons show up accordingly. I know the packaging tutorial goes over native-input, input and propogated inputs
<Dynamicmetaflow>but in this case where the hicolor-icon-theme is not required to build gnome but is needed in order to see the icons in the GUI which of inputs should the hicolor-icon-theme be placed?
*Dynamicmetaflow is reminded of why he uses window managers and emacs all of a sudden.
<Dynamicmetaflow>nckx: I'm looking to test gnome-boxes now, some reason my guix vm I created won't run, I get a critical warning that's relted to it saying QEMU binary lacks smartcard passthrough mode support...
<apteryx>err, I think the lack of error output is strictly a Geiser thing
<rekado>Dynamicmetaflow: I see warnings in wizard-source.vala:444. This looks like to download OS images it needs internet access, and that’s probably not working because of missing GNOME networking libraries. May need more wrapping.
<Dynamicmetaflow>lsl88: It was because of the packaging tutorial that helped me create an environment to create the gnome-boxes package, it's been built and now with nckx and rekado figuring out its quirks
<abralek>problem (is it a problem?) is that the documentation says:
<abralek> As for ‘dynamic-link’, LIB should not contain any suffix such as ‘.so’ (*note dynamic-link: Foreign Libraries.). It should also not contain any directory components. Libraries that implement Guile Extensions should be put into the normal locations for shared libraries. We recommend to use the naming convention ‘libguile-
<abralek>bla-blum’ for a extension related to a module ‘(bla blum)’.
<abralek>But thanks, if we have such example it should be fine than
<rekado>Dynamicmetaflow: it may be worth testing this by 1) building these packages to get their locations, 2) then set env vars like LD_LIBRARY_PATH and the like to see if they affect the behaviour of gnome-boxes.
<davexunit>rekado: yeah that needs patching and there is no convenient configure flag to handle it. this was before I used guix. :)
<rekado>Dynamicmetaflow: i.e. testing outside of the Guix build container.
<Dynamicmetaflow>I would recommend Racket for learning and then you can deviate from there depending on what you want to do
<davexunit>yeah, just start. you'll begin to develop your own tastes in time.
<Fzer000>Racket -> clojure. Watch some talks by Rich Hickey, he is a great speaker
<minall>Btw guys, I'm trying to use xwidgets-browse-url on emacs, but a message that says -your emacs is not compiled with xwidget support- pops out, So I need to recompile it with xwidget supprt, how do I rebuild it on GuixSD?
<Dynamicmetaflow>rekado: how would i patch qemu for supporting smartcard passtrhough?
<roptat>you can find them with "guix package -A ^texlive-"
<ryanprior>Fzer0: I have still not managed to set up a clojure dev environment, although I have been coping with this by working on my guile/geiser dev environment instead :) how about you? Any new insights?
<orang3>hello Guix! Do you have any clue about why I can't mount my usb drive in the Guix System? Am I supposed to add my user to some group in my config.scm? The manual just mentions that gvfs should be present in the packages section to do "user mounts", but it seems not to be enough.
<civodul>orang3: if you're using GNOME, it's supposed to just work
<civodul>that is, you plug in the drive, and then a "File" window pops up
<orang3>I'm using XFCE, should it matter? Also I noticed (not sure if it's related) that while fdisk can easily access and modify partitions, gparted segfaults right after it finishes to search for disks
<civodul>orang3: good question, i don't know about Xfce!
<civodul>i suppose it should just work as well, maybe there's a bug
<civodul>could you email your bug report to email@example.com?