Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 26 Jul 2024 17:18:31 +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-JQzto0kMA1@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 #8 from Leo Vandewoestijne <freebsd@dns.company> ---
I tried your patches several times.
And indeed the move of knot-lib entries to LDCONFIG makes a difference.
But every time I finalize the port to be perfect, then the same problem
re-occurs. And I can't put the finger to the cause (yet).

So earlier this week I came to a solution which shares more values - to pre=
vent
double maintenance of the two ports. Then when I was comparing the pkg-plis=
t,
the only difference are the executables, which are of limited size anyway. =
And
the dependencies seem equal.
And so I start to wonder wether it isn't smarter to simply make knot-resolv=
er
depend on knot3, and get rid of the knot3-lib port.

Then for users who insists not wanting the daemon I theoretically could sim=
ply
add post-install rm commands, which would make my life and everybody elses a
lot easier.

Ahead of your previous reply I also was looking how to install everything as
not-root, but I haven't tested what happens when kresd:kresd starts using t=
he
lib which is knot:knot
It's on my radar.

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