Hi all, > I wonder if this can properly be achieved through dpkg triggers.
Yes it can ;-) > That would be based on a specific dpkg trigger (e.g. xindy-buildmem). No, it would be a clisp trigger. clisp would look for some place where new files are dropped, and rebuilds mems. If a new version of clisp is uploaded then all mems are rebuilt. I have done that for tex-common and all the tex-formats: - tex-common shows interest (dpkg parlance) in a certain directory - packages shipping tex formats drop a certain file there - if that occurred, triggers are called and .fmt files are rebuilt - if tex-common is updated, all formats are rebuilt - (irrelevant for clisp) if one of the engines is updated, then all the formats based on this engine (like tex, xetex, luatex etc) are rebuilt. Similar things happen with python (compiling py to pyc), elisp files (el to elc) etc. The main "compiler" is triggered when depending packages are installed. If this is the plan I can help setting up such a layout in clisp. All the best Norbert -- PREINING Norbert http://www.preining.info Accelia Inc. + JAIST + TeX Live + Debian Developer GPG: 0x860CDC13 fp: F7D8 A928 26E3 16A1 9FA0 ACF0 6CAC A448 860C DC13
