[Pkg-Cyrus-imapd-Debian-devel] libsnmp-dev dependency
Henrique de Moraes Holschuh
hmh at debian.org
Mon Nov 28 22:11:06 UTC 2005
I will be asking questions and proposing changes instead of commiting them
half-assed for now, so please bear with me.
Is there a good reason why the code in trunk is build-depending on
libsnmp4.2-dev? That thing is outrageously old, and unlike cyrus 2.1, 2.2
builds fine against NetSNMP 5 (in fact, I bet I could get 2.1 to do so too,
if so inclined -- but hell will freeze over first :-) ).
Updating the dependency to libsnmp9-dev (unstable/testing) and libsnmp5-dev
(sarge) is the right way to go IMHO. The package builds fine.
Any of you guys is *actually* using the SNMP agent-x functions? Have you
guys stress-tested them? Last time I debugged those I nearly went ballistic
over the amount of crap upstream libsnmp had in that stuff (which was so
utterly broken it was not funny). Since then, I have always wondered if it
would not be best to just skip compiling agent-x snmp support in Cyrus.
The first thing that killed agent-x support for my needs was that if you
restarted snmpd for any reason, you'd need to restart cyrus to get the
agent-x connection going again. The broken tcpwrappers shit in libsnmp was
just icying in the cake (and I *sure* hope nobody enabled that crap again in
the Debian packages).
--
"One disk to rule them all, One disk to find them. One disk to bring
them all and in the darkness grind them. In the Land of Redmond
where the shadows lie." -- The Silicon Valley Tarot
Henrique Holschuh
More information about the Pkg-Cyrus-imapd-Debian-devel
mailing list