!djTaTBQyWEPRQxrPTb:nixos.org

Nixpkgs Architecture

216 Members
Discussions about Nixpkgs' architecture - https://github.com/NixOS/nixpkgs/labels/architecture47 Servers

Load older messages


SenderMessageTime
8 Sep 2023
@tomberek:matrix.orgtomberek infinisil: Amazing talk today. Very well done. Bravo! 22:54:03
@infinisil:matrix.orginfinisilThanks! ☺️22:55:26
@infinisil:matrix.orginfinisil
In reply to @figsoda:matrix.org
just implemented the feature in nix-init, I think one thing that would help is if some constants and shard_for_package are exposed in a crate
It is internal, but we could maybe just mark it as such. Can you open an issue or a PR to discuss this?
22:59:40
@figsoda:matrix.orgfigsoda
In reply to @infinisil:matrix.org
It is internal, but we could maybe just mark it as such. Can you open an issue or a PR to discuss this?
https://github.com/NixOS/nixpkgs/issues/254122
23:06:46
@figsoda:matrix.orgfigsodanot much more information aside from what was already said, but this would be a good place to aggregate the discussion23:07:27
@infinisil:matrix.orginfinisil figsoda: Can you ping @nixpkgs-architecture/team in the issue so it's going to the teams notifications? That would be great :) 23:12:53
@infinisil:matrix.orginfinisilUpdating it should work23:12:58
@figsoda:matrix.orgfigsodaupdated the issue to ping @nixpkgs-architecture and @nixpkgs-architecture/team since the latter wasn't giving me a preview23:15:23
@infinisil:matrix.orginfinisilAh darn, yeah I think we need to push some people to move the architecture team into the nixos org, because apparently these pings don't work :/23:31:36
@infinisil:matrix.orginfinisil figsoda: So maybe just ping me and @roberth 23:32:23
@infinisil:matrix.orginfinisilSorry for the trouble 😅23:32:59
@figsoda:matrix.orgfigsodano worries23:37:19
9 Sep 2023
@quantenzitrone:matrix.org@quantenzitrone:matrix.orgjust watched the talk on media.ccc.de 👏👏👏09:20:54
@edwtjo:fairydust.spaceEdward Tjörnhammar joined the room.12:37:32
12 Sep 2023
@cifre:matrix.org@cifre:matrix.org joined the room.00:44:33
@piegames:matrix.org@piegames:matrix.orgJust a random idea, what if the automatic migration skipped all packages with open PRs at first to not make any conflicts? Then do one or two more such runs in the hope of catching some more packages, and then the assumption is that everything left is mostly old stuff that is allowed to conflict09:03:19
@rick:matrix.ciphernetics.nl@rick:matrix.ciphernetics.nlI thought the migration would take care of that by giving git enough hints? Or doesn't that work (well enough)?10:27:54
@piegames:matrix.org@piegames:matrix.orgWell yes but it still requires rebasing10:28:21
@piegames:matrix.org@piegames:matrix.orgNot sure how many PRs are even affected, and if it's worth it. Just an idea10:28:37
@infinisil:matrix.orginfinisil piegames: Hmm yeah I discussed this before, my main argument for not doing this is the complexity of doing so 10:32:42
@piegames:matrix.org@piegames:matrix.orgWhat complexity? (not rhetorical question)10:33:14
@infinisil:matrix.orginfinisilI wonder if it's worth it, because rebase PR's should be fairly quick on an individual basis, whereas implementing this requires searching through all PR's (automated of course), and then adding those to an exception list or something, having to decide when to do it anyways10:33:49
@piegames:matrix.org@piegames:matrix.orgThough I'd be interested in some numbers here, like how many pull requests and how many packages are affected by this anyways? How many of these pull requests are younger than three months?10:34:49
@infinisil:matrix.orginfinisilAnd how many PR's will not have to rebase because of this? I guess the turn-over rate is fairly high, just waiting some weeks probably gets a high percentage10:34:56
@profpatsch:augsburg.one@profpatsch:augsburg.onepiegames: I had the same idea during nixcon, but honestly I think it’s totally feasible to require PRs to be rebased on top of master10:35:42
@profpatsch:augsburg.one@profpatsch:augsburg.oneSince that parallelizes well10:35:48
@qyliss:fairydust.spaceAlyssa Rosspresumably we could just use "Rebase and Merge" in the UI, as long as git can tell what's going on? 10:36:13
@profpatsch:augsburg.one@profpatsch:augsburg.oneofc long feature branches might hate that, but they can merge master back into themselves10:36:24
@qyliss:fairydust.spaceAlyssa Rossmakes the history (and especially bisects) easier too10:36:26
@piegames:matrix.org@piegames:matrix.org
In reply to @qyliss:fairydust.space
presumably we could just use "Rebase and Merge" in the UI, as long as git can tell what's going on?
This would be a deviation from us currently having merge commits everywhere.
10:37:06

Show newer messages


Back to Room ListRoom Version: 9