!djTaTBQyWEPRQxrPTb:nixos.org

Nixpkgs Architecture Team

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

Load older messages


SenderMessageTime
20 Mar 2024
@philiptaron:matrix.orgPhilip Taron (UTC-8)🫰23:11:37
@philiptaron:matrix.orgPhilip Taron (UTC-8) * 🤞23:11:57
@infinisil:matrix.orginfinisilLol I was wondering about that emoji haha23:12:17
@philiptaron:matrix.orgPhilip Taron (UTC-8)Wrong hand gesture. 😬23:12:31
@philiptaron:matrix.orgPhilip Taron (UTC-8)Crossed something!23:12:45
@infinisil:matrix.orginfinisilOh and if we use GitHub releases to do the distribution, it also makes sense to pin it to the release instead of the store path23:13:42
@philiptaron:matrix.orgPhilip Taron (UTC-8)Yes.23:13:50
@infinisil:matrix.orginfinisilOne minor problem: It's non-trivial like this to allow people to run it locally23:14:37
@philiptaron:matrix.orgPhilip Taron (UTC-8)How so? It'23:15:04
@philiptaron:matrix.orgPhilip Taron (UTC-8) * How so?23:15:09
@infinisil:matrix.orginfinisil Oh yeah should be fine, we can just do full nix-build's then and not worry about fetching pre-built paths 23:15:41
@philiptaron:matrix.orgPhilip Taron (UTC-8)Yeah.23:15:46
@philiptaron:matrix.orgPhilip Taron (UTC-8)People can pay for it.23:16:08
@philiptaron:matrix.orgPhilip Taron (UTC-8)CI doesn't want to.23:16:14
@infinisil:matrix.orginfinisilHaha yes23:16:33
@infinisil:matrix.orginfinisilOkay so, I guess the next thing to do is to have some automated release process that creates the artifacts, I'll look into that23:17:02
@philiptaron:matrix.orgPhilip Taron (UTC-8)Take a look at this repo: https://github.com/sorairolake/qrtool23:17:39
@philiptaron:matrix.orgPhilip Taron (UTC-8)I see that it's being released by github-actions, which is what we want, I think.23:19:20
@infinisil:matrix.orginfinisilYeah sounds good, it's using https://github.com/softprops/action-gh-release23:19:54
@hacker1024:matrix.orghacker1024 joined the room.23:20:05
@infinisil:matrix.orginfinisilAlthough this would involve having to manually push tags, not a fan of that23:20:48
@infinisil:matrix.orginfinisilWould be nicer if it would automatically do a weekly PR, which when merged creates a release23:21:01
@infinisil:matrix.orginfinisilOr so23:21:05
@philiptaron:matrix.orgPhilip Taron (UTC-8)That's totally possible, and since we'll need a machine account anyway to not get stalled on automated PRs, it can absolutely push a tag, I would think.23:22:09
@infinisil:matrix.orginfinisilThe automated update PRs (like https://github.com/NixOS/nixpkgs-check-by-name/pull/14) don't need any special privileges, since it's just a PR23:23:13
@infinisil:matrix.orginfinisilA tag would need more permissions23:23:18
@infinisil:matrix.orginfinisilWe could do something like "For every master push, check if its version number increased, if yes, create a release"23:23:47
@philiptaron:matrix.orgPhilip Taron (UTC-8)Having that in the git metadata is quite nice.23:24:09
@philiptaron:matrix.orgPhilip Taron (UTC-8)Sure, it's more permissions, but it's really nice.23:24:28
@infinisil:matrix.orginfinisilI guess we really don't need a separate machine account for the automated releases23:25:43

Show newer messages


Back to Room ListRoom Version: 9