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 Tue, Apr 03, 2012 at 04:23:17PM +, Kamble, Nitin A wrote:
Thanks for catching the typo. We use x86_64-linux-gnux32
Thanks for the quick reply.
On IRC Steve Langasek pointed out that some part of the difference
resides in the architecture-kernel part. You cannot run a x32 binary on
an
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
Hi Helmut,
Helmut Grohne wrote:
On IRC Steve Langasek pointed out that some part of the difference
resides in the architecture-kernel part. You cannot run a x32 binary on
an arbitrary x86_64 linux kernel
Yes, that's true. The kernel needs CONFIG_X86_X32_ABI set.
There are all sorts of
On Wed, Apr 04, 2012 at 08:53:45AM +0200, Helmut Grohne wrote:
On Tue, Apr 03, 2012 at 04:23:17PM +, Kamble, Nitin A wrote:
Thanks for catching the typo. We use x86_64-linux-gnux32
Thanks for the quick reply.
On IRC Steve Langasek pointed out that some part of the difference
resides
7 matches
Mail list logo
