<parnikkapore>Hi Guix! I'm thinking about using Cuirass to do devops for my channel. Can I make a specification that uses a remote branch that will be rebased and force-pushed (i.e. the branch's tip won't be a descendant of the last evaluation)
<nckhexen>I coincidentally have a Germain keyboard (but not layout). Here it's a typo for, well, something I can't type, because I'm in an initrd and for some reason alt doesn't work the way it should here.
<batalie>hi, guix. i'm trying to write a manifest that will work on all of my machines. the problem is that i need to pull in a patch, but my username is slightly different on my different machines, which messes up giving with-patch a filename. could someone take a look at this? note i'm pretty bad at scheme :) https://paste.debian.net/hidden/ab943af9/
<pastor>Another idea I has it to just build the toplevel crate but then I don't know how the output should look like. And I don't really know how to define the diferent outputs of the package like that
<nckhexen>Where does the build system 'pick the top-level Cargo.toml'? Or do you mean cargo proper?
<nckhexen>zamfofex: How does your custom phase get run in the dependent packages though.
<old>I have a package written in C that has Python bindings. However, during the installation, setup.py install a .egg file instead of the python files
<old>I suspect that this is handle by python-build-system, however I need to use gnu-build-system for the project since it is a C project that generate shared libraries and binaries?
<pastor>old: you can add an extra phase that installs the files that `make install` is not deploying
<nckhexen>This is not a serious suggestion, but you could rewrite the top-level Cargo.toml in a snippet and something something profit but probably not.
<nckhexen>That would stand a chance of making it into dependents, at least.
<zamfofex>nckhexen: Ah, good point. Rust builds all dependencies from source, right? Kinda like Haskell, I think. Perhaps a simple solution would be to have a custom source for the packages. I.e. clone the Git repo, and then create a tarball with only one of the directories from it, and use that as the source for the package.
<nckhexen>Isn't reinventing static linking but even worse GRAND?
<old>pastor: right. That would be a painful thing to do but if no other choice ..
<pastor>zamfofex: This is not possible. They depend on eachother
<pastor>old: You can reuse the python install phase
<zamfofex>pastor: Like, mutually depend on each other?
<nckhexen>If so, there's no point in 'packaging' them separately, they are not separate packages.
<pastor>zamfofex: this would be the dependency for the module `canvas`
<zamfofex>Kolev: I use micro often, note that it’s official build is a static binary which works transparently on Guix.
<Kolev>zamfofex, I had difficulties adding ~/.local/bin/ to my $PATH.
<zamfofex>nckhexen: As much as I kinda hate it, I can understand the reasoning behind source‐only builds. I feel like programming languages don’t want to have to implement headers like in C nor a custom binary format like Java.
<zamfofex>Kolev: A simple solution (one that I use) is setting a Bash alias to it. It has been working well for me for a while now!
<zamfofex>Though I have taken the alias away somewhat recently in order to encourage myself to use Lite XL more often, so now I just start micro with ‘~/bin/micro’.
<Guest41>zamfofex ah, thanks I accidently called it contfig.scm
<jackhill>lilyp: remember I complained about the new epiphany and file upload not working? I can't reproduce that today, it works! Yay. Don't know if I was hallucinating or if things were just in a wierd state and restarted helpd.
<lilyp>If you do manage to reproduce it, don't forget to report it properly with all relevant info :)
<jackhill>lilyp: yep :) I was trying to collect just that sort of information as it turns out
<futurile>hmm if I do `guix shell --container --nesting` and then in the shell do `guix describe` I only get the guix channel - not my other channels. Is that a change of behaviour or am I now hallucinating
<futurile>ack nope - I got it - I must have run my original tests in my home directory so ~/.config/guix/channels.scm was available - and blew up `guix time-machine`.
<apteryx>lilyp: I'll delete the wip-gnome* branches, unless you see a point
<lilyp>apteryx: IIUC they're ancient gnome anyway, so go ahead; current dev work is on gnome-team
<PotentialUser-93>I messed up. I put something in .xsession, now I cannot start into i3. How can just boot into the shell in Guix ? Gel please
<futurile>Q: if I do `guix shell --container --nesting git`, and then in the shell I do `guix package --list-installed` it doesn't show that git is installed. It is there - it's in $PATH. Why doesn't it show up as being installed?
<Guest41>I had I3 not starting. After installing alacritty again i3 started properly again . very strange
<futurile>snape: yeah I think it's one of those things you know, but you still expect `guix package <blah>` to show you whats happening in the current env. I find profiles simultaneously useful and complicated :-)