!sUXcTulPzyhnqOiFPL:helsinki-systems.de

NixOS Perl

43 Members
13 Servers

Load older messages


SenderMessageTime
29 Apr 2024
@mjolnir:nixos.orgNixOS Moderation Botchanged room power levels.15:29:11
1 May 2024
@mjolnir:nixos.orgNixOS Moderation Botchanged room power levels.15:07:24
14 May 2024
@purepani:matrix.orgpurepani joined the room.02:20:12
22 May 2024
@mjolnir:nixos.orgNixOS Moderation Botchanged room power levels.15:26:03
@mjolnir:nixos.orgNixOS Moderation Botchanged room power levels.15:28:17
26 May 2024
@qbit:tapenet.orgqbitis there a .. thing.. that you import into mkShell that grabs all the perl deps? 14:26:05
27 May 2024
@stigo:matrix.orgstigo (away) vcunat: perl 5.40 is coming soon, and I'm thinking to start testing using the RC1 release. is it useful to have a hydra jobset to test that mass rebuild? 12:51:19
@stigo:matrix.orgstigo (away)
In reply to @qbit:tapenet.org
is there a .. thing.. that you import into mkShell that grabs all the perl deps?
not sure what you mean? as in having them in PERL5LIB?
12:52:01
@vcunat:matrix.orgvcunat
In reply to @stigo:matrix.org
vcunat: perl 5.40 is coming soon, and I'm thinking to start testing using the RC1 release. is it useful to have a hydra jobset to test that mass rebuild?
I suppose. If there's a risk of many packaging failing to build. But it's also a question when, e.g. if RC1 is a good point for that or a bit later. (I don't know perl stuff.)
12:52:57
@stigo:matrix.orgstigo (away)the actual 5.40 release is prob coming in a few days, so I'll prob wait for that12:53:38
@qbit:tapenet.orgqbitfor example: https://github.com/qbit/pr-status-pl/blob/main/flake.nix#L5312:53:51
@qbit:tapenet.orgqbiti use direnv to load thaet shell, and for some reason emacs can't see the Git modul12:54:10
@qbit:tapenet.orgqbite12:54:11
@qbit:tapenet.orgqbithm but vim sees it..12:55:24
@qbit:tapenet.orgqbitso idk now12:55:26
@stigo:matrix.orgstigo (away)
In reply to @qbit:tapenet.org
i use direnv to load thaet shell, and for some reason emacs can't see the Git modul
I usually just use let perl' = perl.withPackages(...); and put that in buildInputs
12:55:54
@hexa:lossy.networkhexaI think we can already create a perl-updates jobset on h.n.o12:56:31
@hexa:lossy.networkhexaand we'd tie that to the branch with the same name on nixpkgs12:56:47
@hexa:lossy.networkhexaand you can trigger evals when you're ready12:57:28
@stigo:matrix.orgstigo (away)
In reply to @qbit:tapenet.org
so idk now
If you're adding perlPackages to buildInput, also add perl
12:57:54
@stigo:matrix.orgstigo (away)... which I can see that you're actually doing :) woops12:58:23
@stigo:matrix.orgstigo (away)
In reply to @hexa:lossy.network
and you can trigger evals when you're ready
that would be useful, so I don't have to annoy staging until the update is in a good state
12:58:57
@hexa:lossy.networkhexado you have a specific entrypoint?12:59:29
@hexa:lossy.networkhexa see pkgs/top-level/release-*.nix 13:00:14
@hexa:lossy.networkhexa the simplest would be release-r.nix 13:00:56
@stigo:matrix.orgstigo (away) ah, TIL about entrypoints. should prob create one for perl then that maps trough all perlPackages based on release-r.nix? 13:02:37
@hexa:lossy.networkhexaand maybe you'll also want a an aggreate tested job?13:02:59
@stigo:matrix.orgstigo (away)not sure what that means, but sounds good :P13:03:20
@hexa:lossy.networkhexahaha 😄 13:03:27
@hexa:lossy.networkhexa like the tested jobset on trunk-combined and unstable-small 13:03:40

Show newer messages


Back to Room ListRoom Version: 9