ports/64523: Make samba-libsmbclient subport of samba-devel

Michael Nottebrock michaelnottebrock at gmx.net
Wed Apr 7 16:01:56 UTC 2004


The following reply was made to PR ports/64523; it has been noted by GNATS.

From: Michael Nottebrock <michaelnottebrock at gmx.net>
To: "Timur I. Bakeyev" <timur at com.bat.ru>
Cc: freebsd-gnats-submit at FreeBSD.org
Subject: Re: ports/64523: Make samba-libsmbclient subport of samba-devel
Date: Wed, 7 Apr 2004 17:49:20 +0200

 --Boundary-02=_DMCdA3AprakmlzN
 Content-Type: text/plain;
   charset="koi8-r"
 Content-Transfer-Encoding: quoted-printable
 Content-Disposition: inline
 
 On Wednesday 07 April 2004 17:22, Timur I. Bakeyev wrote:
 
 > >1.) samba-devel and samba-libsmbclient still conflict
 > >with each other, which
 > >doesn't make sense. Having a client library installed
 > >must not prevent people
 > >from installing the server.
 >
 > This is quite compleax question, on my opinion. The
 > problem with current approach is that samba-libsmbclient
 > installs the most simplistic version of library, bare
 > bones, I'd say.
 
 This can probably be optionalized in the samba-libsmbclient port.
 
 > My point to keep libsmbclient in samba-devel is the one,
 > mentioned above, plus expences of double compilation of
 > samba tree, which isn't so small. If everyone(who depend
 > on libsmbclient) thinks it's ok, we can get rid of client
 > library from samba-devel.
 
 We really have to at some point. For example with the current status quo, y=
 ou=20
 cannot install samba-devel when you're using KDE - because kdebase depends =
 on=20
 samba-libsmbclient (as it only uses client functionality) and with that=20
 installed, the CONFLICTS prevents users from installing samba-devel.
 
 > >2.) The slave port has stylebugs (see ports/64393).
 >
 > Hm.. I've looked over the whole PR and didn't find
 > anything,  in the slave port, that conflicts with the
 > statements there. Contrary, samba-devel itself has
 > problems with style and doesn't validate by portlint(but
 > thats a separate issue, that involves OPTIONS and
 > structure of bsd.ports.mk).
 >
 > Can you point me, what's wrong with the slave port on your
 > opinion.
 
 I can't - I guess I imagined the errors I saw, forget about it :-}.
 
 =2D-=20
    ,_,   | Michael Nottebrock               | lofi at freebsd.org
  (/^ ^\) | FreeBSD - The Power to Serve     | http://www.freebsd.org
    \u/   | K Desktop Environment on FreeBSD | http://freebsd.kde.org
 
 --Boundary-02=_DMCdA3AprakmlzN
 Content-Type: application/pgp-signature
 Content-Description: signature
 
 -----BEGIN PGP SIGNATURE-----
 Version: GnuPG v1.2.4 (FreeBSD)
 
 iD8DBQBAdCMDXhc68WspdLARApzWAJ9cUhOs/SHxlRRVwMdTeDIEdAEh0QCfeeBO
 RbvJ2Z1TKA2qXu+9Lu0XarI=
 =jRRt
 -----END PGP SIGNATURE-----
 
 --Boundary-02=_DMCdA3AprakmlzN--



More information about the freebsd-ports-bugs mailing list