| 13 May 2024 |
 raitobezarius | In reply to @easrng:yuri.im
do they get the nicer progress display without flakes? yes | 23:55:26 |
 Qyriad | In reply to@easrng:yuri.im
do they get the nicer progress display without flakes? yes, that's part of nix3/new-cli, not flakes, but you can actually get them in the old CLI too: nix-build --log-format bar-with-logs '<nixpkgs>' hello | 23:55:27 |
| Qyriad | In reply to@qyriad:katesiria.org
there are four kinds of installables:
flakeref + attrpath a full /nix/store path a nix expression and an (optionally empty) attrpath, with --expr (or -E in Lix) a nix file and an (optionally empty) attrpath, with --file/-f
In order:
$ nix build "nixpkgs#neovim"
$ nix build /nix/store/hfvwharmvin21pbxqapzbmwy7gmf8l8v-neovim-0.9.5.drv
$ nix build --file '<nixpkgs>' neovim
$ nix build --impure --expr 'let pkgs = import <nixpkgs> { }; in pkgs.neovim'
all do the same thing | 23:57:00 |
 samrose | So maybe there are some ideas in Lix to improve flakes over time eh? | 23:57:07 |
| Qyriad | that's the hope! | 23:57:14 |
| Qyriad | oh yeah you can also use flakes with the old CLI. I don't think this is documented literally anywhere, but:
nix-build 'flake:nixpkgs' -A neovim | 23:58:56 |
| samrose | In reply to @qyriad:katesiria.org
oh yeah you can also use flakes with the old CLI. I don't think this is documented literally anywhere, but:
nix-build 'flake:nixpkgs' -A neovim Someone did show me that a while back at nixcon in paris :) | 23:59:35 |
| Qyriad | (the Nix docs team refusing to document experimental features really just does more harm than good, imho) | 23:59:59 |
| 14 May 2024 |
| samrose | It seems like the nix run approach could be a candidate way to test non-nixos functionality of Lix on Nix I've been using it to do some tests of building postgres, postgres extensions, and then running pgtap and other postgres tests on a package set. I guess that is more for testing the runnig of software packaged with nix
It seemed the nix tests are mostly just like bash integration tests of the cli executable. | 00:03:07 |
| samrose | I am not sure if it would help to have some matrix of machines (x86_64-linux, wsl2, macos, aarch64-linux) that could test the installation of Lix, and then some nix profile install followed by maybe not nix run, but rather just using what was installed, and checking integrity of the Lix installation and package installation, and ... I don't know immediately what else | 00:07:30 |
| samrose | In reply to @samrose:matrix.org
I am not sure if it would help to have some matrix of machines (x86_64-linux, wsl2, macos, aarch64-linux) that could test the installation of Lix, and then some nix profile install followed by maybe not nix run, but rather just using what was installed, and checking integrity of the Lix installation and package installation, and ... I don't know immediately what else the open source postgresql project uses cirrusci https://cirrus-ci.org/faq/#are-there-any-limits which offers a matrix of builders for free to open source projects with the limitations in that link (not the only solution but it might help to use resources that are free to open source projects potentially) | 00:10:39 |
| Qyriad | hmm, that is good to know | 00:13:06 |
| Qyriad | aarch64-linux is what we are most lacking in right now | 00:13:19 |
| samrose | anyway, I'd love to help and am flexible about how I do it, when it comes to helping test this stuff somehow | 00:13:57 |
| samrose | I guess at cirrus that use containers, although it could still be feasible to use their containers to build and test builds I believe | 00:14:24 |
| samrose | at cirrus they only offer containers for aarch64-linux I mean | 00:14:43 |
| samrose | I don't think github has rolled out their aarch64-linux runners yet other than some beta testing thingy | 00:15:13 |
| samrose | cirrus uses yaml or the (imo kinda wack) starlark language. But it's also possible to just break out into using nix/nix run to script these things once nix is installed on the machine anyway of course | 00:17:19 |
| samrose | there may be some other ci companies that offer free services to open source projects too, I can look around and see | 00:18:33 |
| Qyriad | we aren't allergic to yaml or starlark tbh | 00:21:54 |
| samrose | https://circleci.com/open-source/ seems to have credits too. Although I don't know the whole background on these companies, so not meant to be an endorsement of any of them per se but the "free to open source" part sounds cool | 00:25:54 |
| samrose | I have used cirrus in the past and at least as a ci service, it worked decently | 00:26:43 |
| Qyriad | we would need something that we could integrate into gerrit at minimum, and ideally really into our existing CI | 00:28:17 |
| samrose | what is the existing CI based on? | 00:29:22 |
| samrose | was it buildbot? | 00:29:45 |
| Qyriad | yep | 00:29:55 |
| samrose | I had not known about buildbot really before just looking it up now :)
But it looks like it's a nice framework to use in lieu of just running scripts | 00:31:45 |
 Lunaphied | Compared to just running custom scripts yeah it's better but it's really not far off | 00:32:06 |
| raitobezarius | It's xonsh with a server | 00:33:03 |
| raitobezarius | I am not sure I cannot parse if Cirrus CI offer aarch64 Linux builder on demand or on spot or something | 00:34:04 |
