Same general problem as D39205. In https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=275922 you can see it in distinfo too where crates that should go into DISTDIR/rust/crates now go into DISTDIR/jetbrains/rust/crates:

TIMESTAMP = 1702039441
SHA256 (jetbrains/rust/crates/autocfg-1.1.0.crate) = d468802bab17cbc0cc575e9b053f41e72aa36bfa6b7f55e3529ffa43161b97fa
SIZE (jetbrains/rust/crates/autocfg-1.1.0.crate) = 13272
[...]

fwiw, this is still approved.

It's using extract because extract is the bare minimum dependency where generate-lockfile could possibly work. Sometimes you don't want the patches applied. If we change it to patch then we have to manually move the patches out the way first in that case. With extract people can just run make patch cargo-crates when they need the patches applied first.

Ideally, crates should download to rust/crates regardless of ${DIST_SUBDIR} but bsd.port.mk logic prevents it I think.

Isn't there LTO_UNSAFE to opt out of WITH_LTO?

In D34823#790565, @mikael wrote:

In D34823#790447, @mikael wrote:

The problem with devel/racer is as follows:

• racer 2.1.48 doesn't build with rust 1.60.0
• racer 2.x requires rustc-dev from rust-nightly
• rustc-dev is not "fabricated" on lang/rust-nightly because we use x.py build instead of x.py dist

Probably time to resurrect https://reviews.freebsd.org/D28520

Racer 2.2.0 builds fine with rust 1.60.0 and rustc-dev (no need for the nightly version)