Solved net/samba410 depends on dns/py-dnspython

Hello all,

Does anyone know why net/samba410 depends on dns/py-dnspython when none of the front end DNS selected:

Code:
/usr/ports/net/samba410 # make showconfig
===> The following configuration options are available for samba410-4.10.13:
     ADS=off: Active Directory client(implies LDAP)
     AD_DC=off: Active Directory Domain Controller
     AESNI=on: Accelerated AES crypto functions(amd64 only)
     CLUSTER=off: Clustering support
     CUPS=off: CUPS printing system support
     DEBUG=off: Build with debugging support
     DEVELOPER=off: With developer framework(implies NTVFS)
     DOCS=off: Build and/or install documentation
     FAM=on: File Alteration Monitor
     GPGME=off: GpgME support
     LDAP=on: LDAP client
     MANDOC=off: Build manpages from DOCBOOK templates
     NTVFS=off: Build *DEPRECATED* NTVFS file server
     PROFILE=on: Profiling data
     QUOTAS=on: Disk quota support
     SPOTLIGHT=off: Spotlight server-side search support
     SYSLOG=on: Syslog logging support
     UTMP=on: UTMP accounting
====> VFS modules
     FRUIT=on: MacOSX and TimeMachine support
     GLUSTERFS=off: GlusterFS support
====> GSSAPI Security API support: you have to select exactly one of them
     GSSAPI_BUILTIN=off: GSSAPI support via bundled Heimdal
     GSSAPI_MIT=on: GSSAPI support via security/krb5
====> Zero configuration networking: you have to select exactly one of them
     ZEROCONF_NONE=off: Zeroconf support is absent
     AVAHI=on: Zeroconf support via Avahi
     MDNSRESPONDER=off: Zeroconf support via mDNSResponder
====> DNS frontend: you can only select none or one of them
     NSUPDATE=off: Use samba NSUPDATE utility for AD DC
     BIND911=off: Use Bind 9.11 as AD DC DNS server frontend
     BIND914=off: Use Bind 9.14 as AD DC DNS server frontend
===> Use 'make config' to modify these settings

According to this required dependencies, DNS isn't needed when AD_DC is also off. This requirement of dns/py-dnspython is indirectly blocking another port from installing.

Thanks,
Tommy
 
It looks to be pulled in due to Python. There doesn't seem to be a option for it but you can try building it with NO_PYTHON set. No idea what the implications are though, other things might break if you set this.
I don't think it would work since the official wiki said python3 is mandatory because of the server tools and the build system (Waf). I tried compiling without the dns/py-dnspython and the SMB share works as needed. Now, I'll just need to create working patch and submit a PR.

Thanks for your help.
 
Back
Top