On Tue, Sep 04, 2001 at 08:53:20PM -0400, Steve M. Robbins wrote: > --- policy.sgml.orig Sun Sep 2 22:50:21 2001 > +++ policy.sgml Tue Sep 4 20:50:04 2001 > @@ -3714,18 +3714,8 @@ > must call <prgn>ldconfig</prgn> in its <prgn>postinst</prgn> > script if the first argument is <tt>configure</tt> and should > call it in the <prgn>postrm</prgn> script if the first > - argument is <tt>remove</tt>. > - </p> > - > - <p> > - However, <prgn>postrm</prgn> and <prgn>preinst</prgn> scripts > - <em>must not</em> call <prgn>ldconfig</prgn> in the case where > - the package is being upgraded (see <ref id="unpackphase"> for > - details), as <prgn>ldconfig</prgn> will see the temporary > - names that <prgn>dpkg</prgn> uses for the files while it is > - installing them and will make the shared library links point > - to them, just before <prgn>dpkg</prgn> continues the > - installation and renames the temporary files! > + argument is <tt>remove</tt>. Apart from these two circumstances, > + the maintainer scripts must not call <prgn>ldconfig</prgn>. > </p> > > <sect>
This seems like the most sensible approach to me. I would second this. -- Chris Waters | Pneumonoultra- osis is too long [EMAIL PROTECTED] | microscopicsilico- to fit into a single or [EMAIL PROTECTED] | volcaniconi- standalone haiku
