Re: The State of Rust in MacPorts Today

On Tue, Dec 13, 2022 at 7:50 AM Christopher Jones wrote: > … move to a model where the version is part of the port name, e.g. the > current one would be called something like rust-1.61. ... > 1. Add a shim port ‘rust’ which simply installs sym-links etc. to the > ‘current best version’ that

Re: The State of Rust in MacPorts Today

nope. Rust version 1.x can be build by 1.x or 1.(x-1) :( See: https://guix.gnu.org/blog/2018/bootstrapping-rust/ -- wbr, Kirill > On 13. Dec 2022, at 22:27, Dave Allured - NOAA Affiliate via macports-dev > wrote: > > Is it possible to

Re: The State of Rust in MacPorts Today

Is it possible to build recent versions directly with rust-1.54? For example, mrustc -> rust 1.54 -> rust 1.65? On Tue, Dec 13, 2022 at 12:07 PM Kirill A. Korinsky via macports-dev < macports-dev@lists.macports.org> wrote: > David, > > the idea is creating a dependency chain: > > Port rust

Re: The State of Rust in MacPorts Today

FFMpeg can certainly be compiled without Rust, including the latest (upstream) version. Perhaps a component that is pulling in Rust should rather be made an optional variant for all systems – it is hardly justified to have it as the default, IMHO. On Wed, Dec 14, 2022 at 12:32 AM grey wrote: >

Re: The State of Rust in MacPorts Today

This is a tangential, so please forgive me if this seems as if it is the wrong time to bring this up, but I seem to have some Rustaceans who may know more about this than I. I was recently seeing if there might be a way to improve upon the FFmpeg ports (there are currently three: ffmpeg,

Re: The State of Rust in MacPorts Today

Chris, > Clearly some thought has to be given to how to ensure the dependency tree > does not get too long. We don’t want, when a new OS comes out for it to have > to build tens of rust versions, just to ultimately bootstrap the last one. > That might just be keeping the first bootstrap port,

Re: The State of Rust in MacPorts Today

Hi, > On 13 Dec 2022, at 5:07 pm, Kirill A. Korinsky via macports-dev > wrote: > > David, > > the idea is creating a dependency chain: > > Port rust (version 1.66) depends on rust-1.65 to be build; > Port rust-1.65 depends on rust-1.64 to be build; > Port rust-1.64 depends on rust-1.63 to

Re: The State of Rust in MacPorts Today

David, the idea is creating a dependency chain: Port rust (version 1.66) depends on rust-1.65 to be build; Port rust-1.65 depends on rust-1.64 to be build; Port rust-1.64 depends on rust-1.63 to be build; ... Port rust-1.56 depends on rust-1.55 to be build; Port rust-1.55 depends on rust-1.54 to

Re: The State of Rust in MacPorts Today

The work on mrustc is novel but I don't think it solves the issues we have here. On modern systems MacPorts uses bootstrap compilers provided by Rust upstream. MCL's bootstrap compilers are for older systems. To update rust, my understanding is that you have to do the usual work of rebasing

Re: The State of Rust in MacPorts Today

Kirill, when you gonna deal with i386, consider also PPC. Sure enough, it is not a priority, but it may be fixable, given that mrustc itself builds on ppc32. To be clear, I do not expect any dedicated fixes, just making sure x86 is not hard-coded and 32-bit platforms are supported. Then all PPC

Re: Dev guide updated for github/easy instructions?

When I used that page, step 1e was confusing to a git newbie. -- Steve From: macports-dev on behalf of Nils Breunese Date: Monday, December 12, 2022 at 4:56 PM To: MacPorts Development Subject: Re: Dev guide updated for github/easy instructions? Does

Re: The State of Rust in MacPorts Today

Folks, From the third hand we may build our own bootstrap chain of rust from scratch. Or almost. We have a https://ports.macports.org/port/mrustc/details/ which is able to bootstrap 1.54 rust on x86_64 and arm64. Unfortunately support of i386

Re: The State of Rust in MacPorts Today

Hi, In my opinion, hosting and maintaining these ‘bootstrap’ compilers outside the macports infrastructure was a poor choice, for all the reasons you mention below. I thought this at the time it was done, and even more so now. Personally, I would suggest you think about a change to how the

Re: The State of Rust in MacPorts Today

The thing blocking me, and probably anyone else in the project, from bumping the version, and also from testing/updating other ports, is that I don't have access to build machines with older MacOS X releases. It is probably better to frame this discussion in that way: how can we get a build

The State of Rust in MacPorts Today

Hello all, Right now, Rust in MacPorts is severely out of date. It's about 5 versions behind the current release, which at the moment is at 1.65.0. In comparison, MacPorts Rust is currently at 1.61.0. As a core language underlying a lot of other ports, many of these ports cannot be updated to