On 17.06.12, Marc Haber wrote: > Package: jed-common > Version: 1:0.99.19-2.1 > Severity: normal
> I am not sure whether this is a policy violation, but it is most > probably a surprise for most users. In Debian I expect all files under > /usr to come from packages, and thus be static. This is not the case > for the *.slc files that are written to /usr/share/jed/lib during > postinst with a call to /usr/share/jed/compile/jed-common install. The *.slc files are bye-compiled versions of the corresponding *.sl files in the packages jed-common and jed-extra. Placing them alongside the sources is common practice and prevents surprises when customizing the editor (using a custom jed-library-path, using drop-in replacements from jed-extra or locally installed). The same scheme is used by Python-2 packages: the generated *.pyc files are stored alongside the *.py source under usr/lib/... > In my expectations, such files should be in /var/lib since they're > variable data and not registered with the packaging system. The byte-compiled filea are no more variable than the rest of the package, as they are only generated/deleted when the package is (de)installed or updated. Günter -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org