[chandler-dev] Building Chandler 1.0.3+ on Ubuntu 9.04 (Jaunty)
matt at slyy.net
Thu Jun 25 00:41:49 PDT 2009
> 1) Are the python --> python2.6 changes required (or recommended)? I
> ask because we use that control file to build on Hardy, Intrepid and
> Jaunty, and so there would have to be a branch in svn if the
> dependencies were different on the 3 platforms.
Good question. You said in an earlier email that you couldn't get the
python2.5-built PyLucene to work with the python2.6 environment in
Jaunty. So I assumed that by building PyLucene in my package in the
python2.6 environment, it would not work with 2.5. I don't know if this
is a good assumption or not.
Since PyLucene is built as part of the package with the given debian/
directory, the control file should list the dependencies for PyLucene,
also. I would imagine that in a proper packaging scheme, PyLucene would
be in its own library package, it would have its dependencies, and the
chandler package would then be python2.x agnostic. At the very least
though, I do believe that the dependency should be python (<< 3.0). The
Python folks have said that 2.x code won't work as-is in 3.0.
> 2) I'm not an expert on packaging, so I'm not sure if the fakeroot and
> svn-buildpackage dependencies are required. They are needed for
> creating .debs, but probably there are other ways of building/
> extracting packages?
This is the first package I've built, and I'm just starting to read up
on how to create packages and the Debian/Ubuntu policy. So I'm far from
More information about the chandler-dev