| 4 Aug 2023 |
 gdamjan | sure - take care :D | 13:45:59 |
 Lily Foster | (I mean I work for a state government in the US and it's a friday -- I can be on mobile, it's not like I'm getting much done anyway 😅) | 13:46:39 |
| gdamjan | --precise | 13:46:41 |
| gdamjan | is there a way to tell it not to shorten strings like this bin/node: ….46.0-dev/include", "/nix/store/l0vnx3ik63qrlj086gq06fjmalsi5dpy-openssl-3.0.9-dev/include", "/n… ? | 13:48:17 |
| Lily Foster | In reply to @gdamjan:spodeli.org
is there a way to tell it not to shorten strings like this bin/node: ….46.0-dev/include", "/nix/store/l0vnx3ik63qrlj086gq06fjmalsi5dpy-openssl-3.0.9-dev/include", "/n… ? Hmmmmm not sure. Also why would the include paths be embedded in the binary???? | 13:49:09 |
| Lily Foster | Unless it's wrapped and that's a wrapper. I forget if it's wrapped | 13:49:25 |
| gdamjan | /nix/store/5vm8fh4q21xlk7i1y6rqykqar296dglr-nodejs-slim-18.16.1/bin/node is 45M … seems like the real deal :D | 13:50:28 |
| gdamjan | ok thanks for why-depends, let me make some experiments | 13:51:16 |
| Lily Foster | In reply to @gdamjan:spodeli.org
/nix/store/5vm8fh4q21xlk7i1y6rqykqar296dglr-nodejs-slim-18.16.1/bin/node is 45M … seems like the real deal :D Damn, I wonder if it just doesn't have LTO or anything on it. Highly templated C++ stuff can explode in size for sure, especially without that | 13:52:24 |
| Lily Foster | But 45 MB is a lot... | 13:52:32 |
| gdamjan | /usr/bin/node is 39M on Arch … I guess a static library or two difference?! | 13:53:35 |
| Lily Foster | Maybe | 13:55:39 |
| gdamjan | this is gonna compile for a while … | 13:56:33 |
| Lily Foster | Yep, good luck 🫠| 13:57:14 |
| gdamjan | time enough to clean my bike :P | 13:58:06 |
| Lily Foster | Yeah, probably. Have fun with that | 13:58:50 |
| Lily Foster | I wish marsam was on Matrix since they usually do most of the nodejs derivation maintenance and can probably speak a lot more intelligently on it. I just do the ecosystem tooling mostly | 13:59:47 |
| gdamjan | discourse then? | 14:01:15 |
| Lily Foster | In reply to @gdamjan:spodeli.org
discourse then? Yeah they are on discourse and can probably be asked there. Ping me on the post too if you make one so it automatically subscribes me to notifs | 14:02:08 |
| gdamjan | some more input … | 19:56:29 |
| gdamjan | the bin/node: ….46.0-dev/include", "/nix/store/l0vnx3ik63qrlj086gq06fjmalsi5dpy-openssl-3.0.9-dev/include", "/n… that why-depends reports seems to referring to:
/nix/store/3sj7ka634hlvdmywr9nndffvk9hiw247-libuv-1.46.0-dev | 19:57:17 |
| gdamjan | also running strings on ./result/bin/node there's this:
{ "target_defaults": {"cflags": [], "default_configuration": "Release", "defines": ["NODE_OPENSSL_CONF_NAME=nodejs_conf", "ICU_NO_USER_DATA_OVERRIDE"], "include_dirs": ["/nix/store/0rnx7rc87hwkbrhsys7mgwq4jw6pz7ma-zlib-1.2.13-dev/include", "/nix/store/3sj7ka634hlvdmywr9nndffvk9hiw247-libuv-1.46.0-dev/include", "/nix/store/l0vnx3ik63qrlj086gq06fjmalsi5dpy-openssl-3.0.9-dev/include", "/nix/store/db79xky20dvsvs5546ffpv5db70yjlxq-icu4c-73.2-dev/include"], "libraries": ["-L/nix/store/5p62fc7h9ij36fqsxlbq73mbwdhnmbkv-zlib-1.2.13/lib", "-lz", "-L/nix/store/c70parvipldqrfip3cmdq6xdxrpk2scd-libuv-1.46.0/lib", "-luv", "-L/nix/store/xal21vd4d9nfwjkcvw0fyq6ivsbxg1pz-openssl-3.0.9/lib", "-lcrypto", "-lssl", "-L/nix/store/6i4vwgsiqp8jd8pb8cgf99sx8081rmsj-icu4c-73.2/lib", "-licui18n", "-licuuc", "-licudata"]},
| 19:57:57 |
| gdamjan | I don't think that's something easy to fix :/ | 20:00:53 |
| Lily Foster | Of course they embed that in the binary... | 20:52:36 |
| Lily Foster | I mean if string never is actually needed if you can't build against slim anyway or something, you could use nuke-references (or whatever it is called) on it for those dev inputs... | 20:53:35 |
| Lily Foster | (Apologies that I only mostly have questionable ideas) | 20:54:00 |
| gdamjan | I can't even say if the idea is questionable :) | 21:39:52 |
| 5 Aug 2023 |
| gdamjan | is there documentation on nuke-references? | 16:39:48 |
| Lily Foster | I hope there is in the nixpkgs manual. It might be nuke-references-to. I may be misremembering the name | 16:40:17 |
| Lily Foster | In reply to @gdamjan:spodeli.org
is there documentation on nuke-references? Looks like it's nukeReferences is the derivation and it's nuke-refs [-e ref-to-keep]* [files-to-remove-all-non-kept-references-from] | 16:46:33 |
