Date: Tue, 26 Sep 2023 13:40:04 +0000 From: bugzilla-noreply@freebsd.org To: python@FreeBSD.org Subject: [Bug 273122] lang/python311: backport netlink support Message-ID: <bug-273122-21822-NlP8noGtGO@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-273122-21822@https.bugs.freebsd.org/bugzilla/> References: <bug-273122-21822@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D273122 --- Comment #14 from Charlie Li <vishwin@freebsd.org> --- (autotools) configure patches, against the generated-by-autoconf output, are unwieldy by default; this is no exception. The existing local as in ${PATCH= DIR} patch against configure deals with LTO support, which is unlikely to be mer= ged upstream. Nothing to do with netlink support, which has been merged upstream (even though trunk only). Mixing these two concerns in the same local patch= (es) is a maintenance issue that is easily and should be avoided. Amongst other things, consider that, when a future ports person starts working on lang/python313 by repocopying lang/python312 (which will contain the netlink patch), they can immediately remove the ${PATCH_SITES}/${PATCHFILES} lines rather than figure out what went wrong in ${PATCHDIR} in this area. So no, these discussions are necessary, and expect more of them. If there i= s an unwillingness by the original submitter to do what is necessary, I will do = it myself. --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-273122-21822-NlP8noGtGO>