Andy Spitzer wrote: > Woof! > > I'm working on packaging up a new FreeSWITCH RPM. > > Alas, FreeSWITCH has yet to release their 1.0.2 version, and while we > are waiting I think it makes sense at this point to pick an interim > version off their trunk so we can move forward with some outstanding FS > configuration issues that need a newer version of FS than we currently > are using. > > So currently we have this: > > lib/freeswitch/freeswitch.spec.in: ... Version: 1.0.1 Release: > 3 ... > > I intend to replace it with a current version from trunk (svn rev > 10526), which I named thusly: ... Version: 1.0.trunk.10526 Release: > 1 ... > > FreeSWITCH shows this version in their builds "FreeSWITCH Version > 1.0.trunk (10524)" which is where the naming came from. > > I'm not sure how RPMs will deal with the Version number changes. Will > it know 1.0.trunk.10526 is "newer" than 1.0.1? And what happens when FS > releases 1.0.2? > > I supposed I could call it "1.0.1.trunk.10526", does that make more > sense? > > --Woof!
This is the best explanation that I once found: http://linux.duke.edu/~mstenner/docs/rpm-version-cmp According to this 1.0.trunk.10526 is not going to work (trunk vs. 1 is undefined) But 1.0.1-10526 will be newer then 1.0.1 (and it's pretty much the same convention that sipXecs is using). D. _______________________________________________ sipx-dev mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-dev Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-dev
