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, 04 Apr 2012 13:48:00 GMT
Space: Apache OpenOffice Community (
Page: AOO 3.4 Release FAQ (

Change Comment:
update src release packaging

Edited by Juergen Schmidt:
This page describes the structure of the Apache OpenOffice 3.4 (AOO3.4) release, the project's
[trunk|] and questions related to these
and their structure. It is intended e.g. to help reviewing a release candidate. A summary
of the activities that we undertook to get us to this point are described in [OOOUSERS:Summary
of Apache OpenOffice 3.4 IP Review Activities]   Additional information can also
be found under [IP Plan for Apache OpenOffice.|]

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

*Q: What is contained in the source package of the release?*
A: The source package contains the full set of files from which the binary packages are created.
It contains all files necessary to build a version of AOO3.4 by externals. It includes all
files from the project trunk which are under ALv2 Apache license and files under Apache [category
A|] license, 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 about e.g. signature and examples based on the current developer snapshots
can be found [here|].

*Q: What is contained in the binary package of the release?*
A: The binary package 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 originally
from Apache. The binary release will contain external components which may be classified as
Apache [category B|] and thus 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 components he is interested in by himself. Extra stuff added this way
contains e.g. Hyphenation and Spelling data, language sets, but also external libraries which
extend the functionality of AOO3.4.

*Q: How is the source release created?*
A: The source release packages are created by an ant script (_main/solven/bin/srcrelease.xml_)
which is triggered as special make target (_dmake aoo_srcrelease_) in the module/directory
_main/instsetoo_native/util_ where the binary packages (full install sets, language packs)
are built as well. The script packs all relevant content from trunk excepting some stuff that
is in trunk for convenience only like _ext_sources_. The script can be run at every time and
will exclude all generated files and pack the files from the repository only. The NOTICE,
LICENSE and README file from _main_ are copied in the root directory of the source release
package. The structure for AOO 3.4 looks like:

*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 which 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