Hi! On Mon, 2020-07-27 at 00:15:12 +0300, KOLANICH wrote: > 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.
Hmm, do you mean you want to have a parallel database that pretty much matches the one in dpkg, and you want to add a trigger on say «/» to update that database on each package installation? Or am I misunderstanding? If the former, that just seems wrong on so many levels. :) While the doc/triggers.txt spec mentions a possibility for this in the DISCUSSION section, we have never really needed it, and its need does seem dubious to me TBH. Thanks, Guillem