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

[Agustin Martin]

On Fri, Jan 12, 2018 at 11:06:11AM -0500, Sam Steingold wrote:
> > * Sébastien Villemot <fronfgvra at qrovna.bet> [2018-01-12 12:30:26 +0100]:
> >
> >> 
> >> What if a user has installed xindy, with clisp as dependency, and then upgrades
> >> clisp to a different version, with a different mem-hash?
> >>   1) Will the package manager report a conflict?
> >
> > Yes.
> >
> >>   2) Will the package manager propose, as solution of this conflict, to install
> >>      another binary package for xindy? Or will it only propose to remove xindy?
> >
> > Only two options will be available:
> > 1) either upgrade clisp and xindy together
> > 2) or do not upgrade any of them
> 
> What about including the xindy FAS files in the distribution?
> FAS files are plain text ASCII files and compress well.
> One can even concatenate them (in the right order) and gzip.
> Then upgrading CLISP would mean re-dumping the lisp image (MEM):
> clisp -i xindy.fas -x '(saveinitmem "xindy.mem")'

Hi all,

Thanks, Bruno and Sam for pointing out the problems of the change I
proposed and for all the info and suggestions you both provided.

I wonder if this can properly be achieved through dpkg triggers.

That would be based on a specific dpkg trigger (e.g. xindy-buildmem).
The result should be that xindy.mem is removed on prerm and rebuilt
after fas contents on package postinst any time clisp or xindy are changed.
It should be located under /var/lib/xindy and xindy.in modified for that.

This may have the additional advantage of making xindy an arch:all package.

-- 
Agustin