Hi!
On Wed, 2012-04-04 at 03:39:54 -0700, Josh Triplett wrote:
On Wed, Apr 04, 2012 at 11:43:48AM +0200, Raphael Hertzog wrote:
On Wed, 04 Apr 2012, Josh Triplett wrote:
In some way we already do:
$ sudo dpkg-trigger --no-await /usr/local/man
$ sudo dpkg --configure -a
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
On Wed, Apr 04, 2012 at 08:09:31AM +0200, Raphael Hertzog wrote:
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).
True. I just want to make sure
On Wed, 04 Apr 2012, Josh Triplett wrote:
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.
I meant there's
On Wed, Apr 04, 2012 at 11:43:48AM +0200, Raphael Hertzog wrote:
On Wed, 04 Apr 2012, Josh Triplett wrote:
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
Package: dpkg
Version: 1.16.2
Severity: wishlist
Many packages provide support for locally installed software in
/usr/local. For instance, man-db supports locally installed manpages,
scripting languages like Python support locally installed modules,
fontconfig supports locally installed fonts,
6 matches
Mail list logo
