Re: the problem of rust :-(

[pin <voidpin%protonmail.com@localhost>]

On Monday, June 24th, 2024 at 2:42 PM, Greg Troxel <gdt%lexort.com@localhost> wrote:

> > On Mon, 24 Jun 2024 09:11:09 +0000
> > pin voidpin%protonmail.com@localhost wrote:
> > 
> > > As we approach the Q2-freeze, the following can no longer be updated:
> > > - devel/cargo-c: pkgsrc version 0.9.32; current upstream release, 0.10.0 requires Rust-1.77.2
> > > - devel/cargo-modules: pkgsrc version 0.15.5; current upstream release, 0.16.0 requires Rust-1.78.0
> > > - editors/tp-note: pkgsrc version 1.24.2; current upstream release, 1.24.4 requires Rust 1.77.2
> > > 
> > > This is better than expected at this point.
> 
> 
> That is a pretty short list of what's being held back, and it doesn't
> seem like a major user problem, compared to entire computers breaking.

Hence, "better than expected" :)
I'd expect this list to grow fast, though.


> tp-note would seem to have some software engineering hygiene problems.
> It is not ok to change prerequisites in a micro release. Maybe I am
> misreading (or maybe this is just evidence of rust culture :-( ).

Well, actually the 1.24.4 release was made to push MSRV down to 1.77.2
The MSRV for 1.24.3 was even higher.
Maybe you are right and it's "bad software engineering" but, MSRV bump was caused by dependencies and not by direct changes to the code.