| 3 Nov 2023 |
 Janne Heß | awesome! that should make it a lot easier | 15:30:51 |
 stigo | Yeah, was considering getting a mac mini... but those prices | 15:31:13 |
| Janne Heß | the arm ones are really nice | 15:31:52 |
| Janne Heß | we have one and run nixos on it for our aarch64 builds | 15:31:59 |
| Janne Heß | sooo powerful | 15:32:06 |
| stigo | It just installs without any weirdness? | 15:32:46 |
| stigo | * NixOS just installs without any weirdness? | 15:32:53 |
| Janne Heß | There's https://github.com/tpwrules/nixos-apple-silicon | 15:33:01 |
| 6 Nov 2023 |
|  @adam:robins.wtf joined the room. | 16:00:47 |
| @adam:robins.wtf | 👋 | 16:01:18 |
| stigo | hey adamcstephens 🐝 :) | 16:27:48 |
| stigo | adamcstephens 🐝: I'm happy to help out with fixing slimserver, prefering to use packages from perlPackages of course. I suggest that we wait a bit for staging-next to be merged into master is it contains a lot of changes to perlPackages, and a clang update that affects darwin packages in particular. Ref: https://github.com/NixOS/nixpkgs/pull/265556#issuecomment-1795211682 | 16:33:51 |
| stigo | Another concern would be the dependency on perl 5.36, as it will be removed from nixpkgs when 5.40 is released. It could be a dependency that wasn't compatible with 5.38, or ofc something in slimserver itself. We should also look at what the problem was there and see if it can be easily patched. | 16:39:49 |
| @adam:robins.wtf | i'm unfamiliar with the perl lifecycle, but it looks like that gives us until 2025 for 5.36? | 17:06:09 |
| @adam:robins.wtf |
To the best of our ability, we will provide "critical" security patches / releases for any major version of Perl whose 5.x.0 release was within the past three years
| 17:07:47 |
| @adam:robins.wtf | and perl 5.36 was released May 28th 2022 | 17:08:01 |
| @adam:robins.wtf | or do we drop releases earlier than upstream stops security patching? | 17:08:25 |
| stigo | A new version of Perl5 is released roughly every year or so, and in nixpkgs we keep the two currently maintained versions. | 17:09:03 |
| stigo | Which today are 5.36 and 5.38 | 17:11:27 |
| @adam:robins.wtf | so 5.36 will be good until roughly may-july next year (depending on release date) | 17:12:09 |
| stigo | Yeah basically | 17:13:09 |
| stigo | Usually backwards compat is not a big issue in perl5, but there are of course some issues :) | 17:14:27 |
| stigo | I've proposed to also only keep one version of perl5 in nixpkgs to make maintenance a bit easier, maybe two if/when perl7 ships. | 17:15:09 |
| @adam:robins.wtf | i suspect that may be fine with slimserver, if we can get it using our perl packages instead of its own | 17:16:00 |
| @adam:robins.wtf | so to try and move forward, am i correct in assuming i should be removing this directory and replacing it with buildInputs ? https://github.com/Logitech/slimserver/tree/public/8.3/CPAN | 17:17:19 |
| @adam:robins.wtf | and if so, any tips to save me the time of manually tracking down all the associated packages? :) | 17:18:05 |
| stigo | In reply to @adam:robins.wtf
so to try and move forward, am i correct in assuming i should be removing this directory and replacing it with buildInputs ? https://github.com/Logitech/slimserver/tree/public/8.3/CPAN I'd guess so, unless something needs to be patched for it to not use the CPAN directory. First I'd check what kind of error messages you get from just using the CPAN directory, likely there are some modules that are not compatible with 5.38 or maybe som nix specific patches that are missing. | 17:19:59 |
| @adam:robins.wtf | it's currently failing with the error in https://github.com/NixOS/nixpkgs/issues/265488 | 17:21:00 |
| stigo | But I think we should wait for staging-next before trying, as it has over 600 commits to perlPackages :) I hope it will be merged into master very soon. | 17:21:08 |
| @adam:robins.wtf | in that CPAN directory is an arch directory which has pre-compiled modules in it | 17:21:32 |
