| 15 Aug 2021 |
 Mic92 | Autotools is also not really maintained anymore. There was only a few months ago someone paid to do some fixes. | 21:52:14 |
 nixinator | In reply to @mic92:nixos.dev
Autotools is afaik more restricting than python. Have you tried installing autotools, coreutils, make, etc on windows? * no because these are unix tools. ;-) | 21:52:16 |
| nixinator | yeah...it's a problem. | 21:52:29 |
| Mic92 | Hence it bitrots as operating systems and toolchains get updated. | 21:52:50 |
| nixinator | sigh...you are absolutel correct. | 21:53:15 |
| nixinator | * sigh...you are absolutely correct. | 21:53:29 |
| nixinator | so whats the solution @mic92 | 21:56:07 |
| nixinator | also, i'd be interested to see what fixes you made to autotools? i strongly believe perfect design is not how many features you can add, but when you can't take anything more away, same goes for dependencies and code reuse. In a perfect world a single application is self contained, and doesn't rely on anything. But it's far from a perfect world, hence DLL hell, dependency nightmares... and it 'work's on my machine syndrome'. That's why i picked up nix, because it really is trying to solve these problems, without containers like docker to build complex software projects . | 22:07:32 |
| 16 Aug 2021 |
 Las | In reply to @nixinator:nixos.dev
so whats the solution @mic92 You could make an ad-hoc build system | 07:35:29 |
| Las | It doesn't have to do caching, since it's for bootstrapping | 07:35:40 |
 Gytis Ivaskevicius | Latest nixpkgs fails to build nix due to , withAWS ? !enableStatic && (stdenv.isLinux || stdenv.isDarwin), aws-sdk-cpp | 12:21:29 |
| Gytis Ivaskevicius | 👀 | 12:21:35 |
| Gytis Ivaskevicius | and its release-21.05 | 12:21:46 |
| Gytis Ivaskevicius | i swear i must be high or something super unprofessional happend | 12:22:07 |
 toonn | The branch or the channel? Because I assume the channel has checks to prevent propagation when nix fails to build. | 12:24:11 |
| Gytis Ivaskevicius | I guess the branch. Im on flakes | 12:24:34 |
 manveru | Eelco Dolstra: anything left to do for https://github.com/NixOS/nix/pull/4922 ? | 15:52:31 |
 fzakaria | what's the best approach to build Nix incrementally? | 16:44:27 |
| fzakaria | Is it through nix-shell steps? | 16:44:47 |
 tomberek | fzakaria: https://hydra.nixos.org/build/149934349/download/1/manual/contributing/hacking.html | 16:47:19 |
| Mic92 | fzakaria: use nix develop instead of nix-shell so | 16:53:25 |
| Mic92 | nix-shell technically works but nix develop should be faster | 16:53:39 |
| Mic92 | ah. it mentiones that | 16:53:47 |
| fzakaria | yea i guess i could upstream a note mentioning that is preferred if you want incremental since nix-build throws it away in /tmp | 16:54:17 |
| fzakaria | (would be cool if nix-build could make use of a ccache so you get nix-build simple invocation but also incremental) | 16:54:37 |
| fzakaria | also if there are attributes to build individual binaries
nix-build -A nix | 16:54:53 |
| Mic92 | I think there was some impure thing in nixpkgs that did that. | 16:55:10 |
| Mic92 | I rather prefer not a sandbox so if I want to debug stuff. | 16:55:24 |
| fzakaria | oh i see ccacheStdenv; i'll have to read up on that. | 16:58:09 |
| fzakaria | (I haven't enabled nix develop yet.. i'm one of those people... lol) | 16:58:19 |
