!djTaTBQyWEPRQxrPTb:nixos.org

Nixpkgs Architecture Team

233 Members
https://github.com/nixpkgs-architecture, weekly public meetings on Wednesday 15:00-16:00 UTC at https://meet.jit.si/nixpkgs-architecture51 Servers

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


SenderMessageTime
11 Jun 2023
@k900:0upti.meK900 It would be cool to eventually end up with python-modules/by-name though 10:22:06
@k900:0upti.meK900And similar in other sets10:22:10
@hexa:lossy.networkhexacertainly10:22:17
@k900:0upti.meK900But we'll have to do that on a set by set basis I think10:22:32
@piegames:matrix.org@piegames:matrix.orgI think that is mentioned in Future work10:22:43
@syphoxy:matrix.org@syphoxy:matrix.org

how about this..

pkgs/A/B/${name}/package.nix

everything that isn't part of the sharding stays in pkgs/ like where it is now.

the one issue we came up with this is that short name packages become ambiguous but I'm pretty sure the ambiguous case only happens for 1 character package names. if you had a package "ab", that would result in pkgs/a/b/ab/package.nix.

for the single letter packages, which in the most generous of circumstances would be at most 40, we could special case them in a folder pkgs/root/.

10:28:30
@syphoxy:matrix.org@syphoxy:matrix.orgeven if we wanted to expand the sharding out to 3 or 4 levels, the ambiguous case would always be the 1 character package names because the shard .. key? is only 1 character long.10:30:40
@syphoxy:matrix.org@syphoxy:matrix.orgthat is, at any level of the sharding, we can distinguish the shard path from a package because packages must be more than 1 character long in length.10:31:43

Show newer messages


Back to Room ListRoom Version: 9