Nix PHP | 74 Members | |
| A room for PHP developers running on Nix | 21 Servers |
| Sender | Message | Time |
|---|---|---|
| 17 Mar 2024 | ||
Just for my understanding. Providing the php version outside of the package itself is a historical thing? I find it a bit strange to not just pick the correct version in the package? | 11:05:32 | |
I mean the callPackage with the provided php version. Instead of just getting php82 as an input to the package itself | 11:07:01 | |
| Not really, it is still the "usual" approach when it is expected that most of the packages will work fine with the default values (or will at some point in the future) But yes both work | 11:18:33 | |
| Makes sense, thanks! | 11:19:47 | |
| https://github.com/NixOS/nixpkgs/pull/296617 | 11:28:22 | |
| (in the end I ended up with just copying what tgerbet created because that was a nicer way of solving it than what I had) | 11:29:14 | |
| I wonder if I should package Laravel adjacent (ish) stuff like laravel-zero and phpinsights. I personally will not use them, but it's also very little effort to maintain them. Other people do use these tools | 12:35:06 | |
| It's fine to package them for sure. Even if I don't use these tools and even if I don't like the Laravel philosophy. | 12:38:11 | |
| I even actively discourage people to use it. But it is what it is. Normally packaging stuff that you don't use yourself is kinda discouraged. But I don't mind maintaining it, and dont see myself leaving | 12:43:20 | |
| But hexa is going to tell me differently :p | 12:43:43 | |
| hah 😄 | 12:48:09 | |
| thanks for digging into it | 12:48:14 | |
| I kinda disagree with using all-packages.nix for overrides most of the time, because stale overrides often get missed | 12:48:55 | |
| the file is too unwieldy for anyone to quickly want to check | 12:49:20 | |
| Yep | 12:51:40 | |
| what surprises me is that the derivation and module both construct their own php instance | 12:51:46 | |
| That was my initial thought seeing it for the first time. But also can get behind the override reason from the docs @tgerbet shared earlier | 12:52:12 | |
| 12:52:19 | |
| this was that I tried myself | 12:52:24 | |
| kinda because
| 12:53:01 | |
| so it does include all extensions already? | 12:53:12 | |
| * so it does include alot extensions already? | 12:53:21 | |
| * so it does include alot of extensions already? | 12:53:25 | |
| trimming it down was an afterthought really | 12:53:38 | |
| did I understand that wrong? | 12:54:01 | |
| ok, I am stupid … my local staged changes do actually work. | 12:55:09 | |
| They are not all enabled but yes | 12:55:25 | |
| Hum in this case it should work out of box | 12:56:10 | |
and instead of constructing it twice, wouldn't it be better to expose and reuse it as engelsystem.php | 12:56:22 | |
In reply to @hexa:lossy.network No, not stupid, smart. Because now I had the opportunity to learn a few things I hadn't seen before ^^ It was for the greater good | 12:56:41 | |