Scott Lawrence wrote: >Subject: Re: [sipX-dev] XX-5695 Software Updates screen cannot >determine version on SCS or system built from sources > >On Wed, 2009-07-29 at 15:08 -0400, 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? > >It's easier than that, I think... > >I believe that you should be able to fetch the process >definition file for any component by doing a GET through >sipXsupervisor for it, the same as reading a log file. If >that isn't true, then it's trivial to make it work. > >Then you can parse the version out of that process definition. > Since that's the value that will be used by the supervisor, >it's the most useful one for sipXconfig to get. >
Yes these methods will give you the correct version number but in this software update mechanism were trying to compare Apples to Apples. We're looking at the version from the "installed rpm" as compared to that from the repo site. You're apple is tastier (or at least looks tastier) but should this really be the one to eat. I recall a "princess" biting into the tasty looking apple and you know what happened to her. :) _______________________________________________ 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/
