Bug#886986: please remove bump-fasl-loader-version.patch

[Sébastien Villemot]

On Sat, Jan 13, 2018 at 01:55:58PM +0900, Norbert Preining wrote:

> > 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.

Thanks to Bruno's cooperation, the plan seems rather to generate a proper
ABI-like number (in this case the .mem hash code), which will allow us to solve
this issue with minimal changes to both xindy and clisp packages.

-- 
⢀⣴⠾⠻⢶⣦⠀  Sébastien Villemot
⣾⠁⢠⠒⠀⣿⡁  Debian Developer
⢿⡄⠘⠷⠚⠋⠀  http://sebastien.villemot.name
⠈⠳⣄⠀⠀⠀⠀  http://www.debian.org
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: not available
URL: <http://lists.alioth.debian.org/pipermail/pkg-common-lisp-devel/attachments/20180113/884427c1/attachment.sig>