!QCCCSJHEsTIfozrZxz:nixos.org

Nix + Go

236 Members
Go packaging for and with Nixpkgs. | Be excellent to each other.48 Servers

Load older messages


SenderMessageTime
5 Apr 2024
@diamondburned:matrix.orgDiamond (it/she)I opened this Discourse back in 201915:32:42
@diamondburned:matrix.orgDiamond (it/she)unrelated but kinda crazy to think I would see tomberek like 4 years after that without even remembering I made this post lol15:33:24
@alexou:femtodata.comAlex Ou joined the room.17:53:37
@jrick:zettaport.comjrickhttps://github.com/NixOS/nixpkgs/pull/301373 why was this merged directly into staging branch instead of master?18:18:51
@jrick:zettaport.comjricksecurity policy maybe?18:19:48
@sumner:nevarro.spaceSumner EvansI think to avoid massive amounts of rebuilds18:21:16
@jrick:zettaport.comjricki see some other go updates were merged to master first, and i think staging is preferably used over master to reduce rebuilds18:35:23
@qbit:tapenet.org@qbit:tapenet.orgit all depends on the number of rebuilds19:36:20
@qbit:tapenet.org@qbit:tapenet.orgsome of the other updates are for non-default versions of go.. so they only have like 10 things dependent on them19:36:38
7 Apr 2024
@fractivore:cyberia.clubsymys changed their display name from symys to symyƨ.07:58:17
@fractivore:cyberia.clubsymys changed their display name from symyƨ to sγmγƨ.08:01:04
@fractivore:cyberia.clubsymys changed their display name from sγmγƨ to SYMYƧ.08:08:40
11 Apr 2024
@withoutwithin:matrix.org@withoutwithin:matrix.org joined the room.21:26:50
17 Apr 2024
@k900:0upti.meK900 ⚡️ changed their display name from K900 ⚡️ to K9Ö0.17:16:42
@k900:0upti.meK900 ⚡️ changed their display name from K9Ö0 to K900.17:21:54
@k900:0upti.meK900 ⚡️ 17:21:54
18 Apr 2024
@fractivore:cyberia.clubsymys left the room.02:37:22
21 Apr 2024
@bogusthing30:matrix.orgbogusthing30 joined the room.04:00:46
22 Apr 2024
@frederic:scs.ems.host@frederic:scs.ems.host changed their display name from Frédéric Christ to Frédéric Christ 🌴 29.04.-13.05..10:03:42
23 Apr 2024
@dnrix:matrix.orgdnr joined the room.02:32:53
@dnrix:matrix.orgdnr I want to build a package with the binary of one of my tests (using the go testing framework). I'm using buildGoModule for everything else so I'd like to use that too. I thought this would be easy but the best I could figure out was to use buildGoModule and then just override buildPhase = "go test -c -o mytest ./mytest"; (and then installPhase to copy it into $out). That works but I'm missing things like tags and other build flags. I can add those back but it's starting to feel a little wrong.. is there a better way to do this? 03:00:10
@qbit:tapenet.org@qbit:tapenet.orgbuilding a binary via tests?!13:24:29
@qbit:tapenet.org@qbit:tapenet.orgthat's weird13:24:30
@jrick:zettaport.comjrickyou build a binary every time you run tests!13:35:10
@qbit:tapenet.org@qbit:tapenet.orgbut saving it for usage elsewhere..13:37:55
@katexochen:matrix.orgPaul Meyer (katexochen)It is not weird, commonly done to run integration tests etc. Especially when building with nix, it allows running integration tests outside the sandbox.16:51:01
@katexochen:matrix.orgPaul Meyer (katexochen)At work we have a modified version of buildGoModule. Sadly overriding phases isn't possibly/easy, IIRC we copy most of the builder to make the modification.16:52:44
@katexochen:matrix.orgPaul Meyer (katexochen)* At work we have a modified version of buildGoModule for this. Sadly overriding phases isn't possibly/easy, IIRC we copy most of the builder to make the modification.16:53:06
@qbit:tapenet.org@qbit:tapenet.orgfirst time I have encountered it17:04:39
@dnrix:matrix.orgdnrThe specific reason in this case I need to run the test binary as root and I don't want to run the whole toolchain as root. Also I want to copy it to another system22:59:25

Show newer messages


Back to Room ListRoom Version: 9