On Monday, 9 January 2023 19:54:08 CET M. Zhou wrote: > Is it possible for us to slightly modify the postinst script to > recompile the cache locally when the compiler id mismatches?
I'd rather not. Untangling pre-compilation issues is hard enough. In case of problem I dont' want to wonder whether the failure comes from files compiled on Debian server or on user's machine. > The fallback script rakudo-helper.pl can at least make sure > a raku-* package is still functional even without a matching > compiler ID. In that case we don't have to add the compiler ID > to the virtual package name, and every architecture can track > the same and consistent virtual package dependency. Given the state of Raku's compiler-id, I think the only sane way (or rather which will preserve my sanity) is to go back to perform pre-compilation at installation time. This require: - an update of dh-raku to restore compilation at installation time. - a modification of all raku modules to: - remove dependency on raku-api* - go back to arch:all - depend on next dh-raku version Thoughts ?
