Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 17 Aug 2023 20:56:37 +0000
From:      bugzilla-noreply@freebsd.org
To:        python@FreeBSD.org
Subject:   [Bug 273122] lang/python311: backport netlink support
Message-ID:  <bug-273122-21822-yhJkAt8Qzh@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

Matthias Andree <mandree@FreeBSD.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |mandree@FreeBSD.org

--- Comment #12 from Matthias Andree <mandree@FreeBSD.org> ---
We are free to integrate third-party packages, including Python, into our
system, and integrate well, as we see fit -- license permitting.

The entire discussion, both upstream and here, is taking WAY more time and
space than the actual solution. The gist of the integration improvement is
telling Python's configure script to look for netlink/netlink.h in addition=
 to
linux/netlink.h.

If we find configure patches unwieldy, we can patch the source file and
regenerate configure at build time, unless that would create circular
dependencies in the tree.

If we can't use patches for whatever reason, then we can use REINPLACE_CMD =
to
keep the change really minimal, and it's possibly even good enough.

Are there particular technical or quality concerns?

Else if we deem it necessary to limit the patch to builds on FreeBSD 13.(>=
=3D2)
and >=3D 14.0 because the older releases' netlink support were present but
unsuitable, then please clearly mention so.


So can we please stop the useless discussion of where and how to host this =
and
cease bitching about Python's feature freeze policies, and just put either =
that
patch and the REINPLACE_CMD, with the reference to the upstream 3.12
discussion, and add that stuff into our ports/ repository, test things, and
then push (with bumped PORTREVISION).=20

Feel free to convince the Python maintainers that this is a fix of the
configure bug, but do it in parallel and don't wait for the result we may n=
ever
have.

Thank you.

--=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-yhJkAt8Qzh>