Miroslav Suchý wrote:
Dennis Gilmore wrote:
On Wednesday 19 November 2008 11:03:45 am Miroslav Suchý wrote:
Can we create new API call which add something to distinguish between
satellite versioning and spacewalk versioning?
I have problem that I want to call proxy.isProxy() which will be only in
0.4+. But the expression "if api > 0.4" is true for old satellites (like
5.0) as well.
I suggest to add some kind of epoch, but I have no idea how to make it
compatible with olders api. Any idea?
I would suggest using an internal API number that is different from release
start with 1.0 and if there is minor changes resultin in incompatabilities
just to 1.1 but major changes result in 2.0 or even just start at 100
Personally i do not think it needs to be tied to the spacewalk/satellite
release.
According the code the the returned version is content of web.version
/etc/rhn/default/rhn_web.conf
I see as best option to create new config option web.apiversion which we
bump up independently on spacewalk version. And ideally return it back
to 5.2 at least and act as API version 0.x never exist.
Yes maybe we can bump it to 100 or 10 to clearly state that it has
nothing to do with spacewalk versioning.
+1
--
Mike McCune
mmccune AT redhat.com
Engineering | Portland, OR
RHN Satellite | 650.567.9039x79248
_______________________________________________
Spacewalk-devel mailing list
[email protected]
https://www.redhat.com/mailman/listinfo/spacewalk-devel
