!djTaTBQyWEPRQxrPTb:nixos.org

Nixpkgs Architecture Team

234 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
20 Jun 2023
@gytis-ivaskevicius:matrix.orgGytis IvaskeviciusI found what yall been looking for - typed nix 😄 https://www.npmjs.com/package/nijs (tho needs to be converted to ts :D)16:07:37
@gytis-ivaskevicius:matrix.orgGytis Ivaskeviciusin all seriousness, I'd love to see someone implement some project using dhall (thus treating nix as compilation target). tho probably not the most productive use of anyones time16:09:07
@figsoda:matrix.orgfigsodanijs (assuming it's pronounced nice)16:10:19
@gytis-ivaskevicius:matrix.orgGytis Ivaskeviciusoh, i did not realize that 😄16:11:17
@gytis-ivaskevicius:matrix.orgGytis IvaskeviciusJust searched github, unfortunatelly it does not seem that anyone did any progress on that front. till this day this is the closest we have: https://github.com/dhallix/packages https://github.com/dhallix/nix-derivation/tree/master/examples16:19:27
@emilazy:matrix.orgemilyNickel is more likely to succeed on that front18:59:08
@emilazy:matrix.orgemilyDhall is I think not sufficiently powerful nor ergonomic for nixpkgs18:59:35
@profpatsch:augsburg.oneprofpatschdhall is also not lazy nor efficient20:43:33
22 Jun 2023
@archive:matrix.org@archive:matrix.org set their display name to archive.matrix.org/faq.05:26:27
23 Jun 2023
@roberthensing:matrix.orgRobert Hensing (roberth)We should really really write down migration guidelines10:23:47
@roberthensing:matrix.orgRobert Hensing (roberth) "manually" holding off migration disasters like this is a fucking drain https://github.com/NixOS/nixpkgs/pull/238331#pullrequestreview-1494880730 10:24:34
@roberthensing:matrix.orgRobert Hensing (roberth)apologies for the rude language10:24:41
@raitobezarius:matrix.orgraitobezariusI would argue that it would be a good occasion to clarify10:27:05
@raitobezarius:matrix.orgraitobezarius(1) Nixpkgs Internal Changes "release notes" (how to communicate API breakages, etc.) across our users and more10:27:20
@raitobezarius:matrix.orgraitobezarius(2) Public API vs private API promises (not necessarily a solution, but maybe have an easy way to declare from the get-go "this is private", "this is public")10:27:46
@raitobezarius:matrix.orgraitobezarius(I don't think versioning at this step makes any sense)10:28:04
@qyliss:fairydust.spaceAlyssa RossI don't see how a public vs. private distinction could make sense for Nixpkgs10:28:43
@roberthensing:matrix.orgRobert Hensing (roberth)The release notes are often quite useless with stuff like renames that are already handled by the system. Just look at the log.10:29:15
@roberthensing:matrix.orgRobert Hensing (roberth)Public: everything that's documented10:29:22
@qyliss:fairydust.spaceAlyssa RossWhat does "documented" mean in this case?10:29:49
@roberthensing:matrix.orgRobert Hensing (roberth)Private: use common sense. Don't import files except the listed ones <list>10:29:53
@piegames:matrix.org@piegames:matrix.org
In reply to @roberthensing:matrix.org
The release notes are often quite useless with stuff like renames that are already handled by the system. Just look at the log.
We could easily add the release notes editors to summarize these instead
10:29:54
@roberthensing:matrix.orgRobert Hensing (roberth)Documented in the manual10:30:01
@qyliss:fairydust.spaceAlyssa Rossah10:30:06
@qyliss:fairydust.spaceAlyssa RossI'm not sure we're ever promised that stable and unstable would be API-compatible10:32:08
@roberthensing:matrix.orgRobert Hensing (roberth)Well, about time then10:32:46

Show newer messages


Back to Room ListRoom Version: 9