Damian Krzeminski wrote: > Arjun Nair wrote: >> Hi, >> >> Currently, to determine the SW version running on a system, we do a rpm >> query for the sipXcommons rpm, and then parse the version number from there. >> I would like to propose a different way to do this. SipXsupervisor has >> access to its build version number, through >> "config/sipxsupervisor-buildstamp.h - SipXsupervisorVersion". So, instead of >> doing the RPM query/parsing, we could pass the SipXsupervisorVersion number >> up to sipXconfig. This method would work on developer builds as well. Does >> anyone see anything wrong with this? >> >> Arjun > > In that case we could just use the version that sipXconfig displays in the > footer: it's provided by the VersionInfo object.
However, this would not work for distributed systems, where the sipXconfig running on the primary maybe of a different version than the SW version on the redundant system. > > That said: I am not sure why we trying to fix it. I see a long list of > comments in JIRA, but no matter what we do the upgrade is going to work for > RPM version only, right? And we do not have any problems detecting the > version on RPM builds - or do we? On a SCS system (from iso), you get a "The system is currently running Loading "fastestmirror" plugin" message rather than the version number. We could just grep for this text manually and deal with it, but it seems pretty dirty to me _______________________________________________ sipx-dev mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-dev Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-dev sipXecs IP PBX -- http://www.sipfoundry.org/
