On Thu, 3 Jul 2003, Julio Merino wrote:
> That's what I was trying to say.  Files outside PREFIX are not in the PLIST,

"in PLIST" doesn't necessarily mean "in PREFIX" - think @cwd.


> so they need to be handled using all these special variables.

IC - so it's really about things not addressed in PLIST.

Which made me wonder why I see SPECIAL_PERMS used for things that are in
PLIST (and are thus handled properly):

audio/xmcd/Makefile:SPECIAL_PERMS=           ${ARCHBIN}/cda ${_SETUID_ROOT}
audio/xmcd/Makefile:SPECIAL_PERMS+=          ${ARCHBIN}/xmcd ${_SETUID_ROOT}
comms/minicom/Makefile:SPECIAL_PERMS=        ${PREFIX}/bin/minicom uucp dialer 4755
print/cups/Makefile:SPECIAL_PERMS=           ${PREFIX}/bin/lppasswd ${CUPS_USER} ${CUPS_GROUP} 4755
x11/eterm/Makefile:SPECIAL_PERMS=            ${PREFIX}/bin/Eterm ${SETUID_ROOT_PERMS}
x11/kdebase3/Makefile:SPECIAL_PERMS+=        ${PREFIX}/bin/konsole_grantpty  ${_KDE_SETUID_ROOT}
x11/kdebase3/Makefile:SPECIAL_PERMS+=        ${PREFIX}/bin/kcheckpass        ${_KDE_SETUID_ROOT}
x11/kdebase3/Makefile:SPECIAL_PERMS+=        ${PREFIX}/bin/ksysguardd        ${_KDE_SETUID_ROOT}
x11/kterm/Makefile:SPECIAL_PERMS=            ${PREFIX}/bin/kterm ${_SETUID_ROOT}
x11/rxvt/Makefile:SPECIAL_PERMS=             ${PREFIX}/bin/rxvt ${SETUID_ROOT_PERMS}
x11/xlockmore-lite/Makefile:SPECIAL_PERMS=   ${PREFIX}/bin/xlock ${SETUID_ROOT_PERMS}
x11/xlockmore/Makefile:SPECIAL_PERMS=        ${PREFIX}/bin/xlock ${SETUID_ROOT_PERMS}

I guess these should be nuked from heaven. All of them.
(Yes, that's all the hits for a grep on SPECIAL_PERMS in pkgsrc Makefiles)


 - Hubert

-- 
Want to get a clue on IPv6 but don't know where to start? Try this:
* Basics -> http://www.onlamp.com/pub/a/onlamp/2001/05/24/ipv6_tutorial.html
* Setup  -> http://www.onlamp.com/pub/a/onlamp/2001/06/01/ipv6_tutorial.html
Of course with your #1 IPv6 ready operating system -> http://www.NetBSD.org/