The Samba suite is a set of programs which run under the FreeBSD
operating system. These programs deliver most of the important
functionality of a Microsoft Lan Manager server. That is, they support
remote access to FreeBSD filespace and FreeBSD printers from Lan Manager
compatible clients. In practical terms, this means that such clients can
connect to and use FreeBSD filespace as if it was a local disk drive, or
FreeBSD printers as if they were local printers.
Some of the most popular Lan Manager compatible clients include Lan
Manager itself, Windows for Workgroups, OS/2 and Windows NT.
WWW: http://www.samba.org/

===> The following configuration options are available for samba35-3.5.19:
LDAP=on: With LDAP support
ADS=off: With Active Directory support
CUPS=on: With CUPS printing support
WINBIND=on: With WinBIND support
SWAT=off: With SWAT WebGUI
ACL_SUPPORT=off: With ACL support
AIO_SUPPORT=off: With Asyncronous IO support
FAM_SUPPORT=off: With File Alteration Monitor
SYSLOG=off: With Syslog support
QUOTAS=off: With Disk quota support
UTMP=off: With UTMP accounting support
PAM_SMBPASS=off: With PAM authentication vs passdb backends
DNSUPDATE=off: With dynamic DNS update(require ADS)
AVAHI=off: With Bonjour service discovery support
EXP_MODULES=off: With experimental modules
POPT=on: With system-wide POPT library
IPV6=on: With IPv6 support
MAX_DEBUG=off: With maximum debugging
SMBTORTURE=off: With smbtorture
===> Use 'make config' to modify these settings

Reason:
A bug, introduced by local patch to pam_winbind.so, that made it coredump
was spotted by Martin Minkus. It is fixed in the 3.5.9 version of the port.
So, if pam_winbind.so started to work for you - send him kudos.

2010-10-26

Affects: users of net/samba35

Author: Timur Bakeyev <timur@FreeBSD.org>

Reason:
This is the latest stable release of the Samba3 distribution. It has
been extended with the experimental support of the NFS4-like ACLs on
ZFS partitions, thanks to the sysutils/libsunacl library by Edward
Tomasz Napierala(trasz). This support haven't been tested thoroughly,
so try it on your own risk.
This port reverted back to the pre- net/samba34 layout of the
directories and now they are again $PREFIX/etc/samba, /var/run/samba,
/var/log/samba, /var/db/samba and /var/spool/samba respectively.
In case, you are upgrading from net/samba34, please rename
corresponding samba34/ subdirectories into samba/ ones. Upgrades from
older versions of Samba and fresh installations should be seamless.

Port Moves

port deleted on 2013-01-31REASON: Obsoleted by net/samba36

Number of commits found: 20

Commit History - (may be incomplete: see SVNWeb link above for full details)

new devel/pkgconf added to replace devel/pkg-config. new version of pkg-config
are no more self hosting so we are stuck with 0.25 version while pkgconf provide
the same set of features as 0.27 and a compatible frontend. A symlink to
pkg-config has been added for convenience and compatibility
This also introduces a new macro to use pkgconf in your ports:
USE_PKGCONFIG
it can take the following arguments:
- yes (meaning build only dep)
- build (meaning build only dep)
- run (meaning run only dep)
- both (meaning run and build dep)
From now USE_GNOME= pkgconfig is deprecated in favour of USE_PKGCONFIG
The old gnome macro has been modified to use pkgconf but still the sameway: run
and build dep to avoid large breakage.
While here fix some ports relying on pkg-config but not specifying it, fix some
ports broken because testing wrong .pc files, and fix ports using pkg-config
--version to determine pkg-config version instead of
pkg-config --modversion pkg-config like recommanded by pkg-config
With Hat: portmgr
Exp-runs by: bapt (pointhat-west), beat (pointyhat)

The samba rc.d script uses some clever tricks to start (up to) 3 different
services using the same script. As a result it resets rcvar several times
in order to process the options for each service.
The changes I made on 2012/01/14 to facilitate the removal of set_rc_var()
from HEAD were effective in the case where the WINBIND option was off (the
case that I tested) because that causes the related portions of the rc.d
script to be removed completely on install. However, if installed from a
package, or installed using the the default OPTIONS, WINBIND is on, which
caused the last known rcvar to be winbind_enable.
Since the common case seems to be for users to use samba_enable (which
only enables smb_and nmb_ by default) the fact that rcvar=winbind_enable,
but that knob is off, caused the startup script to trip on a totally
unrelated portion of rc.subr.

In the rc.d scripts, change assignments to rcvar to use the
literal name_enable wherever possible, and ${name}_enable
when it's not, to prepare for the demise of set_rcvar().
In cases where I had to hand-edit unusual instances also
modify formatting slightly to be more uniform (and in
some cases, correct). This includes adding some $FreeBSD$
tags, and most importantly moving rcvar= to right after
name= so it's clear that one is derived from the other.