<Cairn>So, in theory, you should be able to type `guix package -i dwm --with-source=[your-repository]`
<Cairn>Oh, I guess, you could simplify that to `guix install dwm --with-source=...`, since install's just another name for package -i
<Cairn>I'm also new to this; trying to remember all the details.
<Cairn>Yep, I just cloned "git://git.suckless.org/dwm" to the directory "custom-dwm" then I ran `guix build dwm --with-source=~/custom-dwm` and it worked.
<aristetix>Speaking of dwm, I can't get mine to install. It fails at stage 'validate-runpath' for some reason. I have it building with #:validate-runpath? #f, but using readelf -d shows that there is no RUNPATH on the executable.
<trevdev>If I want to use stumpwm, but install modules in the user-space, what's the best way to go about that? I'm a CL novice. I can asdf the modules if I install them with root, but not with guix home
<Cairn>Good character limit for (synopsis)? Should I keep it under 50, or I can I go up to 70?
<lilyp>Cairn: if you need a new line, you should stop
<SamSam>oh and just for future cases what package to install to hace make command?
<Cairn>SamSam: The issue with using make, that Guix doesn't place libraries where it normally expects. In my brief experience, make seems useless, not only because it normally won't succeed, but also since it's circumventing the entire point of Guix.
<Cairn>I recommend learning to work with Guix for all your package building needs.
<Cairn>But the make command is, of course, in the package called "make"
<Cairn>Which you can learn by typing "guix search make"
<Cairn>Heed my warning though! Use the package system; don't try to use make on its own!
<conjunctive>Hi, looking to create a simple dev environment for Ruby & the ruby-pg gem. In the guix.scm file I've set the #:ruby argument on the ruby-build-system to a recent version (e.g. ruby-3.1), but after running guix shell and IRB I see "Ignoring pg-1.3.5 because its extensions are not built."
<conjunctive>I then tried using package-input-rewriting on ruby-pg to further override which ruby package was being used (e.g. ruby-3.1), but this only led to build failures (with #:deep? #t) or the exact result as before (with #:deep? #f).
<conjunctive>dthompson has a great blog post on packaging gems with Guix. The only part I'm missing is how to constrain the Ruby version and have extensions be built for it.
***Dynom_ is now known as Guest4076
<conjunctive>Updated a testing library dep and added a clause for it to package-input-rewriting, seems to have fixed it! Would be interested if anyone knows of an alternative approach.
<sneek>abrenon, nckx says: I think this is supported by git-checkout (which would replace your entire origin).
<sneek>abrenon, nckx says: This ‘just’ checks out the repository on the host side, using any SSH authentication information present there. Kind of like local-file. That said, the functional store model doesn't play well with some kinds of huge data sets.
<attila_lendvai>are there compiler macros in scheme? i.e. a macro that can optionally optimize a function call site. my highlevel goal is to have a (maybe-value v default) function that only instantiates its default value when needed.
<antipode>attila_lendvai: I'm not sure what you mean, exactly, but (if you know how to) it's easy to, say, write a 'const*' macro that turns (const* #false) -> predefined-const-false-variable (const* #true) -> predefined-const-true-variable, ... and for other things expands to (const exp).
<antipode>That would be purely macro / expansion though, there is no interaction with the compiler and optimiser
<attila_lendvai>what i want is, basically, a user-defined transparent optimization for a function call that can bail out, and that doesn't change the semantics of the function. (the equivalent of a so called compiler macro in CL; further web search suggests that it's not part of scheme, but some schemes provide it in a non-standard way)
<drakonis>attila_lendvai: i think mit scheme is an implementation that provides that
<rekado>I would like to change an existing service so that it does not automatically start.
<rekado>the system service provides an extension to the shepherd-root-service-type
<rekado>IIUC modify-services doesn’t let me directly manipulate the shepherd service
<rekado>do we really lack a simple way to modify a shepherd service?
<drakonis>attila_lendvai: you might like the new compiler backend being written for guile
<davidl>General idea: how about writing a script that does package-imports for low-dependency projects? Wouldn't it be easy, actually, to traverse packages on for example npmjs.org, look at package.json for each package, and if there are no dependencies mentioned, then attempt to build it, and if successful, it can be saved to a package module node-unsorted.scm? Then make a quick sanity check and add a bunch to guix master. Saving some time for
<ericson2314>I want to show the nix community guix could be interested in this, and I want to show the guix community that nix is serious about decoupling libstore and daemon --- this isn't some weird attempt to canibalize guix users or whatever
<ericson2314>a mini nix would have just those CLI commands which don't need libexpr or libflakes
<apteryx>I'm sure they'll jump back into action soon
<apteryx>it's better form anyway to ask openly in guix-help, guix-devel, or here, so that hopefully the burden can be shared :-)
<examors>Hey Guix! Is there any way to identify shadowed package variable definitions? I have 'define-public'ed the same names multiple times (as a result of a series of recursive imports), but I'd rather not try to find them all by hand :P
***linj[m] is now known as linj
<pkill9>sometime I will set up sway so it launches applications ina container associated with the workspace you're on
<pkill9>so certain workspaces will be environments
<Cairn>Alright. So for a go project, do I need to package all the dependencies as well?
<yuu[m]>Cairn: afaik for using the any import/build-system you need to do that yes, since guix official tooling require full bootstrap
<Cairn>Hm. Can you submit multiple commits in the same patch? Or should I squash them all into a single commit?
<demitasse>do app images work on Guix? or only flatpaks?
<mgd>Hello, I've recently been getting an error saying error: unsupported manifest format when trying to install anything. I just want to understand what the error means
<cwebber>I happen to have the same JID as I do email
<cwebber>also I'm not sure what this has to do with #guix
<gnucode>sorry cwebber that's my mistake. I meant she.
<gnucode>I was just wondering if guix had packaged an XMPP client program that I could use as my generic contact book.
<gnucode>emacs' bbdb is really hard to get to work (my opinion) little documentation. and I routinely lose break my installs of whatever distro I happen to be using at the time. XMPP (jmp.chat) is the first contact manager that I trust. I suppose I could ask the jmp.chat guys.
<acrow>nckx: Thank you for your assistance yesterday. https://paste.debian.net/1250880/ This works to build mkcue from the debian sources. I'm interested in improving this. The way I eventually accessed the patches using find-files is very awkward and fails to build on the availability of the native input. Anyone care to comment?
<ericson2314>But at least I know that community so I know what I'm up against :)
<tricon`>mbakke: i very much enjoyed your post. thank you.
<August18_2022>Hello people, has anybody tried to install GUIX without a graphical environment + display manager and setting up Xorg with Xinit (for startx command) afterwards. I am having trouble executing startx, although the dependencies are there.
<tricon`>August18_2022: I use said setup with DWM.
<August18_2022>Thank you, I will try to replicate that inside a VM again, but in the first paste, there are two »exec« calls, isn't it the case that after the first »exec« was executed, it wouldn't execute anything further in the script/file?
<florhizome[m]>> Why gnome 42 does not packaged for Guix yet? Is there any problem with it?
<florhizome[m]>I just wanted to ask about this – first, gnome packages are stuck between 40.0 and 41.x, it would seem to make sense to try to have a consistent versioning for the core libs and DE, second do we have a core updates drop soon (the last one is more then half a year ago), and are there any ambitions to move to 42+?
<pkill9>or polluting non+project usage of the program
<pkill9>like run chromoum for a project and bookmark a bunch of things
<trevdev[m]>I am trying to get stumpwm-contrib to work in the home environment. From what I have learned, I must get the asdf module source-registry.conf.d into the correct config folder `~/.config/common-lisp/`. This must happen for the module itself & all of its `input` dependencies.
<trevdev[m]>I can get `(directory-union)` to farm out all of the packages (and all of their output directories!) into one place. Is there some elegant way to single-out the registry stuff in the `/etc` output folder?
<trevdev[m]>I suppose I could just slam all of the package data into a user-folder that ASDF prefers like `~/common-lisp` or `~/.local/share/common-lisp/source` but that feels like overkill.
<trevdev[m]>Wait, I'm seeing `source-registry.conf.d` in `~/.guix-home/profile/etc/common-lisp` - this is what I need. I can be symlinked to the config folder.
<yuu[m]>how much storage does ci.guix.gnu.org uses?
<dthompson>from time to time I ask this: has anyone ever gotten an error like the following from guix deploy?
<dthompson>guix deploy: error: corrupt input while restoring archive from #<closed: file 7f7578f2d930>
<dthompson>unmatched-paren: it's consistently reproducible. in fact I've been blocked from using guix deploy for like a year due to it. I just gave up awhile back and only now found the motivation to try again.
<dthompson>I just find it odd that I seem to be the only one blocked by it
<lilyp>dthompson: this doesn't look like a deploy error, but a substitute error
<lilyp>it should normally go away upon second invocation
<dthompson>lilyp: unfortunately it doesn't. it happens every time. I can't reproduce it outside of using guix deploy. if I manually reconfigure on the remote host it works.
<dthompson>I'm getting a guix dev environment setup for the first time in a long time so I can attempt to dig in a little further when I have a chance.
<blake2b>dthompson: how about running guix pull on the deployment target? how is memory usage over there?
<blake2b>oh sorry, I just saw that the reconfigure was on the host
<dthompson>blake2b: I haven't done this in awhile but in the past I'd make sure that I have the latest version of the guix daemon running to rule out running an outdated daemon
<blake2b>like lilyp said, this is a typical error that occurs when there are network problems. but I know I've also experienced it from my own cuirass server when I was running too many workers, using up all the ram. are you running cuirass on the host?
<blake2b>dthompson: did you run "guix pull" before you reconfigured? if not, i think you would have reconfigured with old definitions on hand (I could be wrong and reconfiguring fetches the current defs, but I don't think it does)
<examors>jackhill: no problem :) there's something very strange going on though - /gnu/store/bp9j67p8ynif5p2vbjl7lg294f5aihxk-xdg-desktop-portal-1.14.4/libexec/xdg-desktop-portal is an ELF binary on my system, and I can run it.