Arch Linux

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#31874 - [pacman] better delivery of messages when installing/upgrading/removing a package

Attached to Project: Arch Linux
Opened by Max Pray (synthead) - Wednesday, 10 October 2012, 01:34 GMT
Last edited by Dave Reisner (falconindy) - Saturday, 20 October 2012, 16:59 GMT
Task Type Feature Request
Category Packages: Core
Status Closed
Assigned To Dan McGee (toofishes)
Dave Reisner (falconindy)
Architecture All
Severity Very Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Pacman doesn't have an internal way of delivering a message after installing a package. For a package to do this, it needs to be echo'd with an .install file. Kind of a hack since .install files are supposed to run necessary commands after an install, not be loud and do nothing. Also, this means that every notification looks different, which is kinda sloppy as far as aesthetics go. optdepends have this same problem, too.

It would be nice if there was some sort of formatting for the text in some way. For example, if the message was to be stored in a file, paragraphs of text would not be separated by newlines: it'd be word-wrapped on display. And perhaps instead of having an important three-line message blow by discreetly (this happens all the time), it would simply install without displaying anything and deliver the messages at the end. Something like "There are 5 unread messages from pacman." and the user can read the messages at any time by a command.
This task depends upon

Closed by  Dave Reisner (falconindy)
Saturday, 20 October 2012, 16:59 GMT
Reason for closing:  Not a bug
Additional comments about closing:  This is all logged to /var/log/pacman.log already.
Comment by Karol Błażewicz (karol) - Wednesday, 10 October 2012, 02:04 GMT
See  FS#12861  for 'deliver the messages at the end' part.
Comment by Alexander F. Rødseth (xyproto) - Tuesday, 16 October 2012, 23:14 GMT
Perhaps this could be solved by involving libnotify somehow? In any case, it's unlikely that it would be implemented directly in pacman, judging from earlier responses.
Comment by Dave Reisner (falconindy) - Wednesday, 17 October 2012, 15:18 GMT
We expect that users are capable of reading pacman's output. If you missed it or want to re-read, it's logged for you in /var/log/pacman.log.

Loading...