[Bug 241347] security/sssd: Update to 1.16.4

[bugzilla-noreply at freebsd.org]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=241347

--- Comment #7 from Rick <vrwmiller at gmail.com> ---
Thanks for explaining 1.16 vs 2.x. It makes sense to track the same version
being deployed in Red Hat.

In considering explicit Samba dependencies, my preference remains in favor of
putting control in the users hands unless there is material information I am
missing or misunderstanding. Explicit dependency works for users pulling in
Samba as a direct consequence of sssd. However, users pulling in Samba as a
consequence of sssd and one or more other ports may experience conflicts and/or
failed builds.

Defining explicit dependencies also implies more effort to ensure
compatibility. In other words, ports defining explicit dependencies must stay
vigilant as Samba versions are deprecated. SSSD fell victim to this as Samba
4.[678] have and are reaching EOL as proven by its failure to build w/ SMB from
July 2019 on after Samba 4.[67] were removed and thus defaults to 4.8.

Comments to Makefile or UPDATING explaining and recommending defining default
Samba to 4.10 when SMB is enabled are appropriate w/ the addition that changing
the default may result in undesirable behavior as a consequence of differing
ABIs with winbind_idmap_sss.so. This is irrelevant to me as each repository
stands on it’s own.

Having said all that, sssd w/ the attached patch for 1.16.4 continues to fail
during configure citing the error above. It occurs even despite defining
PYTHON_VERSION and/or PYTHON_CMD in make.conf for either Python 2.7 or 3.6
like:

.if ${.CURDIR:M*/security/sssd}
PYTHON_VERSION= 3.6
PYTHON_CMD=/usr/local/bin/python3.6
OPTIONS_FILE_SET+=SMB  
.endif

-- 
You are receiving this mail because:
You are the assignee for the bug.