Page MenuHomeFreeBSD

Make dns/samba-nsupdate a slave port of dns/bind912
Needs ReviewPublic

Authored by timur on Aug 24 2018, 12:08 AM.
Referenced Files
Unknown Object (File)
Dec 20 2022, 1:58 AM
Unknown Object (File)
Nov 27 2022, 11:36 AM
Subscribers
This revision needs review, but there are no reviewers specified.

Details

Reviewers
None
Summary

While ago when samba ports needed specially compiled version of nsupdate with enabled GSS-TSIG feature I've just created a separate port for it, samba-nsupdate.

I find it's a duplicate effort to maintain such a separate port and think it's beneficial to make it slave port of the dns/bind* port. Such an addition requires some changes in the dns/bind-tools and dns/bind912 ports.

Test Plan

Compile all 3 ports in poudriere, make sure that resulting packages are haven't changed.

Diff Detail

Repository
rP FreeBSD ports repository
Lint
Lint Skipped
Unit
Tests Skipped

Event Timeline

I completely disagree with this changes, I refuse to maintain the samba-nsupdate port.

timur removed rP FreeBSD ports repository as the repository for this revision.
timur changed the visibility from "Public (No Login Required)" to "No One".
timur changed the edit policy from "All Users" to "No One".
timur changed the visibility from "No One" to "Public (No Login Required)".Aug 18 2020, 1:48 AM
timur changed the edit policy from "No One" to "All Users".
timur added a project: Ports Committers.

To avoid collisions with DHCP and other applications,
it might be better to just depend on the binaries created by bind-tools?

$ pkg which /usr/local/bin/nsupdate
/usr/local/bin/nsupdate was installed by package bind-tools-9.16.5

The port can error out if the tolls do not have ben build with the needed options.

I guess you miss the point.. For nsupdate to be any usable as a intermediator between Samba and bind9 it has to be compiled against (some) Kerberos library.

The default settings for bind-tools don't enable this option, and, at least in the past there was no selection of which Krb5 implementation to use.

Hence I had to introduce separate binary, samba-nsupdate which always build against Krb5.

From other side, it just a custom build of one binary from bind-tools and with a bit of OPTIONS magic and slave port it can follow the bind9 mainstream port nicely.

ATM I have to literally copy whatever mat@ did to the current bind port, which is kind of error prone and waste of effort.

What I proposed while ago is to have a happy family of bind9 slave ports which co-exist peacefully together.

But, for whatever reason mat@ is against it :(