r14 - 28 Nov 2007 - 10:05:11 - HeikkiToivonenYou are here: OSAF >  Projects Web  >  DesktopZeroDotSevenRelease > UbuntuHardyHeronChandler

Getting Chandler to Ubuntu Hardy Heron Repositories

Ubuntu is planning the next Long Term Support (LTS) release, code name Hardy Heron, scheduled in April 2008. Release schedule.

This page tracks the planning and tasks needed to get Chandler into the official Ubuntu Hardy Heron repositories, so that users will be able to do a simple apt-get install chandler to install Chandler on their Ubuntu system. The Chandler tracking bug is Bug:11054.

To do this, we need to get all of the dependencies into the repositories as well. We will also need to get our OSAF-specific patches integrated into the Ubuntu versions of the packages. We should also do some Debian/Ubuntu specific customizations.

NOTE: A very important requirement for this to work is that we must not add a dependency to something that will not be able to make it into the Ubuntu repositories in time. So probably no Python 2.6 dependencies etc.

Package Debian (unstable) Ubuntu (Gutsy) Chandler Notes
swig 1.3.31 1.3.31 1.3.29 optional patches Need wxPython patches if you want to make changes to wxPython
db 4.6 4.6 4.6 Need chandlerdb patches, but Andi says he could work around if he had to
icu 3.6 3.6 3.6
openssl 0.9.8 0.9.8 0.9.8
readline 5.2 5.2 5.2 optional
python 2.5.1 2.5.1 2.5.1 Need patches for restart?
bzip2 1.0.3 1.0.4 1.0.3 optional upgrade
zlib yes yes yes
setuptools 0.6c6 0.6c6 0.6c6
epydoc 3.0beta1 3.0beta1 3.0beta1 optional
PyLucene no no 2.2.0 This includes dependency to some java package Bug:11222
PyICU no no 0.6-78 Bug:11223
zopeinterface 3.3.1 3.3.1 3.3.0b2-r71371 optional upgrade
twisted 2.5.0 2.5.0 2.4+patches Need patches(?) bear: don't think so but they may not have recent version
vobject 0.4.8 0.4.8 0.4.8-r186 Need latest
dateutil 1.1 1.1 1.1 Need patches
m2crypto 0.18.2 0.17 0.18.2 Need latest
zanshin no no r169 Bug:11225
eggtranslations no no 1.0-r10
pylint yes yes yes optional Includes dependencies to logilab-astng and logilab-common
parsedatetime no no 0.8.4 Bug:11226
configobj 4.4.0 4.4.0 4.3.2 optional upgrade
docutils 0.4 0.4 0.4 Need patch bear submitted to Python
wxPython 2.6.3.2.1.5 2.8.4 custom Need patches, includes dependencies to wxWidgets etc.
chandlerdb no no 0.7-25
feedparser 4.1 4.1 4.1 optional From feeds plugin
amazon ? ? ? optional From Amazon plugin
flickr ? ? ? optional From Flickr plugin
EXIF ? ?   optional From Flickr plugin
killableprocess no no ? optional From tools/
createPot.py ? ? ? optional From tools/
py2depgraph.py
depgraph2dot.py
? ? ? optional From tools/
chandler no no no Would contain chandler/ and parts of internal/launchers and internal/installers

Cross-Platform Changes Needed

Need to streamline plugins support so that both system wide and user-specific plugins are supported. Administrator needs to be able to install plugins into chandler/plugins, for example, and users need to be able to install into profileDir/plugins, for example. When Chandler launches, it should load plugins from both locations. Not sure which location should win in case of conflicting plugins.

Andi said on IRC:

  • even the path to chandler.prefs can be overridden with a command line flag
  • an installer could hence set a command line flag for a system-wide installation that gets a chandler.prefs per user
  • where all the other defaults that need to be overridden can be

Debian/Ubuntu Customizations

Package Debian (unstable) Ubuntu (Gutsy) Chandler Notes
ca-certificates yes yes custom Rework certstore code to work with CA certificates shipped by Debian/Ubuntu. Chandler should scan ca-certificates certificates on each launch to update Certificate items. Permanently trust server certificate should be changed to make it clear these are stored in chandler, not system wide. Should provide support for migrating certificates (EIM). ca-certificates does not include latest Mozilla certificates, meaning Hub certificate is not known, filed Debian bug 447062.

Ubuntu Packages

Ubuntu Packaging Guide.

https://wiki.ubuntu.com/Spec/PackagingGuideMerge

https://launchpad.net/~chandler-project

Personal Package Archives: https://launchpad.net/ubuntu/+ppas

Debian Packages

One way to get packages into Ubuntu is to get the package into Debian. It seems like most (all?) Debian packages "automatically" make their way into Ubuntu.

If Debian already packages your module, but you have released a new version of your package recently, and Debian has not yet picked up your version (search packages in any distributions), you should file a bug to get Debian to upgrade their package.

You could also file a request to package (RFP) if the module is not yet packaged by Debian.

If nothing else helps, the debian developers corner seems to have all the info needed on how to become a package maintainer:

  • http://www.us.debian.org/devel/
Edit | WYSIWYG | Attach | Printable | Raw View | Backlinks: Web, All Webs | History: r14 < r13 < r12 < r11 < r10 | More topic actions
 
Open Source Applications Foundation
Except where otherwise noted, this site and its content are licensed by OSAF under an Creative Commons License, Attribution Only 3.0.
See list of page contributors for attributions.