Subject: pkg/10768: netatalk-asun package system binaries' path.
To: None <gnats-bugs@gnats.netbsd.org>
From: Takahiro Kambe <taca@sky.yamashina.kyoto.jp>
List: netbsd-bugs
Date: 08/06/2000 16:13:12
>Number: 10768
>Category: pkg
>Synopsis: netatalk-asun package system binaries' path.
>Confidential: no
>Severity: non-critical
>Priority: low
>Responsible: pkg-manager
>State: open
>Class: change-request
>Submitter-Id: net
>Arrival-Date: Sun Aug 06 16:14:00 PDT 2000
>Closed-Date:
>Last-Modified:
>Originator: Takahiro Kambe
>Release: NetBSD 1.5_ALPHA 2000/8/5
>Organization:
>Environment:
System: NetBSD edge.sky.yamashina.kyoto.jp 1.5_ALPHA NetBSD 1.5_ALPHA (CF-M33) #51: Sat Aug 5 15:59:43 JST 2000 taca@edge.sky.yamashina.kyoto.jp:/usr/src/sys/arch/i386/compile/CF-M33 i386
>Description:
I'm happy with addition of netatalk-asun package.
But I found that it installs system binaries into ${LOCALBASE}/libexec
instead of ${LOCALBASE}/sbin. Since netatalk package installs
system binaries into ${LOCALBASE}/sbin, netatalk-asun package
should use the same install path.
From netatalk-asun/pkg/PLIST, those files are considered to move
${LOCALBASE}/sbin:
libexec/afpd
libexec/atalkd
libexec/etc2ps
libexec/papd
Other files seems to executed indirectly by other commands, so
they should still remain in ${LOCALBASE}/libexec.
libexec/psffilters/*
libexec/psa
libexec/psf
>How-To-Repeat:
Compare netatalk-asun/pkg/PLIST and netatalk/pkg/PLIST.
>Fix:
I'm sorry that I don't have much time for providing real code now,
but it should be fairly easy.
>Release-Note:
>Audit-Trail:
>Unformatted: