Hello again, Guillem!
On Wed, Sep 11, 2019 at 10:24 PM Matt Zagrabelny wrote:
>
> One could expose any/all of the following (if available):
>
> DPKG_HOOK_PACKAGE_FILENAME=/path/to/some.deb
> DPKG_HOOK_PACKAGE_NAME=foo
> DPKG_HOOK_PACKAGE_FD=12
>
>
>> Also these would need to get multiple entries
Hey Guillem!
Thanks for the reply.
On Wed, Sep 11, 2019 at 9:14 PM Guillem Jover wrote:
> Hi!
>
> On Tue, 2019-09-10 at 16:39:22 -0500, Matt Zagrabelny wrote:
> > Package: dpkg
> > Version: 1.19.7
> > Severity: wishlist
>
> > I would like to access other meta data (besides DPKG_HOOK_ACTION) whe
Hi!
On Tue, 2019-09-10 at 16:39:22 -0500, Matt Zagrabelny wrote:
> Package: dpkg
> Version: 1.19.7
> Severity: wishlist
> I would like to access other meta data (besides DPKG_HOOK_ACTION) when
> running various pre/post-invoke commands.
>
> Would you consider exposing:
>
> DPKG_HOOK_PACKAGE_NAM
Package: dpkg
Version: 1.19.7
Severity: wishlist
Greetings,
I would like to access other meta data (besides DPKG_HOOK_ACTION) when running
various pre/post-invoke commands.
Would you consider exposing:
DPKG_HOOK_PACKAGE_NAME
That contains the package name?
Thank you!
-m
-- Package-specific
4 matches
Mail list logo