<apteryx_>I'm trying to build cling inside my profile (not as a package, yet). I get this error when running cmake: ld-wrapper: error: attempt to use impure library. Any idea? If I try from a pure environment, I instead get an error that /usr/bin is not in the PATH or something similar.
<atw>what might I need to add to my system config to get brightness keys working? currently no application is grabbing that key as hitting a brightness key will cause emacs to say "<XF86MonBrightnessDown> is undefined"
<marusich>lapinpin, I presume you are the same as lapinpinpin. That message, "but I am a...", probably comes from a recent commit that Ludo made which is intended to make it possible to transparently build for other architectures (without cross-building) using QEMU.
<marusich>I suggest that you report the issue you are having on guix-devel@, or bug-guix@.
<marusich>Ludo, or someone else, might be able to provide more useful feedback.
<trivial-fis>I read the menu about guix environment, but didn't get it right.
<snape>I have no experience with Python, but lots of Python packages are already packaged for Guix, and I don't think they would be unconvenient to use
<trivial-fis>Quick introduction. Python virtualenv let you set up a isolated environment in a directory. All packages in that env are independent of the outside world. And you can install/remove packages anytime you want just like normal environment.
<trivial-fis>The installed packages with python interpreter itself will be stored in that directory.
<trivial-fis>I want to achieve the same effect with guix profile. But the spawned shell seems to use my ~/.guix-profile by default.
<snape>you mean you want to achieve the same effect with guix environment?
<snape>Yes. I probably don't understand well what you want, since I never worked with Python environments though. But if you quit a Guix environment and want to get back to it, you need to type the command again.
<snape>with --pure there should be nothing using ~/.guix-profile
<trivial-fis>Most of the time, environment created by python virtualenv ties to a specific project. So basically one env for each project. I need to go back to the exact same environment every time I work on that project.
<trivial-fis>And I need to remove that environment after I am done with(Never ever need to see it again).
<snape>IMHO you quit the shell when you are done, and you type the same command if you want to get back.
<clacke[m]>or is sourcing the etc/profile the way to do it?
<rekado>I wanted to add support for deb packages and flatpaks
<castilma>rekado: sorry, i still assume everyone is male on the internet (and I thought guys can also be used for groups, even though there are females in there).
<castilma>clacke[m]: it does that by default, afaik. but by default it there is no garbage collecter root created to prevent it from being collected(after you quit the shell). you can create one with -r option.
<civodul>rekado: half of the population is female so let's just avoid "guys" :-)
<nckx>Hola Guix. Say I want to add perl as a native-input, but not have all perl shebangs patched (and hence retain a reference). Is there a keyword or other easy way to disable automatic patching for only 1 particular input?
<nckx>(Next options are disabling the auto-patcher altogether and hope that doesn't break anything, or manually undoing the patching, but both are icky.)
<bavier>nckx: manually unpatching the shebang is pretty easy
<nckx>bavier: Oh sure. Just a bit silly if I don't need them patched to begin with.
<nckx>They're all just example files which makes it even sillier.
<sneek>ng0, nee` says: I fixed or worked around most of the problems I had with GNUSocial and got some patches merged upstream. I have do some more testing and then I'll send an update during the next week.