[pacman-dev] [PATCH 0/2][WIP][RFC] hooks

[Connor Behan]

On 10/04/14 04:59 PM, Andrew Gregory wrote:
> Because this is a rather minimal implementation, my primary concern at this
> point is making sure that no essential features are missing and that I don't
> commit us to anything that would make implementing the remaining features more
> difficult later.
I have long looked forward to hooks, but the use cases I have in mind
might be unreasonable. Could the framework be written to expose certain
details about the package (file list, dependencies, etc) to the Exec =
script? Hooks for packages that are already installed, can determine
this with pacman -Q. But it might be nice to have a hook that changes
the indentation of any newly installed *.py say.

A crazier idea is "changing dependencies" during installation instead of
using -d. One complaint about Arch is e.g. python2-matplotlib
"depending" on python2-pyqt4 when really it can be configured to use gtk
instead. If there was something like When = PostExtract, a script could
edit the .PKGINFO file and switch qt to gtk. However, it would probably
be stupid to make pacman extract all the .PKGINFO files before resolving
dependencies.

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 555 bytes
Desc: OpenPGP digital signature
URL: <http://mailman.archlinux.org/pipermail/pacman-dev/attachments/20140411/14b72cfd/attachment.asc>