Opened 10 years ago

Closed 10 years ago

#24205 closed defect (fixed)

Enable SSL by default for ldns

Reported by: anand@… Owned by: marius.rieder@…
Priority: Normal Milestone:
Component: ports Version: 1.8.2
Keywords: Cc: deric@…, marius.rieder@…, wouter@…, nerdling (Jeremy Lavergne)
Port: unbound ldns

Description

The current port of unbound, 1.4.3_1, fails to install, because of a conflict with the ldns port.

Here's the issue: unbound depends on ldns WITH ssl support. On my system, I do have ldns installed WITH ssl support, and unbound links against it. However, the Portfile of unbound explicitly lists a conflict with ldns, because it seems to assume that unbound will use the built-in ldns.

This isn't an ideal situation, because I don't want to remove my ldns package just to install unbound. I need the ldns package, because it is required by the ldns-tools package, which I often make use of.

One solution is probably to make SSL support for ldns mandatory instead of a variant. That way, unbound can always use the external ldns, and one can have them both installed on a system.

Attachments (1)

ldns-ssl-1.6.4.patch (3.8 KB) - added by marius.rieder@… 10 years ago.

Download all attachments as: .zip

Change History (8)

comment:1 Changed 10 years ago by jmroot (Joshua Root)

Cc: deric@… marius.rieder@… added
Owner: changed from macports-tickets@… to snc@…

Please remember to cc the maintainers.

comment:2 Changed 10 years ago by nerdling (Jeremy Lavergne)

Cc: snc@… added
Owner: changed from snc@… to marius.rieder@…
Port: ldns added

comment:3 Changed 10 years ago by nerdling (Jeremy Lavergne)

Summary: Unbound fails to installEnable SSL by default for ldns

Changed 10 years ago by marius.rieder@…

Attachment: ldns-ssl-1.6.4.patch added

comment:4 Changed 10 years ago by marius.rieder@…

If updated and ssl enabled ldns. Patch is attached. Can you please test if unbound work with this?

I had successfully build unbound with conflicts removed and " --with-ldns=${prefix}" added to configure.args in unbound. But i don't know unbound, so please test if it's working correctly.

  • Marius

comment:5 in reply to:  4 ; Changed 10 years ago by anand@…

Hi Marius,

I've tested the patch, and built unbound against it, and it seems to run just fine. You may commit it. And the unbound maintainers can also update the port to remove the conflict.

comment:6 in reply to:  5 Changed 10 years ago by marius.rieder@…

Hi

Replying to anand@…:

I've tested the patch, and built unbound against it, and it seems to run just fine.

I'm happy to hear this.

You may commit it. And the unbound maintainers can also update the port to remove the conflict.

As i don't have commit access, i hope the unbound maintainers feel free to commit it together with unbound.

  • Marius

comment:7 Changed 10 years ago by nerdling (Jeremy Lavergne)

Resolution: fixed
Status: newclosed

Updated by dports: drill in r69210, ldns in r69208, ldns-tools in r69209.

Note: See TracTickets for help on using tickets.