[pacman-dev] Display messages from install scripts after all packages have been installed
Hi, I'm sure this question/request must have been asked before, however I wasn't able to find anything by searching for it. Apologies in advance if this is the wrong place to post. Install scripts bundled with packages sometimes print *important* changes/warnings when a package is installed or upgraded. These warnings are clearly visible when installing a single package, but tend to get lost when installing lots of packages because the install script hooks run right after each package is installed. I'm wondering if there is someway to delay the printing of these messages/warnings until all packages have been installed. Could/should a new hook be added that could run after all packages have been installed? Does anyone besides me even care? Thanks, Jashandeep
On Wed, Dec 23, 2015 at 7:14 AM, Jashandeep Sohi
Install scripts bundled with packages sometimes print *important* changes/warnings when a package is installed or upgraded. These warnings are clearly visible when installing a single package, but tend to get lost when installing lots of packages because the install script hooks run right after each package is installed.
I open a fresh terminal, run 'pacman -Syu' and use the scrollback buffer to have a look at the output.
On 23/12/15 16:14, Jashandeep Sohi wrote:
Hi,
I'm sure this question/request must have been asked before, however I wasn't able to find anything by searching for it. Apologies in advance if this is the wrong place to post.
Install scripts bundled with packages sometimes print *important* changes/warnings when a package is installed or upgraded. These warnings are clearly visible when installing a single package, but tend to get lost when installing lots of packages because the install script hooks run right after each package is installed.
I'm wondering if there is someway to delay the printing of these messages/warnings until all packages have been installed. Could/should a new hook be added that could run after all packages have been installed? Does anyone besides me even care?
It has been asked before but rejected. All scriptlet output is recorded in the pacman log if you can not scroll back to it. A
Yes, I'm aware I could scroll back, look at the log or pipe the output
to a temp file for later analysis, but this feels like a unnecessary
extra step to perform after each update considering these messages are
rare and I'd expect nothing out-of-the-ordinary most of the time.
But if this has been asked before, there is little point in rehashing
old arguments. Could you point me towards the discussion so I can
understand why it was rejected?
Thanks,
Jashandeep
On Wed, Dec 23, 2015 at 4:30 PM, Allan McRae
On 23/12/15 16:14, Jashandeep Sohi wrote:
Hi,
I'm sure this question/request must have been asked before, however I wasn't able to find anything by searching for it. Apologies in advance if this is the wrong place to post.
Install scripts bundled with packages sometimes print *important* changes/warnings when a package is installed or upgraded. These warnings are clearly visible when installing a single package, but tend to get lost when installing lots of packages because the install script hooks run right after each package is installed.
I'm wondering if there is someway to delay the printing of these messages/warnings until all packages have been installed. Could/should a new hook be added that could run after all packages have been installed? Does anyone besides me even care?
It has been asked before but rejected. All scriptlet output is recorded in the pacman log if you can not scroll back to it.
A
On 24/12/15 16:04, Jashandeep Sohi wrote:
Yes, I'm aware I could scroll back, look at the log or pipe the output to a temp file for later analysis, but this feels like a unnecessary extra step to perform after each update considering these messages are rare and I'd expect nothing out-of-the-ordinary most of the time.
But if this has been asked before, there is little point in rehashing old arguments. Could you point me towards the discussion so I can understand why it was rejected?
Thanks, Jashandeep
On 12/22/15 at 10:14pm, Jashandeep Sohi wrote:
Hi,
I'm sure this question/request must have been asked before, however I wasn't able to find anything by searching for it. Apologies in advance if this is the wrong place to post.
Install scripts bundled with packages sometimes print *important* changes/warnings when a package is installed or upgraded. These warnings are clearly visible when installing a single package, but tend to get lost when installing lots of packages because the install script hooks run right after each package is installed.
I'm wondering if there is someway to delay the printing of these messages/warnings until all packages have been installed. Could/should a new hook be added that could run after all packages have been installed? Does anyone besides me even care?
Thanks, Jashandeep
Not every feature needs to be integrated directly into pacman. Everything you want is in the log, feel free to use a wrapper to parse it out yourself: #!/bin/bash logfile='/var/log/pacman.log' lines="$(wc --lines "$logfile" | cut --fields=1 --delimiter=' ')" (( lines++ )) pacman "$@" tail --lines=+$lines "$logfile" | paclog --caller='ALPM-SCRIPTLET' --warnings # or naive parsing for those without paclog #tail --lines=+$lines "$logfile" | grep --extended-regexp '\[ALPM-SCRIPTLET\]|error:|warning:' apg
participants (4)
-
Allan McRae
-
Andrew Gregory
-
Jashandeep Sohi
-
Karol Blazewicz