<clever>
idealy, man.nix would define a hook in a list, and system-pack.nix would run it
<clever>
bennylb: if you set programs.man.enable = false;, it will omit man-db from the system packages, and skip the .man output of every package in the systemPackages
<clever>
it just ignored the boot priority if uefi was on
<clever>
Tipping_Fedora: i had to entirely disable uefi to even make linux boot on my system
<clever>
Tipping_Fedora: ive never gotten uefi to actualy boot on any of my systems, and i havent heard anything about how to configure it to dual-boot
<clever>
that does sound like it would help with things
<clever>
and there are more complex rules on where it has to go
<clever>
and youll never find it again
<clever>
if you dont make it indirect, it will get lost within /nix/var/nix
<clever>
i just keep them in home
<clever>
it can be put anywhere you can write to
<clever>
and i dont think it allows it in the store at all
<clever>
mainly so you can delete it later
<clever>
and as long as that symlink remains there, hello cant be GC'd
<clever>
i now have a symlink in my home dir, that points to the build of hello
<clever>
if the user puts a set of mods into ~/.nixpkgs/ and then does factorio.override { mods = [ ./mod1.zip ./mod2.zip ./mod3.zip ]; } in config.nix
<clever>
./modfoo.zip is one way around that
<clever>
i also had to deal with the auth wall just for the game itself
<clever>
ah yeah
<clever>
so it can have deps
<clever>
maybe also make those entries attrsets
<clever>
joepie91: i think the user would need to provide a list of either fetchurl's or ./modfoo.zip's
<clever>
ah, that helps
<clever>
joepie91: yeah
<clever>
joepie91: for chromium, i believe it accepts a cli arg, and its simpler to put stuff elsewhere
<clever>
joepie91: so i had to copy the ts binary, and symlink everything that wasnt changing, just to put the plugins in a different derivation
<clever>
joepie91: in the case of teamspeak plugins, it tries to follow any symlinks and find the real ts binary, then look relative to that
<clever>
i'm a dude :P
<clever>
dcz: use something like fetchurl or fetchFromGithub to download that revision, and import the result of the fetch
<clever>
thats harder to notice then the join-spam
<clever>
qknight: do you want to build a custom project, or all of nixpkgs?
<clever>
qknight: 32 or 64bit machine?
<clever>
unlmtd[m]: we also have #arcane-chat on freenode already
<clever>
unlmtd[m]: me and taktoa also have plans for an entire chat program, text+voice+video
<clever>
unlmtd[m]: a list of random things i have plans to finish, a gui installer for nixos, ssh agent forwarding in nix-build, a haskell display manager for nixos, fuse mounting for /nix/store
<clever>
ive memorized large chunks of nix and nixpkgs code, and have ideas on how to improve a number of htings
<clever>
gchristensen: oh, and i think this part of the manual needs work, using a builder like that can often completely break the ability to override things
<clever>
jophish: you wouldnt replicate the commands exactly, but it would remind you about weird things you may have had to edit
<clever>
cant remember who has push access to accept it
<clever>
gchristensen: also, i need to look into that ssh agent forwarding idea with nix
<clever>
and it could just throw away $out when your done, impurities are not allowed in the real /nix/store!
<clever>
gchristensen: another nix-shell mode, beyond --pure, where it just treats nix-daemon as an ssh server, and gives you a shell inside a real sandbox
<clever>
gchristensen: oh, that gives me an idea
<clever>
so i had to manualy make $out, and give myself write, to simulate a nix sandbox
<clever>
and root gives it write to the inputs and doesnt reproduce the failure
<clever>
but a normal nix-shell installPhase fails, because it also lacks write to $out
<clever>
(as it should!)
<clever>
and because i setup nix-daemon on the mac, it lacked write to its inputs
<clever>
one of the install phases was trying to install things to a dependency
<clever>
which reminds me of a bug i saw in qt on osx
<clever>
so you must damage the build state to even open a shell in it
<clever>
and if that already exists, nix-shell fails
<clever>
and nix-shell'ing creates a __nix_qt5__ in the pwd
<clever>
and some things like QT need a preconfigure hook ran to make qmake even function
<clever>
gchristensen: for that, i build with -K, then nix-shell and cd
<clever>
and the tooling has known log files that it hides info in
<clever>
may be of more use in standardized languages like haskell or rust, where there is a standard package format already
<clever>
but you would need a general idea on what could fail in the future, and make it save things before it fails
<clever>
for example, save config.log to $out, so you can debug it without having to reproduce it locally
<clever>
you can also set failureHook to a snippet of bash, that will do such logging
<clever>
so you could log details on the failure to $out
<clever>
i think hydra also counts that as failed, but lets you download the $out
<clever>
and will cache whatever it left in $out
<clever>
then nix will consider it as finished, not failed
<clever>
lukego: or you could also concatMap in nix to unroll the loop
<clever>
lukego: if srcs= is on the derivation, nix will turn it into a $srcs env variable automaticaly, then you can use a normal bash for loop
<clever>
i also have a different FP_arch
<clever>
Tag_FP_arch: VFPv3-D16
<clever>
jophish: i'm not seeing neon in my rpi2 builds, you may want to double-check that the cpu can support everything listed
<clever>
dcz: then you can just tab-complete any package, or :b hello to build one
<clever>
dcz: nix-repl '<nixpkgs>' to load up nixpkgs
<clever>
though if you have a v7 cpu, it should just work on v6 and v7
<clever>
and -A as well, which shows sub-arch level stuff (v6 vs v7)
<clever>
Tag_CPU_name: "7-A"
<clever>
root@raspberrypi:~# /nix/store/rbd67ylkmx2fpci7k4d4kaf6lnwrikyv-binutils-2.28/bin/readelf -A /nix/store/rbd67ylkmx2fpci7k4d4kaf6lnwrikyv-binutils-2.28/bin/readelf
<clever>
jophish: try running an arm objdump against the ghc with -d
<clever>
root@raspberrypi:~# /nix/store/rbd67ylkmx2fpci7k4d4kaf6lnwrikyv-binutils-2.28/bin/objdump -d /nix/store/rbd67ylkmx2fpci7k4d4kaf6lnwrikyv-binutils-2.28/bin/objdump | less
<clever>
jophish: one min
<clever>
ah
<clever>
jophish: one trick, you can copy that shell script to $HOME, then just edit the right bash into the copy, and try running it
<clever>
jophish: ah, that will need to be fixed then
<clever>
jophish: its an aarch64 cpu right?, does it have backwards compat? which also has to be enabled in the kernel