Date: Wed, 28 Feb 2024 16:26:03 +0000 From: bugzilla-noreply@freebsd.org To: ports-bugs@FreeBSD.org Subject: [Bug 277332] dns/knot-resolver and dns/knot3 are mutually exclusive due to dns/knot3-lib Message-ID: <bug-277332-7788-J0RIy8wy89@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-277332-7788@https.bugs.freebsd.org/bugzilla/> References: <bug-277332-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=3D277332 --- Comment #3 from Michael Grimm <trashcan@ellael.org> --- (In reply to Leo Vandewoestijne from comment #2) > Reason for this is because people who do want knot-resolver=20 > often don't want the entire dns/knot-resolver port (plus all of it's deps= .). If you do mean that people who want dns/knot3 don't want the additional stu= ff from dns/knot-resolver, then yes that makes sense regarding dependencies. I you do mean that people who want dns/knot-resolver do not want the additi= onal stuff from dns/knot3 then thats really marginal. Only one more dependency of liburcu, some 26 additional files, because the rest coms from the metaport dns/knot3-lib >> Possible solutions #2 > > is incorrect, as dns/knot3 does NOT depend on dns/knot3-lib True, but I do have running patches that make dns/knot3 like dns/knot-resol= ver dependent on dns/knot3-lib. Now, all library files come from one port, only= and pkg doesn't complain any longer about duplicate files. It is working in my environment for two days now, but I do not have knot-resolver running yet (still on unbound). I do need some more fiddeling and modifications, because 'poudriere testport dns/knot3' still complains about e.g. 'Error: Orphaned: lib/libzscanner.so' That is understandable because I had to cut pkg-plist down to the files, ne= eded by dns/knot3 only. If you do want, I can provide you with diffs against my local/knot3 et al. = But these are no 'git --diff' yet. > Basically the problem is that there is no way to signal to Knot-DNS=20 > to use the already present lib. Regardless it just installs it, since=20 > it (correctly) expects that it is the only source of it. Except, one makes dns/knot3 AND dns/knot-resolver dependent on dns/knot3-lib ;-) > Contrary you could also say the 'duplicate path check' is creating a=20 > problem of something that actually isn't a problem. True. But how would one achieve this, if possible at all? I do not have eno= ugh experience with modifying ports. > Question: > Is this error actually always occuring, regardless of the order of instal= l? > Since dns/knot3-lib is a metaport of dns/knot3 I find it odd that it's in= conflict=20 > with itself. In the meantime I found: 1) poudriere bulk -j xyz dns/knot-resolver dns/knot3 works. But if you=20 do install both packages, they do remove each other leaving you with=20 only one port becomes installed by removing the other. Order doesn't matter. 2) I do use metaports for my grouping of relevant ports per jail et al.=20 And here, order doesn't matter. Error message see first comment of mine. --=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-277332-7788-J0RIy8wy89>