<rain1>Maybe the best solution would be a complete update of icecat
<jlicht>rain1: what is wrong with icecat? afaik, it is based on a "lts-like" release of firefox, and gets regular security updates as well
<jlicht>All I am missing is the ability to use guix to manage my add-ons :)
<rain1>for me personally I just want the newest version of firefox (potentially rebranded, so it can be included in guix)
<apteryx>jlicht: +1, icecat is as good as firefox in my daily usage, and thanks to the hard work of Mark Weaver, it also gets patched for security.
<rain1>that's a neat idea that guix could manage ff addons!
<rain1>ok so perhaps the idea of making icecat base off the latest ff is not the right path then
<apteryx>rain1: if you have the manpower to maintain it, I don't see why we couldn't have a icecat-next that'd track newer firefox
<jlicht>rain1: well, it would of course always be nice to have the option to do so, but it does not seem to be a focus area for upstream icecat devs. In that sense, if you are willing to make it work, it could definitely happen :)
<rain1>I would like to contribute something smaller first though, I wonder what i could do
<lfam>Part of the issue is that there is not really an "upstream" icecat project with a lot of resources. It's basically one or two people working as volunteers
***astronavt_ is now known as astronavt
<bandali>hi, could someone please enable python3 bindings for the z3 package?
<bandali>as of now, z3 only includes ,python-2 in native-inputs
<marusich>bandali, perhaps you could try customizing the package definition to install the python3 bindings?
<marusich>You would need to create a new package definition that uses python-3. Judging by the package definition for z3, you would probably need to do the following things in your new package definition: (1) use python-3 in the native-inputs instead of python-2, (2) replace the string "python" in the bootstrap phase because python-3 provides no binary named python (it only provides "python3" etc.),
<marusich>and (3) change the configure flags - specifically you would probably need to replace "/lib/python2.7/site-packages" with something more appropriate for python3.
<marusich>This is, of course, assuming that the z3 project supports python3.
<marusich>If you get stuck, ask for help. The community is helpful, but sometimes the fastest way to get something done is to try it yourself. It may be faster than waiting for someone to do it.
<marusich>If you have questions, I'm sure someone here or on the email@example.com email list can lend a hand.
<epimrphsm>The package I am trying to build has several shell scripts for the build pipeline that reference /usr/bin/env. What is the proper way of handling this with Guix?
<epimrphsm>Should I substitute /usr/bin/env to (which "env")?
<epimrphsm>I've noticed that this is done automatically for /bin/sh, if I understand the output of `guile build` correctly
<epimrphsm>oh i see the problem, patch-shebang doesn't work in this case because /usr/bin/env does not occur as a shebang at the beginning of hte file
<epimrphsm>wtf why would you write `/usr/bin/env awk ...` in a shell script D:
<cbaines>epimrphsm, using env is normally undesirable, as in many cases you want to use a absolute path to the thing in the store
<cbaines>for example, I would suggest replacing /usr/bin/env awk with an absolute reference to either awk or gawk in the gawk package