net-snmp: Use ${PN} instead of hardcoding net-snmp

This shows up when doing multilib builds where
PN != BPN and warnings about non existent systemd packages are
popping up.

Signed-off-by: Khem Raj <raj.khem@gmail.com>
This commit is contained in:
Khem Raj
2012-12-13 10:01:10 -08:00
parent 1db7387892
commit d129d2b6aa
@@ -38,8 +38,8 @@ do_install_append() {
-i ${STAGING_BINDIR}/net-snmp-config
}
PACKAGES = "net-snmp-dbg net-snmp-doc net-snmp-dev net-snmp-staticdev net-snmp-static net-snmp-libs \
net-snmp-mibs net-snmp-server net-snmp-client net-snmp-server-snmpd net-snmp-server-snmptrapd"
PACKAGES = "${PN}-dbg ${PN}-doc ${PN}-dev ${PN}-staticdev ${PN}-static ${PN}-libs \
${PN}-mibs ${PN}-server ${PN}-client ${PN}-server-snmpd ${PN}-server-snmptrapd"
ALLOW_EMPTY_${PN}-server = "1"
FILES_${PN}-libs = "${libdir}/lib*${SOLIBS}"
@@ -59,7 +59,7 @@ INITSCRIPT_PARAMS_${PN}-server = "defaults"
LEAD_SONAME = "libnetsnmp.so"
pkg_postrm_net-snmp-server() {
pkg_postrm_${PN}-server() {
if test "x$D" != "x"; then
OPT="-r $D "
else