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
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
|
Details
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
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
This is supposed to be done in .install file, not in PKGBUILD.
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.
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
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" ...