[Bug 273122] lang/python311: backport netlink support
- In reply to: bugzilla-noreply_a_freebsd.org: "[Bug 273122] lang/python311: backport netlink support"
- Go to: [ bottom of page ] [ top of archives ] [ this month ]
Date: Thu, 17 Aug 2023 00:51:58 UTC
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=273122 --- Comment #9 from Charlie Li <vishwin@freebsd.org> --- We've done this with at least earlier iterations of graphics/mesa{,-devel}, and it all works as intended. It's not just about keeping track, but ensuring that everything is applied in the correct order, and that any local patches are based on the original source plus items they accepted whether in the same branch or trunk. Combining upstream patches with our local patches, sometimes resulting in the same local patch file (names) in ${PATCHDIR}, is just a bad idea. (In reply to Joseph Mingrone from comment #7) This is necessary when considering maintenance, semantics and mechanics. (In reply to Daniel Engberg from comment #8) Python upstream brought this upon themselves. In many other software projects, this would be a bug fix, not a new feature. If anyone there cares enough, they can read the last couple comments in the original issue, maybe see this exchange, and understand/remind themselves that asking distributions to carry arbitrary stuff they accepted as local patches comes at a cost. Don't forget that some other upstreams don't bother to backport anything, not even bug or build fixes, forcing downstreams like us to carry stuff. The single patch file doesn't address the ordering. ${PATCHDIR} really isn't meant for something like this. -- You are receiving this mail because: You are the assignee for the bug.