<jgart>char[m], there was a discussion on the mailing list about that very thing
<jackhill>jgart: char[m]: I beleive it's the same for even manpages too (need man-db in the shell to pick up the pages of programs in that profile) (unless man-db has now been special cased). I think the idea is that the interperter, programming language, etc (ncurses for terminfo files, although there was talk about special casing that recently for foot) determines what environment vars get processed which is where
<sughosha>Hi, there is a line in Makefile which contains $(NAME). I am trying to use (substitute*) function remove the "$(NAME)", but I'm not able to escape the "$" by a backslash, as it is saying "invalid character in escape sequence". Could anyone help me please?
<podiki[m]>you sure that part is not generated somewhere else maybe? from a configure?
<sughosha>The problem is that the package is storing the header files in "/usr/include/gbinder", but I want them to be in just "/include". The makefile has like this: "/usr/include/$(NAME)". I want it to be just in "/include"
<sughosha>I'm trying to package gbinder-python, as a dependency for waydroid.
<sughosha>> you sure that part is not generated somewhere else maybe? from a configure?
<sughosha>Yes, it's not. I can replace anything else than the "$" sign.
<podiki[m]>you might need some matching for the start of the line?
<sughosha>No, because first I tried to substitute only "usr/include" to "/include". It was working. But then I realised that it has one more subfolder, "gbinder". Now I'm stuck with the above problem.
<apteryx>sneek: later tell civodul after experimenting with the original idea, relying on a version field was easier and cleaner; I was able to also rename the --system, --load and --repl initrd options: https://issues.guix.gnu.org/40998#5
<anticomputer>hrmm, so say I want to build a .so in my ~/ that I have to load and re-use at some point in the future, presumably I'd want to use a guix environment with -r to build the shared lib so that any linked libs don't get garbage collected out from under the .so in the future yea?
<anticomputer>oh sheesh, so I just spent an hour forking a custom libvterm package because emacs-vterm wasn't working for me and I was convinced that I needed to build libvterm from the git ref that emacs-vterm uses, got that done, emacs-vterm still doesn't work ... many headscratchings later ... remembered my (shared between systems) emacs config sets the vterm shell to "/bin/zsh" ... d'oh, moved the setq to "which zsh" and all is well hah
<mbakke>sughosha: hg-commitsigs does something similar ... you'll need the same #:imported-modules, write #:modules as (((guix build python-build-system) #:prefix python:) (guix build copy-build-system)) and then you can (add-after 'install 'wrap (assoc-ref python:%standard-phases 'wrap))
<podiki[m]>excalamus: curious what you meant by problems you ran into, was it in having different pieces? I was just going to generate the config.scm from org babel, but right now it is just for one machine, so nothing fancy to generate
<excalamus>this is where I think I misunderstood you. I've tried to document my work with guix using org. The issue there is that building can take a while. Since the org shell is blocking, that means your emacs session freezes until your guix stuff finishes. If you're talking about tangling a script, yes, that works fine.
<podiki[m]>ah, so more literate programming of your actual guix hacking?
<acrow>I also imagined during guix days that people were going to annouce that guix-home now enables a local store into which you can put your personal secrets. Managed, of course, using the home-guix-shepherd. Did I miss it?
<excalamus>I didn't see that. I may have missed it in the first part of the day (I was asleep)
<excalamus>roptat, the time zone differences are a challenge. Not sure what else can be done about that
<acrow>Current setup uses guix-home and syncthing. stow is there (with files safe in the filestructure) but has to be fixed up after every time guix-home is reconfigured.
<acrow>Syncthing works great for me (because I have multiple cheap machines that can share things) but I feel some guilt that I don't put the work needed into reducing things to rsync (as lilyp suggests).
<lilyp>That was not a suggestion, do not ask me for tips on backups!
<acrow>Yes, I'm a reductionist. There, there I said it. Now let's not talk about it anymore.
<lilyp>Rather than discussing software solutions, my aim was to discuss the set of files you need to back up at all
<acrow>lilyp: nice work, btw. If you didn't already hear it from me. thank you.
<lilyp>putting your config.scm and home.scm both into syncthing is still more reasonable than having no backup or storing entire disk images
<Samuel[m]12><excalamus> "this is where I think I misunder..." <- have you seen ob-async? It doesn't work with #+calls, but for any long running tasks its a lifesaver, such as remote db queries directly from src blocks -- and you can use multiple blocks concurrently
<acrow>ok -- but where do my, few, secrets go? Is this where a small container image is appropriate?
<acrow>secrets are the burr under my blanket. The antithesis of declarative programming. The forbidden fruit that I think I ought be able to grasp. :)
<excalamus>Samuel, yes, I have. I found that it worked for some things, but not others, like sessions. The source worries me, too. The main functionality looks like a copy-paste from the org source.
<blake2b>any interesting examples of pattern-matching for bitwise operations in scheme someone could recommend?
<the_tubular>I know that there was some prerecorded ones, I'm talking about the other ones
<acrow>efraim: and then you just take that base64 and put it into your guix-home (plain-file "blah.b64" "my-secrets") like thing?
<efraim>I haven't yet but I think I'll just embed it as is
<efraim>Probably not ssh/config but I have some other files that I'll try out first
<efraim>I have some passwords that I leave encrypted for sending mail. Easier to just remember my gpg passphrase
<acrow>efraim: yes, that is the reductionist ideal! one password. tidy.
<blake2b>one thing I think my presentation was lacking due to time constraints is to show folks the incredible part of the docs, which is the Guile Implementation section. if you've used guile in guix but havent dove into the language itself, do yourself a favor and just go straight to the section on the compiler tower and read until the end
<excalamus>blake2b, I'd watch a video of that if you recorded it
<blake2b>perhaps I will. I think people don't realize that with guile, you essentially get declarative, compiled languages for free with the (define-language ...) form. its really simple to use and there are all of these high level compiler tools to play with.
<paul_j>Evening all! Quick question - is there documentation explaining how I can test a patch out? I am following the problem with thermald/upower, and Maxime has kindly provided a couple of patches which should resolve it for now, while upstream sort out the problem.
<paul_j>I am quite happy to work with the full source if that is necessary, but I wondered if there is some way to inject a local patch during the build.
<lilyp>paul_j: currently not, but the gist of it is you download the patch-set from mumi, run `git am', build things locally and test them (in a pure evironment, vm, or similar)
<paul_j>lilyp: the patches are attached to the thread about the bug, so I can get them from there. I'll give it a go, and see what happens!
<ss2>Hello, and good evening. It is such a shame that I didn't manage to participate today, and tomorrow I'll just about be around for 16--18 properly discussing the future of Guix. I might join before.
<ss2>I'd like to somehow jump in tomorrow, and discuss about my little work on writing a Samba service. And I'd happily would also like to use an oppurtunety to introduce myself too. It is nice seeing and hearing some real voices.
<ss2>But I'm not so sure when the timing will be best to talk a bit about Samba.
<ss2>Seems a bit late now and I missed the whole show today. I hope to catch you tomorrow at a better timing.
<roptat>ss2, you could join during one of the "spontaneous topics" sessions :)
<ss2>I thought so too, but I'm not sure if I'll manage. I'm always in bad luck with timing.
<lilyp>I don't think a manifest is a full package description, but since you'll be invoking specifications->manifest or packages->manifest anyway, you can instead stuff those into a list and proceed from there
<Haider>are any of you also having problems in Qutebrowser where it wont render certain fonts?