I think triggerer packages information should be exposed to
triggers. In example we may want to have an index of information
about installed packages in a form better suitable for lookup than
files in info. I.e. a trie for file paths mapping them to packages.
But this DB has to be updated. We can either update it fully on each installation, which is long, or selectively only for the packages
installed. To do it we need the info about the packages installed
be passed to triggers and hooks.
|Location:||Huddersfield, West Yorkshire, UK|
|Nodes:||8 (0 / 8)|