Unable to install 0.62 when using -Dsysvinit=true option

[Dudemanguy]

If you attempt to build and install openrc using -Dsysvinit=true like so,

meson setup build -Dprefix=/usr -Dsysvinit=true
meson compile -C build

when trying to install, you might get the following error.

meson install -C build --dry-run
ERROR: Tried to install symlink to missing file /etc/init.d/agetty

The culprit appears to be the install_symlink calls introduced in e56171b. I think this is actually just an upstream meson limitation though. Appears to be exactly this issue. I guess some workaround for now is needed.

[navi-desu]

the agetty target is configured and installed right above, so it should exist, i can't reproduce this with the commands as listed, as i get:

Installing /home/anna/src/openrc/openrc/install/init.d/agetty to /etc/init.d

then later

Installing symlink pointing to /etc/init.d/agetty to /etc/init.d/agetty.tty1

could you provide install-log.txt and meson-log.txt from builddir/meson-logs?

[Dudemanguy]

I think it's a meson thing because the symlink already exists on your system but not on mine since I don't actually have openrc installed. So you don't hit that meson limitation. It can pop up while packaging for example since you install to some destdir.

Here's the two logs.
install-log.txt
meson-log.txt

[eli-schwartz]

mesonbuild/meson#12266

My analysis:

As for openrc:

Installing symlink pointing to /etc/init.d/agetty to /home/eschwartz/git/openrc/builddir/pkg/etc/init.d/agetty.tty1

ERROR: Tried to install symlink to missing file /home/eschwartz/git/openrc/builddir/pkg/etc/init.d/agetty.tty1

and:

$ ls -l builddir/pkg/etc/init.d/
total 164
-rwxr-xr-x 1 eschwartz eschwartz 1242 Apr 25 12:10 agetty*
lrwxrwxrwx 1 eschwartz eschwartz   18 Apr 25 12:11 agetty.tty1 -> /etc/init.d/agetty

Latter case is blinking red, because it doesn't exist yet. We are trying to create absolute symlinks in a DESTDIR where one points to the other, so in fact this is expected to not exist at staged-install time (DESTDIR) but will exist at real-install time (merging DESTDIR to the live filesystem e.g. via a distro package manager).

So yeah, this check makes no sense I guess. Or if we do want to check it, we need a more sophisticated check that handles recursively checking broken symbolic links against their DESTDIR offset.

[navi-desu]

meson install -C build --dry-run

#849 should fix this, though --dry-run won't work