On 8/5/24 16:15, Andy Lemin wrote:
Hi List!
Hello.
I reported this to Netatalk, and they advised that we ask your opinions?
I'm not the port maintainer, but I'll try to answer anyway...
Simply samba419 port demands that talloc is _not_ installed, as samba
bundles talloc.
That's an option: you can try modifying the value of
SAMBA4_BUNDLED_TALLOC in the Makefile to no.
I'm not sure it will even build, however.
See:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=280510
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=280557
However this means that no other packages (including Netatalk) can also
use talloc on the same server, as trying to install talloc results in
samba being removed.
That's the rationale behind those bug reports.
Conflict causing one or the other to be removed;
'talloc-2.3.4_1 conflicts with samba419-4.19.7 on
/usr/local/lib/python3.11/site-packages/talloc.cpython-311.so'
We can understand why samba want to bundle talloc, but wonder if this is
actually a porting issue instead?
It *is* a porting issue.
bye
av.
