Wes Hardaker wrote: > 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).
I haven't tested how exactly the install procedure behaves/breaks on version differences, but I'd be keen to introduce an override flag and tell people about it at the same time we bail out because of version differences, at least if they are minor-minor (e.g. 5.3.1 vs. 5.3.2). I'd even argue to only warn rather than exit in this situation and only refuse to continue if we detect a different *branch* (e.g. 5.2.x vs. 5.3.x). There's also a different problem: running the perl module against different net-snmp libraries than they've been compiled against. This is where our soname changes help to refuse cross-branch library loading, but I don't see how we prevent anything else than that. So why force differently at install time? Aren't we supposed to maintain compatibility within the same branch anyway? > algorithm: perl version = W + X/100 + Y/10000 + Z/100000 > > thus 5.3.1 would be 5.0301 Fine by me. +Thomas -- Thomas Anders (thomas.anders at blue-cable.de) 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
