[MacPorts] #68364: rust: Update to 1.74.1
MacPorts
noreply at macports.org
Fri Dec 29 17:20:18 UTC 2023
#68364: rust: Update to 1.74.1
--------------------------+---------------------------------
Reporter: Schamschula | Owner: MarcusCalhoun-Lopez
Type: update | Status: assigned
Priority: Normal | Milestone:
Component: ports | Version: 2.8.1
Resolution: | Keywords:
Port: rust |
--------------------------+---------------------------------
Comment (by halostatue):
Upstream is now 1.75.0, however I am failing to build either {{{rust}}} or
{{{rust-bootstrap}}}. I’m mostly focusing on {{{rust-bootstrap}}} right
now because it appears to be necessary to have the previous level working.
I’m not *entirely* sure what's going on in `rust-bootstrap`, but the most
recent build failure (setting `version_current` to `1.72.1` and
`version_m1` to `1.71.1`) is
{{{
:info:build Unexpected rustc version: 1.69.0, we should use 1.70.x/1.71.1
to build source with 1.71.1
}}}
It appears that this (1.69.0) is from `rust.add_bootstrap_components` (in
`_resources/port1.0/group/rust-1.0.tcl:146`) and that points to
`https://github.com/MarcusCalhoun-
Lopez/rust/releases/download/${version_current}:macports_vendor`, which I
think has been mentioned in other tickets or the mailing lists as a
slightly odd dependency.
There's some dependencies that I don’t understand which, if I didn’t want
to shift mostly to MacPorts for my package management, I would be
seriously thinking about switching *back* to `rustup` and `cargo install`
and/or `cargo binstall` for any rust-based dependencies.
It would be good to get some guidance from the port and port group owner
on the right way to upgrade these ports, because I’m willing to spend some
time helping out with this, but my Tcl-fu is not strong and there appear
to be a number of undocumented procedural steps that are required (what's
bootstrap-transition vs bootstrap, etc.).
This is made more difficult by the fact that I *know* that on macOS, the
only supported architectures are x86_64 and arm64 and OS versions 10.12 or
higher. I don't think that Rust has ever had `powerpc-apple-darwin`
targets and `i686-apple-darwin` is a Tier 3 target (might work, might not,
poorly supported), so some of the architecture choices seem questionable
in the `rust`/`rust-bootstrap` portfiles.
I’m sure that there's good reasons behind the choices, but from my
perspective, I can't reason them out.
--
Ticket URL: <https://trac.macports.org/ticket/68364#comment:14>
MacPorts <https://www.macports.org/>
Ports system for macOS
More information about the macports-tickets
mailing list