[pacman-dev] [RFC] alpmtrigger: triggering events after all packages got installed...

Xavier shiningxc at gmail.com
Sat Sep 12 08:34:24 EDT 2009


On Sat, Sep 12, 2009 at 2:19 PM, Marc - A. Dahlhaus <mad at wol.de> wrote:
>
> I actually have read the text on the wiki and i know that there is a
> transaction hook mentioned there.
>
> Did you think about the case where a common task could be wanted if there
> isn't any filename based rule that could fire it up?
>
> An example could be that a package adds some functionality that is an
> optional dependency for a job. If the dependency is not installed on the
> jobs first execution than some thinks are not done. If the optional
> dependency get installed at a later point it could ask for the trigger of
> the dependency and activate the missing things.
>
> I argue that they should be differently handled because of situation where
> the "file X got installed so we need to start Y" will not work.
>

I read your message like 10 times, and I am not sure I understand what
you are saying.
Maybe if you could provide a more concrete example, it would be
clearer for everyone :)


More information about the pacman-dev mailing list