!lymvtcwDJ7ZA9Npq:lix.systems

Lix Development

426 Members
(Technical) development of Lix, the package manager, a Nix implementation. Please be mindful of ongoing technical conversations in this channel.141 Servers

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


SenderMessageTime
14 Oct 2025
@raitobezarius:matrix.orgraitobezariusIf sizes are crucial to that goal, np16:24:50
@k900:0upti.meK900tbh I still don't see the value, because like, we can't remove the <algo>:<hex> formats16:24:52
@k900:0upti.meK900And literally everything relevant uses those16:24:57
@k900:0upti.meK900Or SRI16:25:02
@k900:0upti.meK900And we can just keep things using those forever probably16:25:11
@raitobezarius:matrix.orgraitobezariusThe only value I see goes beyond hashes personally16:25:12
@k900:0upti.meK900 convertHash is a massive hammer for a tiny nail 16:25:19
@raitobezarius:matrix.orgraitobezariusI see people who wants to use base32 data inside non-hashes16:25:19
@raitobezarius:matrix.orgraitobezariusFor valid reasons16:25:23
@raitobezarius:matrix.orgraitobezariusIf it ends up constructing convertHash, fine16:25:33
@raitobezarius:matrix.orgraitobezariusBut that's not my sole motive for spawning these primops16:25:49
@emilazy:matrix.orgemily

so Nixpkgs would need

  1. parsing and serialization for SRI and <algo>:<digest> that matches the implementation
  2. a lookup table between hashes and byte sizes

and the code would be Lix-specific (because Nix has chosen that strings cannot contain NUL bytes so the intermediate values would not be valid)

that may be fine

16:26:06
@raitobezarius:matrix.orgraitobezarius I'd say that the code is specific to those who have !(builtins?convertHash) true but idk 16:26:48

Show newer messages


Back to Room ListRoom Version: 10