LibreOffice Packaging for Oneiric

Registered by Björn Michaelsen on 2011-05-03

General discussion session about all topics related to LibreOffice packaging and goals for Oneiric. Some of these are:
- making LibreOffice packages smaller (considering upstream changes like different packing of themes etc.).
- simplifying the build by forfeiting the split (or rather duplication) of the libreoffice/libreoffice-l10n source packages.
- synchronize human->humanity theme rename for packages and upstream change
- what priorities for upstream changes result from our requirements and how do we communicate those.

Blueprint information

Status:
Complete
Approver:
Martin Pitt
Priority:
High
Drafter:
Björn Michaelsen
Direction:
Approved
Assignee:
Björn Michaelsen
Definition:
Approved
Series goal:
Accepted for oneiric
Implementation:
Implemented
Milestone target:
None
Started by
Björn Michaelsen on 2011-07-18
Completed by
Björn Michaelsen on 2011-10-07

Related branches

Sprints

Whiteboard

Work items for Ubuntu oneiric-alpha-1:
Humanity theme upstream integration: DONE
Start discussion long term plans about theme organization (removing duplicates, sensible icon file names): DONE
Follow up and drive the discussion upstream to migrate to gettext (until July 2011) (moved to https://blueprints.launchpad.net/ubuntu/+spec/desktop-o-libreoffice-communities): DROPPED
Integrate lo-menubar into upstream: DONE

Work items for Ubuntu oneiric-alpha-2:
Get current status of LibreOffice split build (pending OneGit migration, which will change way too much): DROPPED
[dpm] Send an e-mail to the ubuntu-translators list with a heads up on the GSoC project for migration to gettext: DONE
Clarify lo-menubar license for upstream: POSTPONED
LibreOffice 3.4.0 ppa release for Natty and Lucid: DROPPED
Discuss with Chris Gregan and Pete Graner on how to improve QA for LibreOffice: DONE
Get a local ARM build bot setup: POSTPONED

Work items for Ubuntu oneiric-alpha-3:
package LibreOffice 3.3.3 release for Natty SRU: DONE

Work items for ubuntu-11.10-beta-1:
package LibreOffice 3.4.1 for Oneiric: DONE
Change lo-menubar and libreoffice packaging to use compiled code from upstream for 3.4.X and beyond (source code is upsteamed, but lo-menubar has too many open bugs to be MIRed): POSTPONED
package LibreOffice 3.3.3 release for Lucid PPA: DROPPED

Work items for ubuntu-11.10-beta-2 :
LibreOffice 3.4.2 should be released for Oneiric, discussed upstream to be released before Oneiric FF: DONE

Work items for ubuntu-11.10:
LibreOffice 3.4.3 ppa release for Natty: DONE
LibreOffice 3.4.3 Natty backport (postgres sdbc woes): DROPPED
LibreOffice 3.4.3 ppa release for Lucid: POSTPONED
LibreOffice 3.4.3 Natty backport (postgres sdbc woes): DROPPED

Work items:
Implement/manage possible icon reoganization upstream: POSTPONED
Implement possible gettext migration upstream (moved to https://blueprints.launchpad.net/ubuntu/+spec/desktop-o-libreoffice-communities): DROPPED

Session notes:

Current state of LO packaging
  * changed in Natty from OO.org to LO
Natty release feedback
  * bad experience for translators to translate the launchers on a wiki page
    * desktop files are a problematic case, but should be taken upstream soon
    * the QuickLists will probably not be taken upstream soon, but the desktop files will
Packaging problems
  * would be nice to have instructions for packaging extensions
  * more and more packages are getting integrated into LO
  * from the packaging point of view, it would be better to have them packaged separately
Upstreams:
  * Debian - improved collaboration
  * LibreOffice
    * release model differs from OO.o
    * in the Oneiric cycle there will be four releases
Packaging
  * do we want to have every release backported/PPA
  * 3.3.3, 3.4, 3.4.1, 3.4.2 before the feature freeze
  * all versions should be packaged for Oneiric
  * if possible have them backported/SRUd for Natty for testing
  * release to PPA, backport if possible
Smaller packages
  * the biggest package is the core, but it's only binaries
  * the security updates were split from the translations
  * one line of change requires rebuilding all packages, in spite of the fact that only one package has changed, and thus everyone has to download all the packages
  * for translations LO uses its own complete tooling, which has many steps, translating from launchpad would add another step to that
  * Question: would LO as upstream move to Launchpad?
    * it is possible for upstream and Ubuntu translators to collaborate using LO translations and Launchpad
    * a proposal has been made for LO to be converted to gettext - looks like the right way, but needs resources
      * the code would be easy to change
      * the tooling, build system is a bigger problem
Themes
  * human has been renamed to humanity
  * the change should be made upstream
  * themes should be packaged separately
  * right now patching the source is required to change the theme
  * building ZIP file for themes would be the right way to go, these could be updated separately

Update 2011-05-21:
see http://blog.documentfoundation.org/2011/05/13/announcing-a-new-beta-release/

(?)

Work Items

Dependency tree

* Blueprints in grey have been implemented.