[pacman-dev] add message() function call for use in *.install/.PKGINFO files

[Jason Chu]

On Wed, 31 May 2006 10:13:55 -0700
Judd Vinet <jvinet at zeroflux.org> wrote:

> On Mon, May 29, 2006 at 03:03:57AM +0200, VMiklos wrote:
> > > Could there be some standard pipe defined to communicate between
> > > .install script and front-end?
> > 
> > that's what i've proposed :)
> > 
> > 2 "commands":
> > 1. START <string>
> > 2. DONE <exit code>
> > 
> > comments? Judd, Aurel? what do you think about this?
> 
> It starts to sound a little convoluted, but I can't think of a better
> way.
> 
> If each scriptlet implicitly included a helper bash script that
> included a task_message() function, that function could relay the
> strings through a fifo that libalpm listened to on the other side.
> libalpm could then feed the strings back to the frontend.
> 
> 
> - J

Wouldn't it be better to have pacman execute a script that sets
up things like task_message and then executes the install script in the
same environment?

That way you could upgrade the task_message() function later, etc.

Jason
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 191 bytes
Desc: not available
URL: <http://archlinux.org/pipermail/pacman-dev/attachments/20060531/a8b100e3/attachment.pgp>