You don't just convert and sleep though. You convert and prune. You slowly rework parts post-conversion to use more sensible approaches/libraries. It's not a one-and-done operation, it's an ongoing thing that they judge the cost of investing in now is less than the long term maintaining C Ubuntu.

Look at the folks in college right now, no one can or will.

Using Rust in no way requires the usage of pushover licenses. While it's true that many devs are using pushover licenses, there are plenty of GPL Rust projects. You are just focusing on the sensationalized ones that get mentioned in news cycles.

• AGPL Rust projects on GitHub
• GPL Rust projects on GitHub
• Unfortunately, Codeberg doesn't support filtering by license, but there are Rust projects on Codeberg, some of which will use copyleft licenses here.
• GNOME's GitLab is also rife with GPL-licensed Rust projects.

If they're translating GPL code to Rust, doesn't that constitute a derived work and require the resulting code to be GPL licenced too?

Wait waddup with clang? Any sources I could read up on?

Which is exactly why you're free to license your code under GPL. If corpos can use, then so can you.

Wow! What an observant smart thought.

Well, except for the fact that code conversion doesn't give you the permission to change licenses or remove copyright. And the small matter of fact that both projects mentioned are Canonical projects, where whatever code that is not directly copyrighted by Canonical, is contributed by someone who signed an agreement with this stipulation:

(b) To the maximum extent permitted by the relevant law, You grant to Us a perpetual, worldwide, non-exclusive, transferable, royalty-free, irrevocable licence under the Copyright covering the Contribution, with the right to sublicense such rights through multiple tiers of sublicensees, to reproduce, modify, display, perform and distribute the Contribution as part of the Material; provided that this license is conditioned upon compliance with Section 2.3.

"Us" being Canonical of course. So they could actually "re-license" the projects right now, without changing a single line of code.

It's always astonishing how condiment in their ignorance people are when it comes to these matters.

You geniuses are getting too predictable with your ignorance.

I literally wrote what's quoted above yesterday replying to someone else.

coreutils ships with Ubunutu 26.04, albeit with a number of caveats.

Package: rust-coreutils 
Version: 0.8.0-0ubuntu3 
Priority: required 
Section: utils 
Origin: Ubuntu 
Maintainer: Ubuntu Developers <ubuntu-devel-discuss@lists.ubuntu.com> 
Original-Maintainer: Debian Rust Maintainers <pkg-rust-maintainers@alioth-lists.debian.net> 
Bugs: https://bugs.launchpad.net/ubuntu/+filebug 
Installed-Size: 16.0 MB 
Depends: libc6 (>= 2.43), libgcc-s1 (>= 4.2), libselinux1 (>= 3.1~) 
Conflicts: coreutils-from-uutils (<< 0.0.0~ubuntu22~) 
Homepage: https://github.com/uutils/coreutils 
Task: minimal 
Download-Size: 4,235 kB 
APT-Manual-Installed: no 
APT-Sources: http://archive.ubuntu.com/ubuntu resolute/main amd64 Packages 
Description: Universal coreutils utils, written in Rust 
 This packages replaces the GNU coreutils package written in C. 
 It should be a drop-in replacement but: 
  Some options have NOT been implemented, 
  Might have important bugs, 
  Might be slower, 
  Output of the binaries might be slightly different. 

 

Because that would require competence.