Re: Debhelper 7, Python package, multiple binary packages
On Sun, Oct 18, 2009 at 10:31:02AM +1100, Ben Finney wrote:
> Thanks, ‘backintime’ does indeed meet these criteria.
>
> The ‘debian/rules’ file is doing some things that I'm confused about:
>
> =====
> override_dh_auto_clean:
> rm -rf locale common/po/*.mo
> find $(CURDIR) -name "*\.py[co]" -delete
> rm -f common/Makefile gnome/Makefile kde4/Makefile
> =====
>
> Is it necessary to remove ‘*.py[co]’ files? Wouldn't it be better to
> call ‘dh_auto_clean’ to do this?
They must be removed to keep the .diff.gz clean, but upstream doesn't ship
makefiles with clean targets, so dh_auto_clean can't handle it. dh_clean
doesn't know about pre-compiled python files.
> =====
> override_dh_pysupport:
> dh_pysupport /usr/share/backintime/
> =====
>
> Is this necessary? Why can't ‘dh_pysupport’ do this without being
> overridden here?
dh_pysupport:
If your package installs private python modules in non-standard
directories, you can make dh_pysupport check those directories by
passing their names on the command line. By default, it will check
/usr/lib/$PACKAGE, /usr/share/$PACKAGE, /usr/lib/games/$PACKAGE and
/usr/share/games/$PACKAGE
In my case, the package names are backintime-* but the install directory is
always /usr/share/backintime, so dh_pysupport needs a little hint here.
--
Jonathan Wiltshire
1024D: 0xDB800B52 / 4216 F01F DCA9 21AC F3D3 A903 CA6B EA3E DB80 0B52
4096R: 0xD3524C51 / 0A55 B7C5 1223 3942 86EC 74C3 5394 479D D352 4C51
Reply to: