Date: Fri, 28 Jan 2022 07:31:29 +0000 From: bugzilla-noreply@freebsd.org To: python@FreeBSD.org Subject: [Bug 257041] [NEW PORT]: devel/py-lief: Parse, modify and abstract ELF, PE and MachO formats Message-ID: <bug-257041-21822-SnWAClWW4v@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-257041-21822@https.bugs.freebsd.org/bugzilla/> References: <bug-257041-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=3D257041 Kubilay Kocak <koobs@FreeBSD.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|maintainer-feedback+ |maintainer-feedback?(ports@ | |nicandneal.net) --- Comment #13 from Kubilay Kocak <koobs@FreeBSD.org> --- The bundled dependencies (see third-party directory in distfile) are somewh= at problematic.=20 We are expected to unbundle all dependencies and use system (ports/package) versions of them. In the short term, we may be able to get away with leaving bundled, any software that has no port/package for it yet, with a long term view to porting them. It would be good to go through the list (I can see at least mbedtls and pyb= ind are in ports) and determine the best method to 'unbundle' them. Nothing sto= od out with a very quick cursory review of upstream Installation docs, so we m= ay need to use cmake vars or modify the cmake invocations. *Hopefully* there's a simple way given this python package uses cmake, which itself is unorthodox to say the least. I'm running the build now and will run through QA again with additional feedback/changes to come. If someone can clarify this 'how do we unbundle these third-party dependenc= ies' question, it would go a long way to progressing and landing this. --=20 You are receiving this mail because: You are on the CC list for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-257041-21822-SnWAClWW4v>