| 26 Oct 2021 |
 David Arnold (blaggacao) | * `/etc/nix/netrc` was it? And then `netrc-file = /etc/nix/netrc` (in the nix config) | 19:17:10 |
 colemickens 🏳️🌈 | You do nix build --profile :/ | 23:02:05 |
| colemickens 🏳️🌈 | cc: Las ^ | 23:02:11 |
| colemickens 🏳️🌈 | approximately: sudo nix "${nixargs[@]}" build --no-link --profile /nix/var/nix/profiles/system "${out}" | 23:02:52 |
 Las | Well, it's better than nothing, thanks colemickens 🏳️🌈 ! | 23:06:32 |
| Las | I made https://github.com/NixOS/nix/issues/5436 | 23:11:29 |
 figsoda | In reply to @tomberek:matrix.org
nix profile remove '.*' ; nix profile install ? :) a useless tip: using .+ instead of '.*' does the same thing and it's shorter | 23:29:04 |
| 27 Oct 2021 |
 Hrafn Blóðbók | What is the URI syntax for gitlab subgroups/subprojects? Example: I want to try out a flake with this convoluted path: https://gitlab.com/veloren/dev/veloren/-/tree/yusdacra/chore/nix | 06:48:48 |
 balsoft | I think git+https is the best you can do :/ | 08:12:01 |
| colemickens 🏳️🌈 | Las: I'm not sure I understood your issue. In the example I gave ${out} was some arbitrary store path (which happened to be a nixos toplevel) | 19:33:46 |
| Las | In reply to @colemickens:matrix.org
Las: I'm not sure I understood your issue. In the example I gave ${out} was some arbitrary store path (which happened to be a nixos toplevel) Yes, you're right. | 19:34:16 |
| Las | I thought that that didn't work, since there is nothing to build. | 19:34:37 |
| Las | it's not intuitively clear from the name. | 19:34:44 |
 Enzime | In reply to @sudoreboot:matrix.org
What is the URI syntax for gitlab subgroups/subprojects? Example: I want to try out a flake with this convoluted path: https://gitlab.com/veloren/dev/veloren/-/tree/yusdacra/chore/nix as far as I understand, that's just the name of the branch so when you specify the flake input you just need to specify ref = "yusdacra/chore/nix"; | 23:48:15 |
| balsoft | In reply to @enzime:nixos.dev
as far as I understand, that's just the name of the branch so when you specify the flake input you just need to specify ref = "yusdacra/chore/nix"; I think the problem is veloren/dev/veloren | 23:57:22 |
| 28 Oct 2021 |
| Enzime | inputs.veloren.url = "git+https://gitlab.com/veloren/dev/veloren.git?ref=yusdacra/chore/nix"; works for me :) | 00:10:13 |
| balsoft | Well yeah | 00:12:51 |
| balsoft | But that will be not very efficient | 00:12:59 |
| balsoft | gitlab:foo/bar is better | 00:13:04 |
| Enzime | In reply to @balsoft:balsoft.ru
But that will be not very efficient oh why's that? | 00:14:11 |
| balsoft | gitlab: just fetches a pre-made tarball | 00:14:53 |
| balsoft | And the git fetcher is meh | 00:15:03 |
| balsoft | There are some details in either this room or the #nix-dev:nixos.org | 00:15:21 |
| balsoft | I don't remember exactly, sorry :D | 00:15:27 |
| Enzime | $ nix flake check "gitlab:veloren/dev/veloren?ref=yusdacra/chore/nix"
error: URL 'gitlab:veloren/dev/veloren?ref=yusdacra/chore/nix' contains multiple branch/tag names
| 00:30:38 |
| Enzime | yeah definitely looks like gitlab: and github: are built with the fundamental assumption that gitlab:A/B B can't contain slashes | 00:31:13 |
 bew | yeah that's because the flake ref syntax is git{hub,lab}:org/repo/branch?options | 00:57:42 |
 tomberek | gitlab allows for sub-organizations, i'm not dealing with any right now, but this assumption may not work in those cases...... can we just tweak the parsing or spec of the flake ref syntax? | 00:59:30 |
| bew | In reply to @balsoft:balsoft.ru
I think git+https is the best you can do :/ as he said, that's the only way to use a repository at an arbitrary url | 01:00:52 |
| bew | In reply to @balsoft:balsoft.ru
I think git+https is the best you can do :/ * as he said, that's the only way I know to use a repository at an arbitrary url | 01:01:12 |
