Re: symlinks in PKG_SYSCONFDIR

[Hauke Fath <hauke%Espresso.Rhein-Neckar.DE@localhost>]

At 19:39 Uhr +0900 26.3.2008, Joerg Sonnenberger wrote:
>> wip/tsm installs a symlink to an i18n directory in 'post-install'; the
>> PLIST has an @unexec for it.
>
>That only works if the symlink is included in the PLIST, otherwise
>binary package installation will differ from source builds.

You're right, of course... I should have remembered the details and didn't:

<snip="pkgsrc-wip-discuss">
To: pkgsrc-wip-discuss%lists.sourceforge.net@localhost
From: Hauke Fath <hf%spg.tu-darmstadt.de@localhost>
Subject: Re: pkgsrc-wip NetBSD 4.99.54/i386 2008-02-24 02:54

At 16:23 Uhr +0100 28.02.2008, Tobias Nygren wrote:
>pkgsrc bulk build report
>========================

Hmmm... for wip/tsm, I get

[...]
=> Registering installation for tsm-5.2.2
tsm-5.2.2 requires installed package suse_compat-10.0nb3
tsm-5.2.2 requires installed package suse_x11-10.0nb3
=> Checking file-check results for tsm-5.2.2
ERROR: ************************************************************
ERROR: The following files are in /usr/bulk/pkg but not in the PLIST:
ERROR:         /usr/bulk/pkg/custom_etc/tsm/en_US
*** Error code 1

The Makefile creates ${PKG_SYSCONFDIR}/en_US as a symlink to
{mumble}/en_US/ (arguably, this wasn't happening for the binary
package, which wanted an "@exec ..." statement in PLIST).

How to deal with this - is it appropriate to add the symlink to
CHECK_FILES_SKIP?
</snip>

Apparently, you cannot add things to PLIST that are outside of $PREFIX, so
you have to add them to CHECK_FILES_SKIP.

        hauke

--
"It's never straight up and down"     (DEVO)