[pacman-dev] add message() function call for use in *.install/.PKGINFO files
roman.kyrylych at gmail.com
Sun May 28 17:16:31 EDT 2006
I think all info messages should just be passed to front-end and it is
front-end's job how and when to show them. So there should be speciall
function for use in .install files instead of current echo stuff.
As for indicating some progress for user: when there is some lengthy
operation in .install it should be prefixed and postfixed with calls
to special functions so user will see a message from front end like
"Generating the initial ramdisk... Please wait." and then "Done" (or
green checkmark in GUI :-D ).
2006/5/28, VMiklos <vmiklos at frugalware.org>:
> On Fri, May 26, 2006 at 04:25:39PM +0300, ????? ??????? <roman.kyrylych at gmail.com> wrote:
> > README can be good if it will be displayed automatically after package install.
> > This is a job of any libalpm front-end anyway.
> > It should be treated like .PKGINFO or .FILELIST files - I mean these
> > README files should be used for front-end work only, and not installed
> > anywhere.
> .PKGINFO and such files are handled in libalpm
> btw sure, this is up to the frontend, shile executing such files are
> dony by libalpm. that's why the post_instal scriptlet must be silent and
> shouldn't output any essential info
> > There is another thing - some packages generates some progress info
> > during install (like ">>> Genreating initial ramdisk... done").
> > - this should be addressed too, maybe with something like
> > status_message() function, or something else.
> the behaviour is bad, but in this case just a gui user should wait (like
> while running ldconfig) but he/she doesn't miss any essential info
> udv / greetings,
> Developer of Frugalware Linux, to make things frugal - http://frugalware.org
> pacman-dev mailing list
> pacman-dev at archlinux.org
More information about the pacman-dev