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

But why are the patches kept separate at all. Especially if it's a copyleft licensed code they're patching. Many of those require release of the code. And the spirit of that was to make companies who profit off of the code release anything they add as they add it. Otherwise, they're welcome to instead of taking open source code and patching it, creating closed source code from scratch without using any of the code from the open source version and selling that. It's very simple. The license says, you want this code, you're welcome to it, but release any fixes or improvements you make do we all benefit, not just developers, but users all benefit. If they keep it locked up, even if they release it as a patch that's not accessible to the large majority of users, then it's violating the spirit if in some cases not the letter of the license.

  • source
  • parent
  • hideshow 1 child comment
  • [–] 1 point 11 months ago

    ...that's not what they're doing though?

    Those patches get either pulled from upstream or built in-house and shared to upstream. Just like in Debian, and just like in the regular Ubuntu releases, the package is based on some upstream version and then the deb packaging applies the patch sets as listed in the diff tarball.

    Here's what the latest kernel for Ubuntu 26.04 look like: https://launchpad.net/ubuntu/+source/linux/6.17.0-6.6

    Those same tarballs are available for any Ubuntu package by running apt source <pkg> as long as you've configured the matching deb-src repositories.

  • source
  • parent