!OqhvaDMJdKYUicLDiE:nixos.org

Nixpkgs Stdenv

217 Members
70 Servers

Load older messages


SenderMessageTime
3 Dec 2025
@rosscomputerguy:matrix.orgTristan RossWould be cursed to wrap everything in that22:04:54
@aleksi:pikaviestin.fialeksi

Actually I see a bug in my own strncasecmp now, when the strings have different lengths, I will have to fix that

22:04:55
@aleksi:pikaviestin.fialeksi

Oh, and I think the printf patches in mes/libs.nix can affect i686

22:07:00
4 Dec 2025
@grqp:matrix.orgGrqP joined the room.03:15:52
@grqp:matrix.orgGrqPIs this the right channel to ask newb questions about makeWrapper and setup hooks?03:18:15
@rosssmyth:matrix.orgrosssmythDon't ask to ask04:38:45
@rosssmyth:matrix.orgrosssmythjust ask04:38:47
@grqp:matrix.orgGrqP

I'm trying to figure out how to navigate the sources to determine where wrapProgram, makeWrapper are populated. I can see in github the shell script, and that pkgs.makeWrapper copies to setup-hook, but can't find who calls makeSetupHook to trigger that.

Is there a fast way to figure this out without grepping the repo directly?

04:54:53
@winter:catgirl.cloudWinter

grep, tbh… or something like builtins.unsafeGetAttrPos "makeWrapper" pkgs

nonetheless. https://github.com/NixOS/nixpkgs/blob/821f1a2ebab0f13d6d65170d6bd7d2b3a182efdb/pkgs/top-level/all-packages.nix#L728

05:19:23
@winter:catgirl.cloudWinter *

grep, tbh… or something like builtins.unsafeGetAttrPos "makeWrapper" pkgs

nonetheless: https://github.com/NixOS/nixpkgs/blob/821f1a2ebab0f13d6d65170d6bd7d2b3a182efdb/pkgs/top-level/all-packages.nix#L728

05:19:30
@grqp:matrix.orgGrqPI forgot about unsafeGetAttrPos. I thought nix repl :e would get me there but not so much.05:24:55
@winter:catgirl.cloudWinter :doc miiiight 05:47:08
@winter:catgirl.cloudWinterbut i forget if upstream nix has this05:47:17
@qyriad:katesiria.orgQyriad Neither makeWrapper nor makeShellWrapper have comments on them, so :doc doesn't help, bleh 11:13:06
@pyrox:pyrox.devdish [Fox/It/She]well they're not functions, they're packages, which is why they dont come up in :doc iirc16:09:33
@winter:catgirl.cloudWinterfunctions have :doc more than packages… :P19:09:15
@ilosariph2:matrix.orgIlosariph joined the room.19:22:03
9 Dec 2025
@aleksi:pikaviestin.fialeksiI've submitted a draft PR to support minimal-bootstrap on x86_64-linux, based on the previous PR to upgrade mes to 0.27.1. https://github.com/NixOS/nixpkgs/pull/469294 This is the specific delta for x86_64-linux: https://github.com/NixOS/nixpkgs/compare/48c34b0b80801c8009a6b75728588cfee5468cff..9b6c3e609f671609f8b6add5dd572679f6527a5b15:29:09
@iblech:livingutopia.orgIngo Blechschmidt

I'm just a bystander, but: Awesome!!! Thank you so much for this work.

For anyone following along, I believe that this can be tested from the comfort of your couch by:

nix-build -I nixpkgs=https://github.com/Gskartwii/nixpkgs/archive/bootstrap-x86_64-linux.tar.gz "<nixpkgs>" -A make-minimal-bootstrap-sources
nix-build -I nixpkgs=https://github.com/Gskartwii/nixpkgs/archive/bootstrap-x86_64-linux.tar.gz "<nixpkgs>" -A minimal-bootstrap.test

I am doing this now (and expect no problems). There was one quickly fixed issue in the beginning, I got a hash mismatch for nyacc, probably because I had already tested an earlier version? (I resolved this by appending a do-nothing question mark to the nyacc URL, prompting a redownload, for which the hash successfully validated. But I don't fully understand the root cause of this issue. On a machine with a fresh cache, this issue did not arise.)

How hard would it be to drop pkgs/stdenv/linux/bootstrap-files (for x86_64)?

22:00:43
@pyrox:pyrox.devdish [Fox/It/She]since I don't have an understanding of how the current bootstrap-files mechanism works, difficult.22:33:02
@pyrox:pyrox.devdish [Fox/It/She]but with this it can be done soon22:33:07
@pyrox:pyrox.devdish [Fox/It/She]though this also requires more tools to be built first22:33:18
@pyrox:pyrox.devdish [Fox/It/She]see #45900222:33:38
@pyrox:pyrox.devdish [Fox/It/She] looked through the additional commits, nice work! 22:40:16
@rosscomputerguy:matrix.orgTristan RossI will look at aarch64-linux minimal-bootstrap lol22:42:36
@pyrox:pyrox.devdish [Fox/It/She]👀22:44:34
10 Dec 2025
@iblech:livingutopia.orgIngo Blechschmidt *

I'm just a bystander, but: Awesome!!! Thank you so much for this work.

For anyone following along, I believe that this can be tested from the comfort of your couch by:

nix-build -I nixpkgs=https://github.com/Gskartwii/nixpkgs/archive/bootstrap-x86_64-linux.tar.gz "<nixpkgs>" -A make-minimal-bootstrap-sources
nix-build -I nixpkgs=https://github.com/Gskartwii/nixpkgs/archive/bootstrap-x86_64-linux.tar.gz "<nixpkgs>" -A minimal-bootstrap.test

I am doing this now (and expect no problems). There was one quickly fixed issue in the beginning, I got a hash mismatch for nyacc, probably because I had already tested an earlier version? (I resolved this by appending a do-nothing question mark to the nyacc URL, prompting a redownload, for which the hash successfully validated. But I don't fully understand the root cause of this issue. On a machine with a fresh cache, this issue did not arise.)

How hard would it be to drop pkgs/stdenv/linux/bootstrap-files (for x86_64)?

Edit. The test successfully concluded as expected.

00:03:42
@aleksi:pikaviestin.fialeksi

Thank you, I appreciate the testing. Credits to to dish and GNU Mes folks among others. I do want to check if I can reproduce the hash mismatch locally. I've seen issues like that, where they only appear after a gc cycle.

06:48:36
@aleksi:pikaviestin.fialeksi

Very exciting :D

06:49:08
@sarunint:matrix.sarunint.comSarun Intaralawan joined the room.13:34:47

There are no newer messages yet.


Back to Room ListRoom Version: 9