On lun, 2008-04-14 at 00:52 +0100, Serafeim Zanikolas wrote:
> I'm packaging a set of pure python modules (ITP #473039), which are part of a
> single module and share a few common files. So in /usr/share/python-support/
> we have:
>
> python-nodebox-web/nodebox_web/web/ (files required by all other modules)
> python-nodebox-web/nodebox_web/web/wikipedia
> python-nodebox-web/nodebox_web/web/yahoo
> [..]
>
> where the non -common ones are independent of each other.
>
> These are packaged as
>
> python-nodebox-web-common
> python-nodebox-web-wikipedia
> python-nodebox-web-yahoo
> [..] (where the latter depend on -common)
This is where things are wrong. There should be one directory
in /usr/share/python-support for each package, and not a single
directory for the three packages.
> The way I deal with this is having a .prerm script for every non -common
> binary that wipes the whole directory (update-python-modules -c), and then
> recreates the dir in a .postrm script (update-python-modules). This works but
> requires a .prerm and .postrm scripts for every binary. (I can't use a single
> pair of scripts for all, because -common must only call update-python-modules
> -c. (Or I could if I could tell from within a single prerm script which
> package the script is ran for.)
I don’t understand why you are trying to do something so incredibly
complicated. Instead, you should:
1. remove any customization that places stuff
in /usr/share/python-support directly;
2. remove all the useless hacks you added as a result of this;
3. let dh_pysupport do the job of moving the right files to the
right directories and add the proper prerm/postinst snippets.
Cheers,
--
.''`.
: :' : We are debian.org. Lower your prices, surrender your code.
`. `' We will add your hardware and software distinctiveness to
`- our own. Resistance is futile.
Attachment:
signature.asc
Description: Ceci est une partie de message =?ISO-8859-1?Q?num=E9riquement?= =?ISO-8859-1?Q?_sign=E9e?=