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

Re: Draft spec for new dpkg "triggers" feature

* Ian Jackson:

> Florian Weimer writes ("Re: Draft spec for new dpkg "triggers" feature"):
>> [Ian Jackson:]
>> > To restore a package in state `triggered' to `installed', dpkg will
>> > run the postinst script:
>> >    postinst triggered "<trigger-name> <trigger-name> ..."
>> Is this completely POSIX-conforming if there are many triggers?
> You seem to be worried about command line argument length limits,
> although I'm forced to read between the lines.  It would be more
> helpful if you were more explicit.

Oops.  I had my mind elsewhere.

> 2. That's irrelevant.  dpkg does not need to run on every
> POSIX-confirming system.

I'm more concerned by people who insist on running maintainer scripts
with castrated, yet POSIX-conforming shells.

Personally, I wouldn't object to something in Policy which mandates
that /bin/sh must support the system's ARG_MAX value, and must not
impose a different limit.

> (CC to debian-devel and debian-policy removed.  Did you deliberately
> fail to honour my Reply-To header or did something strip it out
> somewhere?)

Seems to be the fault of my Gnus configuration.  Sorry.

Reply to: