incubator-ooo-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
Subject [CONF] Apache OpenOffice Community > AOO 3.4 Release FAQ
Date Wed, 28 Mar 2012 12:57:00 GMT
Space: Apache OpenOffice Community (
Page: AOO 3.4 Release FAQ (

Added by Armin Le Grand:
This page describes the structure of the Apache OpenOffice 3.4 (AOO3.4) release and questions
related to it. It is intended e.g. to help reviewing a release candidate.

*Q: How is a AOO3.4 release structured?*
A: The AOO3.4 release is composed of two main parts, the source release and the binary release.

*Q: What is contained in the source part of the release?*
A: The source release contains the fill set of files from which the binary releases are created.
It contains all files necessary to build a version of AOO3.4 by others. It includes files
from the project trunk which are under ALv2 Apache license and files under Apache [category
A|], thus these file collections allow to build complete,
ALv2-compatible versions of AOO3.4. For information how to build AOO3.4 based on this file
sets, see [here|]. Detailed
information (e.g. signature) and examples based on the current developer snapshots can be
found [here|].

*Q: What is contained in the binary part of the release?*
A: The binary part will be a combination of [full installation sets|],
[multilingual full installation sets|]
and individual [language packs|].
For a release candidate these will be signed to allow checking them being unmodified and from
Apache. The binary release will contain external components which may be classified as Apache
[category B|] and cannot be part of the source release.
This is done for the end user's convenience so that not everyone who downloads AOO3.4 has
to install some components by himself. Extra stuff added in this way contains e.g. Hyphenation
and Spelling data sets, but also external libraries which extend the functionality of AOO3.4.

*Q: How is the source release created?*

*Q: What is trunk/ext_libraries?*
A: When looking at the project's [trunk|]
yo can see a sub directory called [ext_libraries|].
It is part of the source release. The projects there contain mechanisms to download, patch
and build modules needed for a configured build (see [Building Guide|]),
but not the external code. The modules could also be part of the trunk/main directory, but
are a starting point for successively moving external content out of the trunk/main to get
a cleaner source structure in the future. New added libraries whcih need external content
should be added here.

*Q: What is trunk/ext_sources?*
A: When looking at the project's [trunk|]
yo can see a sub directory called [ext_sources|].
This contains additions to the regular AOO3.4 which are not in the Apache source release,
but extend the functionality of the binary AOO3.4 releases. This is done to not force each
AOO3.4 user to install these contained additional functionality himself. ext_source is not
part of the source release. For being able to build various configured versions of AOO3.4
(using configure flags, see [Building Guide|])
the build environment has mechanisms to dynamically download the contents needed from sources
of the net.

*Q: Where are the LICENSE and NOTICE files?*

*Q: What information is contained in the LICENSE file?*

*Q: What information is contained in the NOTICE file?*

*Q: What are category-b components and how are these handled for building AOO3.4?*

Change your notification preferences:

View raw message