The State of Rust in MacPorts Today

[Herby G]

Thank you for the update, Marcus. I apologize for any harsh tone of mine in
this conversation, and I hope that things are getting better on your end.

I tested this PR on macOS 12.6.2 arm64 and it built successfully:

$ rustc --version; cargo --version
> rustc 1.66.0 (69f9c33d7 2022-12-12) (built from a source tarball)
> cargo 1.66.0
>

> If we do decide to continue our own Rust binaries, I agree that it would
be highly advisable to find a more suitable location.

Can we restart the discussion about placing this in an official repo in the
MacPorts Github account? Would also be nice to use Github actions to
automatically build as much as is possible in an automated way on update.


On Tue, Dec 20, 2022 at 10:51 PM <mcalhoun at macports.org> wrote:

> I am sorry I have not been a better maintainer for the Rust port.
> Life has been a little hectic.
>
> As has been discussed in this thread, there is definitely room for
> improvements in the Rust setup.
> Until a final consensus is reached, I opened a pull request to at least
> get Rust to its latest version using the previous infrastructure.
> (https://github.com/macports/macports-ports/pull/17028).
>
> I am not sure the GCC and Clang ports are necessary a good model.
> In those cases, there is a system compiler could build a compiler, which
> could be used to build a compiler, etc.
> That is not the case for Rust.
>
> To build Rust, MacPorts has to download Rust binaries.
> If the system is new enough, upstream provides them.
> If we want to support older system, we have to build and distribute our
> own.
> Of course, mrustc and/or Rust-GCC may change that.
>
> If we do decide to continue our own Rust binaries, I agree that it would
> be highly advisable to find a more suitable location.
>
> -Marcus
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.macports.org/pipermail/macports-dev/attachments/20221220/5ab7b9e8/attachment.htm>