Re: Status of recent and upcoming changes
Graham Wilson writes:
> On Sun, Jun 11, 2006 at 05:50:06PM +0200, Matthias Klose wrote:
> > - Some infrastructure was implemented to remove all hardcoded
> > information about versions in the packaging scripts, so that
> > sourceless package rebuilds (binary NMUs) are enough to update
> > a package for new/removed/default python versions.
>
> Is it possible to elaborate on this point more in the final mail, or at
> least provide a link so that maintainers can know how to use this new
> funtionality?
I'll try to add something. Currently this is
- collapsing the pythonX.Y-foo packages into python-foo
- use of python-all / python-all-dev as build dependency
- deriving version numbers from a script (now pyversions)
in python (>= 2.4) tomorrow in experimental
- use variables in debian/control and let the debhelper
scripts expand these variables.
We can surely give the rationale for doing this in the policy, maybe
pointing out some examples. Currently you can find these at
http://wiki.debian.org/DebianPythonFAQ and/or
http://python-modules.alioth.debian.org/python-central_howto.txt
We are somewhat lost, if the packaging uses fixed python version
strings in the debian/*install files. Maybe add a target to generate
these/update files at the build.
Matthias
Reply to: