On Tue, 03 Apr 2012, Josh Triplett wrote: > As a more optimal solution, packages could register file triggers on > appropriate paths in /usr/local
Some packages already do (man-db for example). > and dpkg could provide a means for an > administrator to manually trigger those triggers after running "make > install" or similar. In some way we already do: $ sudo dpkg-trigger --no-await /usr/local/man $ sudo dpkg --configure -a Processing triggers for man-db ... But there's easy way to find out all the file triggers that match /usr/local/something. > This way, rather than the administrator needing to manually run mandb, > ldconfig, fc-cache, and various other things, they could run a single > command to update all interested packages. I'm not sure that this command should be part of dpkg. But it seems reasonable to improve dpkg so that such a tool can be written on top of dpkg. Cheers, -- Raphaël Hertzog ◈ Debian Developer Pre-order a copy of the Debian Administrator's Handbook and help liberate it: http://debian-handbook.info/liberation/ -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
