Welcome to the Pacman bug tracker. Please search the current bugs and feature requests before filing a new one! Use advanced search and select "Search in Comments".

* Please select the correct category and version.
* Write a descriptive summary, background info, and provide a reproducible test case whenever possible.

FS#1571 - metadata for informational messages

Attached to Project: Pacman
Opened by Dale Blount (dale) - Monday, 04 October 2004, 01:37 GMT
Last edited by Aaron Griffin (phrakture) - Tuesday, 08 September 2009, 22:49 GMT
Task Type Feature Request
Status Closed
Assigned To Aaron Griffin (phrakture)
Architecture not specified
Severity Low
Priority Normal
Reported Version 0.7 Wombat
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 3
Private No


support for:

message=("A new profile is needed.\nPlease create a new profile")

or something like that in PKGBUILDS would be very useful for packages w/o install files that need informational messages.
This task depends upon

Closed by  Aaron Griffin (phrakture)
Tuesday, 08 September 2009, 22:49 GMT
Reason for closing:  No response
Additional comments about closing:  Open for 4.5 years with no action - reopen if needed
Comment by Roman Kyrylych (Romashka) - Sunday, 15 October 2006, 11:54 GMT
It was discussed in pacman-dev ML recently. Proof-of-concept patch was made by VMiklos.
Comment by Roman Kyrylych (Romashka) - Wednesday, 28 February 2007, 23:22 GMT
Note about original FR's Details:
This is supposed to be done in .install file, not in PKGBUILD.
Comment by Dan McGee (toofishes) - Monday, 05 March 2007, 01:42 GMT
Two notes:
1) This is definitely intended for the PKGBUILD- the whole point is to get rid of an install file that contains only messages.
2) We're going to hold off until after pacman 3.0.0 release for this. I can almost guarantee this is a top FR for pacman 3.1 though.
Comment by Aaron Griffin (phrakture) - Monday, 05 March 2007, 04:20 GMT
As I posted on the mailing list:
It would be more beneficial to define a whole set of functions in some external file, as install files are just bash scripts.

For instance: /usr/lib/archlinux/functions
We can source this file manually before calling something like post_upgrade.

This allows us to kill two birds with one stone:
* Unify message scripts w.r.t. makepkg/rc.d scripts/etc
* Make something like this easier, and have the same output as the rest of the system
Comment by Bjørn Kiær (BLK) - Thursday, 28 June 2007, 18:20 GMT
I don't agree that this should be done with predefined functions in the install script. As Dan McGee says, the whole point of the request is to remove the necessity of install scripts simply to display post-install messages.

There would be other benefits to implementing it as a variable in the PKGBUILD:
- Pacman could show all such messages together at the end of the install run, thus preventing important messages from getting buried in all the "Upgrading foobar ... done" noise during a large upgrade/installation (such as after a new installation).
- Pacman could keep a backlog of the most recent such messages. If something doesn't work, the user could then go back in the log file to see if he has overlooked an important message.
- It seems a little cleaner to me :)

Another thing that _might_ be a good idea is the ability to mark the severity of messages; pacman could then distinguish them by, for instance, colour-coding. It is a little more important that the user sees "/boot/initrd has been moved to /boot/kernel.img. Update grub, or your system won't boot!" than "Foo only supports mp3 out of the box; you might want to install extra codecs" ...