Daniel Jacobowitz writes (Re: Bug#447609: ldconfig triggerisation):
On Mon, Oct 22, 2007 at 04:07:05PM +0100, Ian Jackson wrote:
[assumptions]
Note that this is usually true but not always; it may be true
enough for our purposes but I want to set the record straight.
Thanks.
The only
On Tue, Oct 23, 2007 at 11:11:37AM +0100, Ian Jackson wrote:
The only failure case I can think of would be a package which places
libraries in the multi-arch directories, which Debian locates using a
file in /etc/ld.so.conf.d, and the same or another package which runs
a newly installed
On Tue, Oct 23, 2007 at 11:11:37AM +0100, Ian Jackson wrote:
Unfortunately because of the way /lib and particularly /usr/lib are
dumping grounds, file triggers wouldn't work properly. A file trigger
is activated by packages' files whose pathnames start with the name of
the trigger. So the
Daniel Jacobowitz writes (Re: Bug#447609: ldconfig triggerisation):
On Tue, Oct 23, 2007 at 11:11:37AM +0100, Ian Jackson wrote:
The only failure case I can think of would be a package which places
libraries in the multi-arch directories, which Debian locates using a
file in /etc
Clint Adams writes (Re: Bug#447609: ldconfig triggerisation):
Why not just move to use of dpkg-trigger piecemeal in each postinst?
That would involve no more invocations of ldconfig than we are already
enduring.
Because that would involve a great deal of additional dependency
complexity: each
Source: glibc
Version: 2.6.1-6
Severity: wishlist
Tags: patch
The attached patch triggerises the invocation of ldconfig by package
maintainer scripts.
By `triggerises' I mean that the patch arranges for ldconfig
invocations by maintainer scripts to call dpkg-trigger instead of
ldconfig.
On Mon, Oct 22, 2007 at 04:07:05PM +0100, Ian Jackson wrote:
The understanding on which we base this approach is that after library
installation (which is when ldconfig is used in maintainer scripts) it
is always safe to defer the execution of ldconfig. Ie, that after a
new library has been
Couldn't file triggers be used, so ldconfig is triggered after any
package installs a library file? That's much more how I expected
triggers to be used, rather than needing an ugly ldconfig wrapper. I
think it also addresses drow's point about libraries in nonstandard
locations, since those
On Mon, Oct 22, 2007 at 06:28:23PM +, Joey Hess wrote:
Couldn't file triggers be used, so ldconfig is triggered after any
package installs a library file? That's much more how I expected
triggers to be used, rather than needing an ugly ldconfig wrapper. I
think it also addresses drow's
9 matches
Mail list logo
