(I tagged this with “c++” but not “rust” because it sounds like this is mainly aimed at c++ rather than rust, and which language the tool is built in is not particularly relevant to the article.)
Why wouldn’t it be useful for Rust? (Honest question - I have no experience with reproducible Rust builds; don’t you end up with native binaries having relative paths same as with C++?)
Ah, this makes me want to revisit the blog post draft I have for the debug package implementation I wrote for makepkg, it uses debugedit and explains the concepts a bit.
(I tagged this with “c++” but not “rust” because it sounds like this is mainly aimed at c++ rather than rust, and which language the tool is built in is not particularly relevant to the article.)
Why wouldn’t it be useful for Rust? (Honest question - I have no experience with reproducible Rust builds; don’t you end up with native binaries having relative paths same as with C++?)
I’m just responding to the fact that in the article you happen to mention using it for c++ a lot and for rust only in passing.
The choice of tags is slightly arbitrary. 😞
Ah, this makes me want to revisit the blog post draft I have for the debug package implementation I wrote for
makepkg, it usesdebugeditand explains the concepts a bit.As long as
debugeditdoesn’t dump core on you like it did for me…I don’t know what package would produce “a 3GB shared object” so I’m not sure if this is a realistic issue in this case.
However it is slow.