128
Rust Coreutils Continues Working Toward 100% GNU Compatibility, Proving Trolls Wrong (www.phoronix.com)
submitted 6 months ago by to c/linux@programming.dev
142 comments fedilink hide all child comments
 

Sylvestre Ledru who serves as the lead developer of the uutils project for the Rust Coreutils implementation presented at FOSDEM 2026 this weekend on this initiative. Ledru has spoken at FOSDEM in prior years on Rust Coreutils and this year's talk focused primarily on Ubuntu 25.10's adoption of it in place of GNU Coreutils.

Ledru's presentation covered the progress made on Rust Coreutils in recent times and Ubuntu 25.10's uptake of Rust Coreutils and continuing that for Ubuntu 26.04 LTS. While some bugs have been found as a result of it, they have been fixed rather quickly. Ledru's presentation also points out some of the popular trolling around Rust Coreutils and ultimately how many of those commenters have been proven wrong

you are viewing a single comment's thread
view the rest of the comments
[–] -1 points 6 months ago (1 child)

Businesses can already create their own forks of GPL-licensed software and not contribute their changes to the upstream project; in fact, they do not even have to share their code with anyone at all if they use it internally do not distribute binaries. However, they are incentivized to share their changes, even if they do not have to, because if they do not then merging upstream changes will become increasingly difficult.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •
  • [–] 1 point 6 months ago (2 children)

    Businesses can already create their own forks of GPL-licensed software and not contribute their changes to the upstream project

    No they can't, at least not legally. Part of using GPL software is that you need to include the GPL with any changes you make.

    It's the entire point of the license and the concept behind copyleft.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 4 child comments
    •
  • [–] 2 points 6 months ago (1 child)

    Reread that quote, and you will see that I was saying that just because they are required to distribute the source code with binaries--which they are only required to do if they distribute binaries--does not mean that they have to take any steps to contribute the changes they've made to the upstream project.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •
  • [–] 1 point 6 months ago (1 child)

    does not mean that they have to take any steps to contribute the changes they’ve made to the upstream project.

    You're partially right. They don't have to "contribute back" by submitting pull requests or something similar.

    They do have to contribute back by making their changes publicly available. Whether upstream uses those changes is up to them.

    I'm going to ignore you now since all of your replies have shown me you're a moron. Peace.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •
  • [–] 1 point 6 months ago

    You only need to provide source code to your users. There’s no need to provide a public git repository to the world.

    You can fork GPL software and sell it. If one of your customers asks, you can send them a copy of the source code on a DVD. This is all the GPL requires.

  • permalink
  • fedilink
  • source
  • parent