WingNews logo WingNews
top | item 47137350

(no title)

bigfishrunning | 5 days ago

further down that thread

https://lists.debian.org/debian-devel/2025/10/msg00288.html

``` Rust is already a hard requirement on all Debian release architectures and ports except for alpha, hppa, m68k, and sh4 (which do not provide sqv). ```

It seems to me that the APT change was just a nail in the coffin of these older architectures, which would have eventually been sunset anyway, due to sqv not being available. If you really want to run some kind of Linux on these very old machines, godspeed, but you can't expect them to be maintained by a project with it's fingers in so many pies forever.

discuss

order

superkuh|5 days ago

Yep. And nothing you've linked or pointed out changes the claim I made: that re: rust, Canonical employees are making the decisions, not Debian.

pjmlp|4 days ago

The thing with open source, and many industry standards like ISO and ECMA, is that who shows up gets to call the shots.

So when it isn't going into the right direction that we care, maybe more people with other mindset should join.

It is like complaining about who wins elections without bothering to cast a valid vote.

bayindirh|5 days ago

Well, it's not always true.

Look at how the proposal for making netplan the default network manager in Debian went. Not good, from Canonical's perspective.

Making /tmp behave the way systemd guys want also went not according to plan. The behavior is modified somewhat because of the discussion.

Rust's influence doesn't come from Canonical per se, but from its promise to eradicate memory related bugs. The initial hype was off the charts, but it's coming down, and the shortcomings are becoming obvious.

Canonical is trying to affect Debian, that's true, but it's not always a given.