[SCM] Samba Shared Repository - branch master updated
Andrew Bartlett
abartlet at samba.org
Thu May 24 20:20:03 MDT 2012
The branch, master has been updated
via eec4f80 move VERSION to alpha22
via 9ccbe16 WHATSNEW: update for alpha21, and mark as release
via 7891ad4 wintest: s3fs is now the default in provision
via 1876d63 doc: Explain our build systems for Samba 4.0
from 64ddb66 s3:smbd/signing: use smbd_server_connection as talloc parent for its smb1 signing state
http://gitweb.samba.org/?p=samba.git;a=shortlog;h=master
- Log -----------------------------------------------------------------
commit eec4f80d613c2c725194a23d208d51a616c3156e
Author: Andrew Bartlett <abartlet at samba.org>
Date: Fri May 25 10:20:46 2012 +1000
move VERSION to alpha22
We will change this to beta once we both fix the VERSION parsing scripts
and we agree that the next release will indeed be the beta.
Andrew Bartlett
Autobuild-User: Andrew Bartlett <abartlet at samba.org>
Autobuild-Date: Fri May 25 04:19:30 CEST 2012 on sn-devel-104
commit 9ccbe1660c466f6c45f6b61a32f6ec5813ccf380
Author: Andrew Bartlett <abartlet at samba.org>
Date: Fri May 25 10:17:34 2012 +1000
WHATSNEW: update for alpha21, and mark as release
The plan has changed. This will we hope be the last alpha.
Andrew Bartlett
commit 7891ad478b46d756a6ff402f62bd529f5520434f
Author: Andrew Bartlett <abartlet at samba.org>
Date: Fri May 25 08:52:47 2012 +1000
wintest: s3fs is now the default in provision
commit 1876d63083e3c4c9a4f6112cca423dcf9b00acfe
Author: Andrew Bartlett <abartlet at samba.org>
Date: Thu May 24 20:31:37 2012 +1000
doc: Explain our build systems for Samba 4.0
-----------------------------------------------------------------------
Summary of changes:
BUILD_SYSTEMS.txt | 97 ++++++++++++++++++++++++++++++++++++++++++++++
VERSION | 2 +-
WHATSNEW.txt | 16 ++++----
wintest/test-s4-howto.py | 3 +-
4 files changed, 107 insertions(+), 11 deletions(-)
create mode 100644 BUILD_SYSTEMS.txt
Changeset truncated at 500 lines:
diff --git a/BUILD_SYSTEMS.txt b/BUILD_SYSTEMS.txt
new file mode 100644
index 0000000..2aff56d
--- /dev/null
+++ b/BUILD_SYSTEMS.txt
@@ -0,0 +1,97 @@
+BUILDING SAMBA 4.0
+(which build system to use and why)
+===================================
+
+The waf build
+-------------
+
+Samba 4.0 ships with a new build system, based on waf. A background to
+this build system can be found at https://wiki.samba.org/index.php/Waf
+
+This is the build system that is used when you run ./configure && make
+in the top level of a Samba 4.0 release tree.
+
+For the vast majority of our users, this is the build system you should
+use. It supports parallel and incremental builds, and builds the whole
+Samba suite, the file server, the print server, the NT4 domain
+controller, winbind, the AD Domain Controller, the client libraries and
+the python libraries.
+
+A key feature for many of our distributors and OEMs is that despite the
+range of additional features, the resulting binaries and libraries are
+substantially smaller, because we use shared libraries extensively.
+
+For distributions that have a requirement to use the system-supplied
+Kerberos library, we support building against a Heimdal or system MIT
+Kerberos library, provided the version is recent enough (otherwise we
+will use our internal version of Heimdal). Please note that builds
+with MIT krb5 support will not have AD DC features.
+
+By the time of the first release candidate, we will finish renaming
+the binaries that we ship so that where we provide a tool under a name
+that was used in Samba 3.x, it continues to behave in the same way it
+always has. This will ensure that our change in build system does not
+impact on our user's ability to use Samba as they always have.
+
+For developers, this build system backs a comprehensive 'make test',
+which provides code coverage of around 48% of our code by line:
+https://build.samba.org/lcov/data/coverage/samba_4_0_test/
+
+This build system also implements important features such as ABI
+checking (which protects you as users from accidental changes to our
+published libraries), symbol versions and dependency checked incremental
+rebuilds after header-file changes.
+
+The waf build also assists developers by providing fully-linked binaries
+that run from bin/ without needing to set LD_LIBRARY_PATH.
+
+For users who do not have python installed on their systems, we provide
+a install_with_python.sh script, which will install a local copy of
+python sufficient to run the build system, without impacting on the rest
+of the system.
+
+Within this requirement, we expect that this build will run on all our
+supported platforms, and will actively deal with any portability issues
+that users can bring to our attention.
+
+For all these reasons, we highly recommend this new build system to all
+our users, for whatever purpose you want to put Samba to.
+
+The autoconf build
+------------------
+
+For a small number of users, the requirement to have access to Python
+2.4 and perl will be unacceptable, and for these users we continue to
+provide the 'autoconf' build system used in Samba 3.x under the
+source3/. This will build fewer parts of Samba, but should not be seen
+as 'the file server build' (typical file server deployments should use
+the top level build), but as a measure provided with limited features
+for systems and organisations unable to meet the requirements for the
+new build system.
+
+If you do need to use the autoconf build system, please let us know:
+both why you cannot use the 'waf' build in the top level, and what
+features of the source3 build that you require. We need this
+information to assess the continuing demand for this parallel
+infrastructure, and to determine which features need to remain available
+in both build systems.
+
+Optional Libraries
+------------------
+
+To assist users and distributors to build Samba with the full feature
+set, by the first release candidate the build system will abort if our
+dependent libraries and their header files are not found on the target
+system. This will mean for example, that xattr, acl and ldap headers
+must be installed for the default build to complete. The configure
+system will check for these headers, and the error message will
+indicate:
+ - the required header and library
+ - the option (such as --without-acl-support) that can be specified to
+ skip this requirement, and
+ - the feature (ACL support optional for file servers, mandatory for AD
+ Domain Controller) being skipped.
+
+This will assist users and in particular distributors in building fully
+functional packages, while allowing those on systems truly without these
+facilities to continue to build Samba after careful consideration.
diff --git a/VERSION b/VERSION
index 87f40ab..1dc74f2 100644
--- a/VERSION
+++ b/VERSION
@@ -57,7 +57,7 @@ SAMBA_VERSION_TP_RELEASE=
# e.g. SAMBA_VERSION_ALPHA_RELEASE=1 #
# -> "4.0.0alpha1" #
########################################################
-SAMBA_VERSION_ALPHA_RELEASE=21
+SAMBA_VERSION_ALPHA_RELEASE=22
########################################################
# For 'pre' releases the version will be #
diff --git a/WHATSNEW.txt b/WHATSNEW.txt
index 41e6055..d737e95 100644
--- a/WHATSNEW.txt
+++ b/WHATSNEW.txt
@@ -1,4 +1,4 @@
-What's new in Samba 4 beta1
+What's new in Samba 4 alpha21
=============================
Samba 4.0 will be the next version of the Samba suite and incorporates
@@ -11,7 +11,7 @@ and above.
WARNINGS
========
-Samba4 beta1 is not a final Samba release, however we are now making
+Samba4 alpha21 is not a final Samba release, however we are now making
good progress towards a Samba 4.0 release, of which this is a preview.
Be aware the this release contains the best of all of Samba's
technology parts, both a file server (that you can reasonably expect
@@ -26,9 +26,9 @@ Samba 3.x release to Samba 4.0 alpha at this stage.
In particular note that the new default configuration 's3fs' may have
different stability characteristics compared with our previous default
file server. We are making this release so that we can find and fix
-any of these issues that arise in the real world. AD DC installations
+any of these issues that arise in the real world. New AD DC installations
can provision with --use-ntvfs to obtain the previous default file
-server.
+server. Existing installations will be unaffected at this stage.
If you are upgrading, or looking to develop, test or deploy Samba 4.0
alpha releases, you should backup all configuration and data.
@@ -36,7 +36,7 @@ alpha releases, you should backup all configuration and data.
NEW FEATURES
============
-Samba 4.0 beta supports the server-side of the Active Directory logon
+Samba 4.0 alpha supports the server-side of the Active Directory logon
environment used by Windows 2000 and later, so we can do full domain
join and domain logon operations with these clients.
@@ -72,11 +72,11 @@ internal workings of the DC code is now implemented in python.
CHANGES SINCE alpha20
=====================
-For a list of changes since alpha 19, please see the git log.
+For a list of changes since alpha20, please see the git log.
$ git clone git://git.samba.org/samba.git
$ cd samba.git
-$ git log samba-4.0.0alpha20..samba-4.0.0beta1
+$ git log samba-4.0.0alpha20..samba-4.0.0alpha21
Some major user-visible changes include:
@@ -102,7 +102,7 @@ the team improves and develops support these new protocols.
KNOWN ISSUES
============
-- We are making this beta release to gain real-world use of the 's3fs'
+- We are making this alpha release to gain real-world use of the 's3fs'
file server combination we will use for the Samba 4.0 release.
Users should expect some rough edges: in particular, there are
warnings about invalid parameters from the two respective parameter
diff --git a/wintest/test-s4-howto.py b/wintest/test-s4-howto.py
index 032c312..36beabb 100755
--- a/wintest/test-s4-howto.py
+++ b/wintest/test-s4-howto.py
@@ -35,8 +35,7 @@ def provision_s4(t, func_level="2008"):
'--option=interfaces=${INTERFACE}',
'--host-ip=${INTERFACE_IP}',
'--option=bind interfaces only=yes',
- '--option=rndc command=${RNDC} -c${PREFIX}/etc/rndc.conf',
- '--use-s3fs=yes']
+ '--option=rndc command=${RNDC} -c${PREFIX}/etc/rndc.conf']
if t.getvar('INTERFACE_IPV6'):
provision.append('--host-ip6=${INTERFACE_IPV6}')
t.run_cmd(provision)
--
Samba Shared Repository
More information about the samba-cvs
mailing list