3 ms·

shrug sure.

• taeric 5y ago
  Fair. And I fully cede that insisting on other words here is silly. I had meant my post mostly as a question, but forgot the right punctuation.
• sangnoir 5y ago
  "Fork" kind of implies the codebases have diverged and there is active maintenance of the fork; "Patchset" is the more common term for changes distros apply to an upstream project before they package it - and this is something most distros do when they fail to upstream the changes (usually due to some benign differences with upstream). However, sometimes the differences can be sharp, such as when Mozilla disagreed with Debian's patchset[1] (it was around trademarks, UI assets and branding). IIRC Mozilla asked Debian to stop calling its package Firefox, so Debian - perhaps vindictively - chose "IceWeasel" instead. Good times. 1. https://en.wikipedia.org/wiki/Mozilla_software_rebranded_by_Debian https://en.wikipedia.org/wiki/Mozilla_software_rebranded_by_...
  • kyrofa 5y ago
    A fork is a copy that is maintained separately, and that is exactly what is happening here. You're actually quite right that, if all they were maintaining was a Debian package, they could theoretically maintain a source package with a vanilla orig tarball and keep their changes to patches, but that's not what they're doing here: > The support offering will include Blender LTS releases across Linux distributions, Microsoft Windows, and macOS. They're not using quilt to do this. They're using git. At least, that's how I did it when I did it for Canonical.