well I hope it wasn't josh because we need the key bsherman added. 😄
well I hope it wasn't josh because we need the key bsherman added. 
DI figured out how to build nix from source https://nixos.org/manual/nix/unstable/contributing/hacking.html
AJosh added the code to copy the keys around iirc 
Jdo you know what command to run to check the key?
Asadly no, check
mokutil --helpAI have meetings at work, I'll try to check if I get some time
Jyeah this is way out of my scope, I'll stand by
PYeah I've been meaning to try that at some point
JI'll PR the version bump in the meantime
Ait looks like you need nix?
PI haven't tried it but I get the sense that the use of nix there is to make sure you have all the dependencies needed, and that it'd probably work without nix as long as you have those dependencies (at least it looks like it's doing normal autotools things)
Apackage it for fedora upstream
Adnf install -y nix
Dthat would be so fricken nice. but I don't know much about packaging. I figured how to build it from source with a custom prefix which is a huge advancement.
Aif you can figure out how to build it in fedora without having to install nix beforehand that'd be a good first step
Abasically see what dependencies it needs to the autotools configure will succeed
Dthat is gonna be hard. I could compile it then have it in a tar for installation
Athere's two hard parts to packaging:
1. figuring out dependencies (some of them may not even be in fedora yet!)
2. figuring out what files the program needs after install
1. figuring out dependencies (some of them may not even be in fedora yet!)
2. figuring out what files the program needs after install
DI think all the dependencies in the compiled nix is already there
Ayeah otherwise it would not work
Abut if you are installing nix to build nix, why not just ship the installed version and skip the compilation step?
Dthat is what I'm planning to do
Dwhat do you think the best prefix would be?
/opt/nix-usr /usr/local or something else?Aneither of those things can be used in an ostree container image
Abecause those are rw locations
A/usr/lib/nixPI'd just install to /usr
DI am talking about general installation. And it would be better to have it packaged as an rpm if it goes on the image
PUnless it has its own filesystem structure
Aoh so basically you will maintain your own nix with custom prefix and ship that
Athen maybe just
/var/nixAbut doing this seems more effort than just bind mounting stuff
Dwhy /var/nix?
Ano real reason,
/usr/local doesn't work well because nix does not follow FHSDthis is custom compiled nix. The output dir is pretty much like what you would see in /usr. there is a bin, a share, a lib, and even an etc directory
Aoh it does follow fhs then
Athen that would work in
/usr/localDok
Dbut if it is an rpm, it goes into /usr
Jsome of these rpmfusion mirrors
Jwe should maybe explicitly set one because it's trying to grab stuff from the german mirror and it timed out, etc.
JKicking stuff
AI think we should figure out how to use metalinks
Amaybe it is simple
JI mean for the iso one we just picked one on the east coast right?
Jthough iirc we changed a URL for that just recently
Ayeah but it may fail again
ASherman had to change it because the one I put apparently just died
Jdid you see the fcix mirror thing? I wish rpmfusion was on it, heh
Jok restarting the last job
AI wonder if there's a way of straight up hosting an rpm repo on github 
