-
m-relay_<n7483:monero.social> How do i enable commands in the log section of GUI wallet? ‘Type a command’ is greyed out for me
-
restlessroninI have created a new literate (org-mode to ansible) setup for a full monero node. it's designed to run on omarchy. is it appropriate to announce the project/repo here?
-
DataHoarderrestlessronin: #monero-community-dev or #monero-community
-
restlessroninDataHoarder: Thank you.
-
m-relay_<kayabanerve:matrix.org> tobtoht: I saw you added a thumbsup to my issue calling for bootstrapping Serai. While not immediately directly related, I achieved cross-platform reproduducible builds of Rust _without_ an OCI solution or similar: github.com/serai-dex/serai/blob/nex…adot-sdk/substrate/runtime/build.rs
-
m-relay_<kayabanerve:matrix.org> I understand the general stance towards reproducibility is to shove it in a container, or even better, a bootstrappable container. The above may still be very interesting when discussing the FCMP++ libraries w.r.t. Monero though.
-
m-relay_<kayabanerve:matrix.org> Personally, I'd like to see (in my own work) reproducible builds where one of the reproductions is bootstrapped. This is made easier by the fact I always target WASM in the above build flow, and WASM is always done _within_ the Rust toolchain, but even for non-WASM targets, it should be possible to force usage of Rust's bundled internal toolchain over the host tools for the resulting artifact.
-
m-relay_<kayabanerve:matrix.org> Note that does still use host tools. Some of Rust macros are performed by compiling the macro to a dylib, then loading it into the compiler itself to transform tokens from the lexer. In a reproducible build, the host tools should only be used for that and while that means the macros may have different binaries, they aren't part of the resulting artifact, solely their observable tr<clipped message>
-
m-relay_<kayabanerve:matrix.org> ansformations to the stream of lexed tokens.