worldofpeace has quit [Read error: Connection reset by peer]
worldofpeace_ has joined #nixos-dev
drakonis has quit [Remote host closed the connection]
jtojnar has quit [Ping timeout: 252 seconds]
phreedom has quit [Remote host closed the connection]
phreedom has joined #nixos-dev
orivej has quit [Ping timeout: 246 seconds]
worldofpeace_ has quit [Ping timeout: 244 seconds]
Lisanna has quit [Quit: Lisanna]
orivej has joined #nixos-dev
__Sander__ has joined #nixos-dev
__Sander__ has quit [Read error: No route to host]
<zimbatm>
is there a standard way to filter derivations and only keep those that match the target platform?
<zimbatm>
terraform-full is unecessarily failing for darwin because a single plugin is not compilable for that platform
__Sander__ has joined #nixos-dev
<LnL>
there's meta.available but that has behaves in unexpected ways in combination allowSupportedSystem
NinjaTrappeur has quit [Quit: WeeChat 2.3]
NinjaTrappeur has joined #nixos-dev
<Mic92>
zimbatm: I am no able to cross-compile direnv.
<Mic92>
s/no//
<Mic92>
s/no/now/
<zimbatm>
aarch64 direnv? :)
<Mic92>
zimbatm: this what i tested, but should work for anything go can run on. I still need a small fix for buildGoPackage so also other go packages work as expected.
<zimbatm>
nice
<zimbatm>
does it work for go programs that have C dependencies?
<Mic92>
zimbatm: do you have a simple example in nixpkgs?
<zimbatm>
terraform-providers-libvirt is not exaclty simple but the last one I touched
<Mic92>
Combined with the static overlay this could be an interesting for go developers.
<Mic92>
s/an//
<arianvp>
what is the difference between pkgs.buildPackages and pkgs?
<arianvp>
I sometimes see pkgs.buildPackages.stdenv instead of pkgs.stdenv
<zimbatm>
pkgs.buildPackages is new to me too
<zimbatm>
as I understand this is the set of packages used to bootstrap the stdenv
drakonis has joined #nixos-dev
<ekleog>
Mic92: oh, you're doing a new buildGoPackage? I have a friend currently trying to make a derivation for a go package, and it looks… hard :/ maybe I can tell him if you're redoing buildGoPackage anyway :)
<Mic92>
ekleog: I don't see the need to redo it.
<ekleog>
Mic92: oh, so just a fix? nvm then, hoped it would handle weird issues, will open an issue on the tracker if we can't make it work :) (should we tag you on it?)
<Mic92>
ekleog: compared to other languages go seems pretty to me, when it comes to compiling it. Rust causes way more headaches.
<ekleog>
hmm'k :) I really have never used it apart from trying to help said friend, so can't comment about that :)
<zimbatm>
ekleog: tell your friend to vendor all his dependencies
<Mic92>
zimbatm: for each force push basically.
<Mic92>
zimbatm: or that go 1.11 modules
<zimbatm>
yeah
<zimbatm>
if you want to punish someone, put a commit mentioning them in nixpkgs master
<Mic92>
you will also be mentioned in each cherry-picking fork.
<zimbatm>
they will be notified for each branch picking up the commit
<ekleog>
zimbatm: that's exactly the issue, literally “cannot find package "github.com/asdine/storm" in any of:”, but it looks like `go2nix`-generated `goDeps` doesn't avoid it… or do you mean something else by “vendor all his dependencies”?
<zimbatm>
ekleog: use godep or govendor to copy all the dependencies in the vendor/ folder of that repo
<zimbatm>
then commit that and you are good to go
<Mic92>
ekleog: depends if you are a packager or project owner.
<zimbatm>
unless it's a library, I say vendor all of the things
<Mic92>
ekleog: sometimes you need to run go2nix from a subdirectory for the dependency to pick up. For example the cmd package.
<ekleog>
oh ok thank you two! (it's just packager here, not project owner, so the vendor option is kind of meh)
<ekleog>
zimbatm: stupid question: is there no equivalent to buildRustPackage that'd automatically godep / govendor?
* ekleog
trying to apply what he “knows” about rust packaging to go, and nothing applies, buildGoPackage appears to be halfway between buildRustPackage and carnix
<zimbatm>
not that I know of
<ekleog>
ok thanks! :)
Lisanna has joined #nixos-dev
<Mic92>
ekleog: that might be possible with go 1.11 modules, before there were too many different go packaging tools on the market.
<Mic92>
But I don't really miss having that fixed input derivation from buildRustPackage. It make some changes hard.
<ekleog>
yeah… otoh it's kind of simple to make it work and doesn't need lots of documentation, compared to the buildGoPackage / carnix approaches :)
aminechikhaoui has quit [Excess Flood]
aminechikhaoui has joined #nixos-dev
<Mic92>
Does anyone remember a guy on NixCon, who wanted to make nix (nix-daemon) work without root permissions?
Lisanna has quit [Remote host closed the connection]
<Mic92>
arianvp: zimbatm buildPackages are simply packages build for the architecture the build is running on. For example one would use buildPackages.go to build for cross compiling.
<Mic92>
this is aquivalent to put packages in nativeBuildInputs
<Mic92>
I should also do a writeup about the topic
jtojnar has joined #nixos-dev
<zimbatm>
ahh ok
<zimbatm>
has this changed recently?
vasarmilan has joined #nixos-dev
vasarmilan has left #nixos-dev [#nixos-dev]
<gchristensen>
srhb, andi-: the build machines are all sitting pretty comfortable at 40% cpu usage. maybe we should increase their jobs?
<yl[m]>
hey guys, I would love to be part of nixpkgs contributor (push access) and I would like to know what are the prerequisites for me to apply and where can I apply
<yl[m]>
drakonis: I believe I can pass all requirements (I have 50 PRs), I have to brush up a bit on the overall workflow (such as commit policy and release policies) but I think I can be ready pretty quick on that
<yl[m]>
the discussion has not yet settled so I assume that I would be the guinea pig of the process :)