!jngDrdMgndWibPCYsR:nixos.org

Nix PHP

64 Members
A room for PHP developers running on Nix22 Servers

You have reached the beginning of time (for this room).


SenderMessageTime
9 May 2024
@patka_123:matrix.orgpatka (new account: @patka:envs.net) Pol Jan Tojnar sorry for the PR spam... 12:47:57
@patka_123:matrix.orgpatka (new account: @patka:envs.net) *

Pol Jan Tojnar sorry for the PR spam...

(yes, I know how git works)

12:58:36
10 May 2024
@slytherx:matrix.orgslytherx joined the room.21:33:17
13 May 2024
@patka_123:matrix.orgpatka (new account: @patka:envs.net)

I might be missing something, so I'll just ask here:

The box PHP package is built with php82.buildComposerProject and upstream also has "php": "^8.2" in their composer.json (and .lock). But then why does it also end up in the php81Packages set?

Shouldn't we have some kind of mechanism that uses the php version that composer uses to decide whether or not it belongs in a given package set?

17:24:03
@patka_123:matrix.orgpatka (new account: @patka:envs.net)

Another question:

isn't it kind of problematic that we supply lock files (with a lock for packages where upstream doesn't provide one) using composerLock = ./composer.lock that is generated with only a single php version, while the package is in 3 package sets (phpPackages 81, 82, 83)? Shouldn't we have 3 different generated lock files, or at least generate the lock file using the lowest supported php package set version? (so 81)

19:30:06
@patka_123:matrix.orgpatka (new account: @patka:envs.net)Awesome. The first r-ryantm php package updates are rolling in 🎉21:11:45
@patka_123:matrix.orgpatka (new account: @patka:envs.net) * Awesome. The first r-ryantm php package updates are rolling in 🎉 https://github.com/NixOS/nixpkgs/pull/31146921:11:53
14 May 2024
@drupol:matrix.orgPolThanks for the very useful change!06:05:31

Show newer messages


Back to Room ListRoom Version: 6