Pacman post-install hooks appear to run but do not

[erikli]

While attempting to install texlive-core:

pacman -S texlive-core

I noticed that the resulting binaries do not function properly to compile .tex files:

pdftex '\empty Hello world!\bye'

results in an error. On further inspection, it appears to be because the post-install hooks (which pacman happily reports are run), do not actually run. The workaround is to run the hooks/scripts in /usr/share/libalpm/{hooks,scripts} manually in the root folder / as the root user. This seems generally unsafe and upstream pacman handles this by chrooting the hooks through libalpm.

This appears related to Issue #30 (chroot "Function not implemented") in that WSL does not provide chroot() currently and that ALWSL has modifications to make things function. My undestanding is that the custom pacman in ALWSL has been stubbed to not require chroot() for package installation. Is ALWSL pacman also supposed to stub-in for the post-install hooks? I have not tried this on a clean ALWSL install so it's also possible that my ALWSL version is using an older customized pacman.

I am guessing the correct ultimate fix for this is to lean on the chroot() implementation that landed upstream WSL in Build 14936 and should ship to most users with Windows 10 creator's update. Until then, it would be nice if the post-install hooks are either run by the custom pacman or a reminder to run the hooks manually is printed out.

[turbo]

I'll look into this.