| 17 Jul 2025 |
 msgilligan | I think the ideal way would be able to access the PRs branch directly and I've seen flakes that use both a stable and unstable release of Nixpkgs, so I think that approach should work. That would also make it easier to rebase and to adapt for new EA releases after the current EA becomes GA. | 21:37:41 |
 emily | yeah, that very much works | 21:43:06 |
| emily | you don't necessarily need two Nixpkgses since GitHub has magic refs that represent the state if the PR was merged | 21:43:45 |
 Infinidoge 🏳️⚧️ | The unfortunate thing with PR branches vs overlays or grabbing directly is that PR branches usually aren't kept up to date, and usually don't follow with a standard stable branch | 21:43:47 |
| Infinidoge 🏳️⚧️ | Oh good magic ref, that works | 21:43:58 |
| emily | though in the presence of merge conflicts that doesn't work so great :) | 21:44:00 |
| Infinidoge 🏳️⚧️ | If flakes supported patches for inputs the world would be at peace | 21:44:20 |
| Infinidoge 🏳️⚧️ | But alas | 21:44:25 |
| Infinidoge 🏳️⚧️ | IFD | 21:44:26 |
| Infinidoge 🏳️⚧️ | I have hope for Fetch Tree, but only hope | 21:44:35 |
| emily | I don't think fetchTree changes anything there | 21:45:44 |
| Infinidoge 🏳️⚧️ | I think the ideal solution would be an out-of-tree repo exposing packages through flakes and an overlay, with a structure identical to how the packages would be in Nixpkgs, so they can be directly transferred in later | 21:45:47 |
| emily | honestly using the PR refs seems fine to me. I just, like, wouldn't deploy it in pros | 21:46:34 |
| emily | * | 21:46:39 |
| emily | but I wouldn't deploy an EA version in prod to begin with :) | 21:46:51 |
| msgilligan | I need to learn about magic refs then. | 21:49:22 |
| msgilligan | Since I'm (mostly) on Darwin, I use Home Manager, so I would add the JDK-ea Nixpkgs as an additional input. | 21:50:57 |
| msgilligan | * Since I'm (mostly) on Darwin, I use Home Manager, so I would add the JDK-ea Nixpkgs as an additional input (to my flake-based Home Manager config) | 21:51:14 |
| Infinidoge 🏳️⚧️ | In reply to @emilazy:matrix.org
I don't think fetchTree changes anything there Eelco suggested adding a patches option to fetchTree, which would support directly applying patches to an input without IFD
it isn't something that currently exists In Reality though, which is why it's only hope and not anticipation
| 21:51:18 |
| Infinidoge 🏳️⚧️ | In reply to @emilazy:matrix.org
I don't think fetchTree changes anything there * Eelco (supposedly, this isn't directly from him) suggested adding a patches option to fetchTree, which would support directly applying patches to an input without IFD
it isn't something that currently exists In Reality though, which is why it's only hope and not anticipation
| 21:51:30 |
| emily | right | 21:52:21 |
| emily | tbh just maintaining a fork is the most convenient thing, give appropriate tooling | 21:52:48 |
| emily | (starts with a j ends with a ujutsu) | 21:52:58 |
| Infinidoge 🏳️⚧️ | I really need to start looking into jj | 21:53:15 |
| Infinidoge 🏳️⚧️ | I'm used to by sprawling collection of git aliases and am comfortable with git, so I haven't so far, but it's workflow looks a lot more practical | 21:53:43 |
 @softmoonworld:matrix.org | is there a temurin-bin-17 for version 17.0.15+6? Is this an opportunity for me to contribute or am I confused? I only see the jdk17 which is not temurin. I also see openjdk17-bootstrap which is confusing me because it says it's temurin. Love any pointers, and I'd be so happy to submit a PR | 21:54:19 |
| Infinidoge 🏳️⚧️ | temurin-bin-17 == openjdk17-bootstrap, and as of the current master branch, is version 17.0.15 | 21:56:46 |
| Infinidoge 🏳️⚧️ | Unsure about the +6 | 21:56:49 |
| emily | In reply to @infinidoge:inx.moe
I'm used to by sprawling collection of git aliases and am comfortable with git, so I haven't so far, but it's workflow looks a lot more practical IMO it is simpler than Git for beginners and more powerful than Git for experts. | 21:56:55 |
| emily | in this case the nice thing for forks is that it is easy to maintain a merge of 5 branches into one | 21:57:18 |
