>> i was upgrading (a chunk of) my installed base of pkgs this weekend
>> was dismayed to find that ethereal depends on net-snmp whereas pchar
>> depends on ucd-snmp, and the two can't coexist.
>> 
>> i opted to to build ethereal as part of my bulk-build, and came back
>> to pchar later.  a quick tweak to the makefile shows that it can
>> happily build against net-snmp, and after a bit of testing, i can't
>> *see* any problems.
>> 
>> is there any reason not to switch pchar to net-snmp for real?
>
>Not at all.  I just haven't had time to sweep through pkgsrc and switch
>packages that need ucd-snmp to use net-snmp instead.  The net-snmp
>buildlink2.mk file has some smarts for using the ucd-snmp-compatibility
>headers and libraries.  I think most packages that use ucd-snmp should
>work if you do:
>
>	USE_UCD_SNMP=	YES
>	.include "../../net/net-snmp/buildlink2.mk"
>
>in place of including the ucd-snmp/buildlink2.mk file.

i didn't go that far.

	diff -r1.17 Makefile
	23c23
	< .include "../ucd-snmp/buildlink2.mk"
	---
	> .include "../net-snmp/buildlink2.mk"
	25c25
	< CONFIGURE_ARGS+=	--with-snmp=${BUILDLINK_PREFIX.ucd-snmp}
	---
	> CONFIGURE_ARGS+=	--with-snmp=${BUILDLINK_PREFIX.net-snmp}

that was enough for me.  shall i commit it?

-- 
|-----< "CODE WARRIOR" >-----|
codewarrior@daemon.org             * "ah!  i see you have the internet
twofsonet@graffiti.com (Andrew Brown)                that goes *ping*!"
werdna@squooshy.com       * "information is power -- share the wealth."