|
|
Directory and File NamesDirectoriesDirectories are created in the mirroring directory structure.Directory names follow the numbering scheme of releases or developer builds respectively. Files
File names follow the following scheme: OOo = static string "OOo" for release builds and RCs|"OOo-Dev" for snapshot builds that can be installed in parallel to an OOo build|"OOo-SDK" for the software development kit|"OOo-URE" for the UNO runtime environment
Examples:Developer Snapshot builds: OOo-Dev_OOE680_m3_Solarisx86_install.tar.gz OOo-Dev_SRC680_m193_Solarisx86_install.tar.gz vs. Release Candidates: OOo_2.1.0rc1_20061124_Solarisx86_install_de.tar.gz OOo_2.1.0rc1_20061124_Solarisx86_install.tar.gz (en-US optional) Source file example: OOo_OOE680_m3_src.tar.gz OOo_SRC680_m193_src.tar.gz OOo_2.1.0rc1_20061124_src.tar.gz If the source archive is split into several parts then use OOo_OOE680_m3_src-core.tar.gz OOo_OOE680_m3_src-binfilter.tar.gz OOo_OOE680_m3_src-l10n.tar.gz OOo_OOE680_m3_src-system.tar.gz SDK: OOo-SDK_2.1.0_SolarisSparc_install.sh (en-US optional) OOo-URE_1.1.0_LinuxIntel_install.sh (en-US optional) Solver: OOo_2.1.0_WindowsIntel_solver.zip For locales we use 2 letter ISO codes, e.g. To make the filenames even longer but expressing all necessary informationuntested versions are tagged with the date (YYYYMMDD) of creation. This extends the scheme from above to OOo(product name)_Version_YYYYMMDD_OSCPU_what_locale(optional _wJRE).extAn example is OOo_2.1.0rc1_20061122_Solarisx86_install_de_wJRE.tar.gz These schemes are taken and extended from a discussion on releases mailing list.$Id: filenames.html,v 1.6 2006/11/23 15:50:24 ja Exp $ |


