[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: dkms needs a pre-depends entry (Policy 3.5)

On Tue, Jul 20, 2010 at 14:36:04 (CEST), Bernd Zeimetz wrote:

> On 07/18/2010 02:35 AM, Ben Hutchings wrote:
>> On Sat, 2010-07-17 at 17:03 +0000, Philipp Kern wrote:
>>> On 2010-07-17, Ben Hutchings <ben@decadent.org.uk> wrote:
>>>> The postinst for nvidia-kernel-dkms invokes dkms, which invokes
>>>> lsb_release.  lsb_release hasn't been configured at this point so its
>>>> module has not been installed for the default Python version.  But I
>>>> agree that there is no need for Pre-Depends.
>>> Quoting `/usr/share/doc/python-support/README.gz':
>>> | What this means is, if you need a namespace package or depend on a 
>>> | package that needs it, *and* that you need to use it during the 
>>> | postinst phase (e.g. for a daemon), you will have to add the following 
>>> | command in the postinst before starting your daemon:
>>> |         update-python-modules -p
>> Then this is a bug in python-support.  If A depends on B, then A should
>> not need to know whether B depends on C (which may well change over
>> tme).
> Lets remove all triggers from dpkg then. Updating the Python modules for every
> new module package is a big waste of time, running it as a trigger results into
> the described problem in a few rare cases. What do you prefer?

what about having dkms' postinst executing the trigger to update Python
modules in this case?

> Also adding update-python-modules -p to a postinst script does not hurt, even
> when dependencies change.

I guess this is exactly what the trigger does, right?

Reinhard Tartler, KeyID 945348A4

Reply to: