jed-common (1:0.99.20~pre.170+dfsg-2) unstable; urgency=medium

    The mechanism for the install-time byte-compilation of *.sl files
    implemented in version 0.99.20~pre.167+dfsg-2 of the package works
    fine, but the generated files (*.slc for instance) are left behind
    when the associated package is removed.

    This problem is fixed now. The postinst script for jed and xjed will
    remove all generated files under the directory /usr/share/jed, before
    compiling them. This happens when files are either installed in or
    removed from /usr/share/jed and its descending sub-directories by
    dpkg.

    This is a brute-force, sub-optimal solution for a problem detected by
    piuparts. In the future, a mechanism for doing compilation of the *.sl
    files only when needed (i.s. only if the .sl file is newer than the
    corresponding .slc file) should be implemented. At any rate, for now,
    the processing time for recompiling all the *.sl files seems to be
    acceptable.

 -- Rafael Laboissière <rafael@debian.org>  Tue, 13 Dec 2022 09:26:29 -0300

jed-common (1:0.99.20~pre.167+dfsg-2) unstable; urgency=medium

    The mechanism for the install-time byte-compilation of *.sl files is
    changed in this version of the package. Previously, this was done in
    the postinst script of jed-common, by calling run-parts on the
    /usr/share/jed/compile/ directory. The executable files found in this
    directory are expected to install/remove scripts for
    generating/removing the *.slc files (compiled from the *.sl files).
    For now, only the jed-common and the jed-extra packages install
    scripts in this directory.

    The problem with this mechanism is that jed-extra had also to run its
    own script (/usr/share/jed/compile/jed-extra) in its postinst script.
    Even worse, the dependency relationships between jed, xjed,
    jed-common, and jed-extra could produce undesirable effects, like the
    one reported in Bug#563630[*]: when installation of jed-extra is
    required for installation in a system that lacks either jed or xjed,
    then a race condition will happen. Indeed, the postinst script for
    jed-common will be run before the postinst script for jed (or xjed),
    but the former needs the existence of /usr/bin/jed-script, which is
    created by the update-alternative call in the postinst script of
    the later.

    In order to fix this problem, we introduce the dpkg triggers
    mechanism in the current version. With this change,
    byte-compilation of *.sl is done by the postinst scripts of both
    jed and xjed, whose debian/*.trigger files declare an interest in the
    /usr/share/jed/compile/ directory. Also, the relationship
    "Recommends: jed|xjed" has been dropped for jed-common.

    The jed-extra package will be changed accordingly.

    [*] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=563630

 -- Rafael Laboissière <rafael@debian.org>  Fri, 29 Jul 2022 13:34:39 -0300
