So, the goal is to: 1) publish the most recent perl module(s) to CPAN about the same time as the most recent Net-SNMP release (5.3.1 being the next one).
2) check that the version number of the perl module matches the version number of the installed net-snmp base. This is done by comparing the output of the net-snmp-config command against the version number in the *.pm file. Bad things happen when these are out of sync (and is actually why we *stopped* publishing it years ago). The newest problem with this: CPAN requires a floating point number for the perl modules it houses. This is a guideline for perl modules in general, but CPAN actually enforces it (I learned this the hard way a few weeks ago when publishing a different module). So... the proposal is to number the perl modules in a slightly different way that is algorithmically determinable to make it convert to a floating point number. net-snmp version: W.X.Y.Z algorithm: perl version = W + X/100 + Y/10000 + Z/100000 thus 5.3.1 would be 5.0301 Thoughts? This has to be dealt with before publishing to CPAN. Ideally, I'd like to change the version numbers in the modules published in the 5.3.1 tar ball too... -- Wes Hardaker Sparta, Inc. Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 _______________________________________________ Net-snmp-coders mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/net-snmp-coders
