Date: Fri, 17 Jun 2016 10:01:22 +0200 From: Kurt Jaeger <lists@opsec.eu> To: Matthias Fechner <idefix@fechner.net> Cc: ports@freebsd.org Subject: Re: net/samba-libsmbclient depends on complete outdated samba36 Message-ID: <20160617080122.GL41922@home.opsec.eu> In-Reply-To: <c192cfe4-f099-a206-c406-48890f0591b8@fechner.net> References: <c192cfe4-f099-a206-c406-48890f0591b8@fechner.net>
next in thread | previous in thread | raw e-mail | index | archive | help
Hi! > I just testing the www/nextcloud port that was commited yesterday, > thanks a lot for this! > > There I saw that samba36 will be installed (in addition to samba43). > > I think the problem is located in port net/samba-libsmbclient which > refers to: > SAMBA_PORT= samba36 > SAMBA_SUBPORT= yes > > Does anyone have an idea to get this old samba version problem fixed? As far as I see, samba36 has the --with-libsmbclient option, which is missing in newer samba4x. Someone needs to talk to the samba folks what they plan to do about this. In general it's a difficult task: - we need find a way to build a seperate libsmbclient with newer samba version, probably as a parallel install to the 36 version - then chase all apps that depend on samba36-libsmbclient and try to build them with that newer version - if necessary, upstream changes -- pi@opsec.eu +49 171 3101372 4 years to go !
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20160617080122.GL41922>