The current Apache OpenOffice supports Apple OS X version 10.7 (Lion), 10.8 (Mountain Lion), 10.9 (Mavericks), 10.10 (Yosemite), 10.11 (El Capitan) and macOS 10.12 (Sierra), 10.13 (High Sierra), 10.14 (Mojave), 10.15 (Catalina). The last OpenOffice version supporting Mac OS X 10.4 (Tiger), 10.5 (Leopard), 10.6 (Snow Leopard) is OpenOffice 4.0.1. Click on it and you will be presented with a green area holding some options. Make sure your operating system 'OS X (version = 10.7) (DMG)' is selected (unless you have an older mac which would be 32-bit). Select the version and language and click on Download full installation. Download the.dmg installation file.
Find packages for your operating system:
Centos Linux | Debian Linux | Fedora Linux | FreeBSD | HP-UX | NetBSD | OpenBSD | openSUSE | Mac OS X | Red Hat Linux | Solaris | SUSE Linux | Ubuntu Linux | Windows
The Apache Subversion project does not officially endorse or maintain any binary packages of the Subversion software. However, volunteers have created binary packages for different distributions and platforms, and as a convenience, we maintain a list of links to them here. If there are any problems with or questions about the different binary packages please send email to the Subversion users mailing list.
Note that binary packages usually come out about a week after the corresponding source release. Please don't post to the mailing lists asking when a binary package for a given platform will be ready. The packagers already know when new source releases come out, and work as fast as they can to make binaries available.
Mac OS X version 10.4 (Tiger) or later. A Java Runtime Environment 6 or later. Verify the integrity of the file. The PGP signatures can be verified using PGP or GPG. First download the KEYS as well as the asc signature file for the relevant distribution. Then verify the signatures using.
Binaries are typically built from the latest stable release.
Note also that this list does not include distributions of larger collections of software of which Subversion is but one piece. Several vendors offer such things, but we concern ourselves primarily with Subversion itself. As such, the listing here is limited to those packages which may be reasonably considered binary distributions of Apache Subversion alone. If you are looking for more widely scoped, Subversion-related value-add offerings, we trust that ${YOUR_FAVORITE_SEARCH_ENGINE}
can facilitate that for you.
CentOS project (client and server)
CollabNet (supported and certified by CollabNet; requires registration)
WANdisco (supported and certified by WANdisco; requires registration)
Debian Project (maintained by Debian Project; client and server; svnserve is part of the subversion package, mod_dav_svn is in the separate libapache2-mod-svn package (formerly libapache2-svn))
WANdisco (supported and certified by WANdisco; requires registration)
HP Porting Centre (maintained by Connect Internet Solutions Ltd.)
OpenBSD Project (client and server; svnserve is part of the subversion package, mod_dav_svn is in the separate ap2-subversion package)
Part of the the standard distribution. svnserve is part of the subversion package, mod_dav_svn is in the separate subversion-server package.
Community packages are available from the openSUSE project, also for the 1.8 series of releases.
Fink (requires Fink)
MacPorts (requires MacPorts)
WANdisco (client and server; supported and certified by WANdisco; requires registration)
Older Subversion binaries were provided with Xcode in versions of Mac OS X prior to 10.15 (Catalina). See the open source section of Apple's web site for more information.
Red Hat (client and server)
CollabNet (supported and certified by CollabNet; requires registration)
WANdisco (supported and certified by WANdisco; requires registration)
On SUSE Linux Enterprise: Enable the SDK. svnserve is part of the subversion package, mod_dav_svn is in the separate subversion-server package.
Community packages are available from the openSUSE project, also for the 1.8 series of releases.
WANdisco (supported and certified by WANdisco; requires registration)
Ubuntu Packages (maintained by Ubuntu Project; client and server; svnserve is part of the subversion package, mod_dav_svn is in the separate libapache2-svn package)
WANdisco (supported and certified by WANdisco; requires registration)
CollabNet (supported and certified by CollabNet; requires registration)
SlikSVN (32- and 64-bit client MSI; maintained by Bert Huijben, SharpSvn project)
TortoiseSVN (optionally installs 32- and 64-bit command line tools and svnserve; supported and maintained by the TortoiseSVN project)
VisualSVN (32- and 64-bit client and server; supported and maintained by VisualSVN)
WANdisco (32- and 64-bit client and server; supported and certified by WANdisco; requires registration)
The next step is to configure the Apache source tree for your particular platform and personal requirements. This is done using the script configure
included in the root directory of the distribution. How to play xbox one through laptop. (Developers downloading an unreleased version of the Apache source tree will need to have autoconf
and libtool
installed and will need to run buildconf
before proceeding with the next steps. This is not necessary for official releases.)
To configure the source tree using all the default options, simply type ./configure
. To change the default options, configure
Cached. accepts a variety of variables and command line options.
The most important option is the location --prefix
where Apache is to be installed later, because Apache has to be configured for this location to work correctly. More fine-tuned control of the location of files is possible with additional configure options.
Also at this point, you can specify which features you want included in Apache by enabling and disabling modules. Apache comes with a wide range of modules included by default. They will be compiled as shared objects (DSOs) which can be loaded or unloaded at runtime. You can also choose to compile modules statically by using the option --enable-module=static
.
Additional modules are enabled using the --enable-module
option, where module is the name of the module with the mod_
string removed and with any underscore converted to a dash. Similarly, you can disable modules with the --disable-module
option. Be careful when using these options, since configure
cannot warn you if the module you specify does not exist; it will simply ignore the option.
In addition, it is sometimes necessary to provide the configure
script with extra information about the location of your compiler, libraries, or header files. This is done by passing either environment variables or command line options to configure
. For more information, see the configure
manual page. Or invoke configure
using the --help
option.
For a short impression of what possibilities you have, here is a typical example which compiles Apache for the installation tree /sw/pkg/apache
with a particular compiler and flags plus the two additional modules mod_ldap
and mod_lua
:
$ CC='pgcc' CFLAGS='-O2'
./configure --prefix=/sw/pkg/apache
--enable-ldap=shared
--enable-lua=shared
When configure
is run it will take several minutes to test for the availability of features on your system and build Makefiles which will later be used to compile the server.
Details on all the different configure
options are available on the configure
manual page.