Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 11 Apr 2024 20:45:12 +0000
From:      bugzilla-noreply@freebsd.org
To:        ports-bugs@FreeBSD.org
Subject:   [Bug 278280] [NEW PORT] dns/py-libknot: Python bindings for libknot
Message-ID:  <bug-278280-7788-vx4usPDqHQ@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-278280-7788@https.bugs.freebsd.org/bugzilla/>
References:  <bug-278280-7788@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=3D278280

Leo Vandewoestijne <freebsd@dns.company> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
 Attachment #249910|                            |maintainer-approval-
              Flags|                            |

--- Comment #3 from Leo Vandewoestijne <freebsd@dns.company> ---
Created attachment 249910
  --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=3D249910&action=
=3Dedit
the whole picture, adjusting dns/knot3, adding dns/py-libknot

(In reply to Einar Bjarni Halld=C3=B3rsson from comment #1)

NO_ARCH=3D        yes

should be below

USE_PYTHON=3D    autoplist concurrent distutils pep517

distutils i.c.w. pep517 is conflicting.
distutils w/o pep517 works.
pep517 is likely preferred, but fails building, unless you add
devel/py-hatchling as build dependancy.

I was trying to make this a metaport, as that would prevent version conflic=
ts
and double work. But it would make the Makefile of dns/knot3 even more
overcomplicated. So instead I would like to take the approach as in attached
patch.

All mutations now validate perfectly with all the testing tools.

--=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-278280-7788-vx4usPDqHQ>