OpenOffice64

Differences between revisions 1 and 2
⇤ ← Revision 1 as of 2005-11-03 23:34:10 →
Size: 1810
Editor: 209
Comment: new page
← Revision 2 as of 2005-11-03 23:37:37 → ⇥
Size: 1819
Editor: 209
Comment:
Deletions are marked like this. Additions are marked like this.
Line 18: Line 18:
- Native packages are currently built for amd64, but the build is broken intentionally after the packages are built. Change the packaging, such that native packages (suffixed -experimental-dont-complain-if-it-doesnt-work or something similar) are produced, which conflict with the i386 packages.
- Continue to build the i386 based packages for amd64 (update the ia32-* packages as well).
- Follow the upstream milestones for packaging (leading to 2.0.1, 2.0.2, 2.0.3 ...)
- Make a test plan how to compare the two builds and check the uploads according the test plan.
  - basic tests, not specific to amd64 (FormalTestPlans)
  - some whitebox tests, targeting problematic areas, where 64bit issues are known to exist.
- Decide on which version to ship with dapper, based on those test results.		  * Native packages are currently built for amd64, but the build is broken intentionally after the packages are built. Change the packaging, such that native packages (suffixed -experimental-dont-complain-if-it-doesnt-work or something similar) are produced, which conflict with the i386 packages.
 * Continue to build the i386 based packages for amd64 (update the ia32-* packages as well).
 * Follow the upstream milestones for packaging (leading to 2.0.1, 2.0.2, 2.0.3 ...)
 * Make a test plan how to compare the two builds and check the uploads according the test plan.
   * basic tests, not specific to amd64 (FormalTestPlans)
   * some whitebox tests, targeting problematic areas, where 64bit issues are known to exist.
 * Decide on which version to ship with dapper, based on those test results.
Line 28: Line 28:
- Define a date, when the decision for i386/amd64 binaries has to be made (DapperReleaseSchedule).
- Can some sub-tasks be found, which could be subject to a bounty.		  * Define a date, when the decision for i386/amd64 binaries has to be made (DapperReleaseSchedule).
 * Can some sub-tasks be found, which could be subject to a bounty.

Summary

OpenOffice.org currently is built on amd64 using the i386 binaries, because the application is not yet completely ported for 64bit. Evaluation of the current state of the 64bit native build of OOo2 on amd64 is needed. Decide between the 64bit build and the current practice of using the 32bit build on amd64.

Rationale

It's a burden to separately maintain the i386 packages (prepackaged i386 libraries and applications) for amd64. If the application is 64bit clean, a lot of maintainance effort can be saved.

Implementation

  • Native packages are currently built for amd64, but the build is broken intentionally after the packages are built. Change the packaging, such that native packages (suffixed -experimental-dont-complain-if-it-doesnt-work or something similar) are produced, which conflict with the i386 packages.
  • Continue to build the i386 based packages for amd64 (update the ia32-* packages as well).
  • Follow the upstream milestones for packaging (leading to 2.0.1, 2.0.2, 2.0.3 ...)
  • Make a test plan how to compare the two builds and check the uploads according the test plan.

    • basic tests, not specific to amd64 (FormalTestPlans)

    • some whitebox tests, targeting problematic areas, where 64bit issues are known to exist.
  • Decide on which version to ship with dapper, based on those test results.

Outstanding issues

  • Define a date, when the decision for i386/amd64 binaries has to be made (DapperReleaseSchedule).

  • Can some sub-tasks be found, which could be subject to a bounty.

OpenOffice64 (last edited 2008-08-06 16:41:47 by localhost)