Bug 276448 - lang/rust-nightly: drop explicit consumers via RUSTC_BOOTSTRAP
Summary: lang/rust-nightly: drop explicit consumers via RUSTC_BOOTSTRAP
Status: New
Alias: None
Product: Ports & Packages
Classification: Unclassified
Component: Individual Port(s) (show other bugs)
Version: Latest
Hardware: Any Any
: --- Affects Only Me
Assignee: Yuri Victorovich
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2024-01-19 03:42 UTC by Jan Beich
Modified: 2024-01-19 03:42 UTC (History)
1 user (show)

See Also:
bugzilla: maintainer-feedback? (rust)
jbeich: maintainer-feedback? (yuri)

Attachments
v1 (apply via "git am") (4.15 KB, patch)
2024-01-19 03:42 UTC, Jan Beich 		no flags Details | Diff
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Jan Beich freebsd_committer freebsd_triage 2024-01-19 03:42:32 UTC 
Created attachment 247763 [details]
v1 (apply via "git am")

The port isn't very well maintained (e.g., may not be updated for months, may lack upstream secfixes), is limited to amd64 (but aarch64 is Tier1 nowadays) and mainly intended to be used via DEFAULT_VERSIONS+=rust=rust-nightly. To enable unstable features one can pass RUSTC_BOOTSTRAP via environ(7) with values like "1" for all crates or limited by "crate1,crate2,...". The latter (limited by crate) only makes sense when some dependencies but not the primary distfile needs unstable features e.g., textproc/ripgrep, net-im/libsignal-node.

Note, misc/amazon-qldb-shell appears to build fine *without* unstable features (tested with rust-1.75.0), so doesn't need RUSTC_BOOTSTRAP=1.