Trick Portage into having installed Rust

[EliasJonsson]

I own a Raspberry Pi 4, 4GB RAM. 4 GB RAM isn't enough in order to compile the Rust package. Although, It is possible to just run

Code: Select all

curl --proto '=https' --tlsv1.2 -sSf https://sh.rustup.rs | sh

and have Rust installed.

Is it possible to somehow tell Portage that the rust package already is installed so that other things that depends on Rust package can be installed?

[irets]

If for some reason you cannot compile it, Rust also exists in binary form.
https://packages.gentoo.org/packages/dev-lang/rust-bin

[mike155]

Is it possible to somehow tell Portage that the rust package already is installed so that other things that depends on Rust package can be installed?

Code: Select all

/etc/portage/profile/package.provided

[mike155]

Code: Select all

curl --proto '=https' --tlsv1.2 -sSf https://sh.rustup.rs | sh

Oops... Never download anything from the internet and execute it without looking at it... Especially not as root... That's the road to hell!

[Hu]

Code: Select all

curl --proto '=https' --tlsv1.2 -sSf https://sh.rustup.rs | sh

Oops... Never download anything from the internet and execute it without looking at it... Especially not as root... That's the road to hell!

Indeed. From a purely academic standpoint, I wonder what OP installed with that command. Since he didn't save the text of what was fed to sh, nor run sh with -x, we'll never really know what commands were executed. At best, we can hope that he got a complete copy of whatever that host is serving today, and that such copy is safe. This is why curlpipesh is always the wrong solution, no matter what problem is under discussion. If it had been served with an emulation of something like subresource integrity, there would be a a bit of a trail. For example (not working, since the server doesn't support this, but in principle it could):

Code: Select all

(expected_sha256sum=e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855 ; set -euo pipefail; local_install_script="$(mktemp --tmpdir curlpipesh-rustup.sh.XXXXXX)"; curl --proto '=https' --tlsv1.2 --silent --show-error --fail https://sh.rustup.rs/curlpipesh/$expected_sha256sum/install.sh -o "$local_install_script"; printf '%s  /dev/fd/3\n' "$expected_sha256sum" | sha256sum --quiet --strict --check - 3< "$local_install_script"; /bin/sh < "$local_install_script"; rm "$local_install_script")

Explained:

• Record the expected checksum once, right at the top, for easy maintenance.
• Enable some safety options.
• Create a temporary file in which to save the downloaded script. This will be needed since we want to make two passes over it, and control flow requirements preclude using tee.
• Download the script to the temporary file, using the same curl invocation that Rust recommends for their curlpipesh (but with some parameters spelled out for easier reading). Notably, this fragment uses a (currently fictitious, but reasonable) path on the server to tell the server what script it expects, so that the server can provide an appropriate document. This could be omitted if you want the fragment to just fail outright whenever the server document changes.
• Run sha256sum to check the downloaded file against what it should be. Due to --check on sha256sum and set -e on the shell, a failed verification at this step will abort, and none of the later steps in my example will run.
• Run the script. Notably, this preserve's upstream's questionable decision not to set -euo pipefail.
• Delete the temporary file.

[Zucca]

At least the command has --tlsv1.2, but doing curlpipesh is bad.
As mentioned above, use rust-bin then instead if you cannot compile rust.

[EliasJonsson]

At least the command has --tlsv1.2, but doing curlpipesh is bad.
As mentioned above, use rust-bin then instead if you cannot compile rust.

Will do. Thanks for pointing that out!