|Re: Package Compatibility Keys [message #641707 is a reply to message #641311]
||Fri, 26 November 2010 22:42
| Dave Russo
Registered: July 2009
On 11/24/2010 1:01 PM, Patrick Geremia wrote:|
> I am using RTSC as a build system and I have a package that contains
> various functions which constitutes my the public API of that package.
> Assuming the first release of the package is 22.214.171.124, am I correct in
> stating that if my public API changes (which imply a person consuming my
> package has to rewrite his code), then the I need to increase M which
> would lead to version 126.96.36.199?
During configuration, all packages contributing content are scanned to
determine if there are any that were built using your package. If the
config tool detects that some package, say P, was built with 1.x.y of
your package and 2.a.b is contributing to the configuration, then the
configuration step will fail with an error indicating the package P must
be rebuilt with version 2.a.b.
> Also, when I create a RTSC release, how can I retrieve the compatibility
> key so as to create a release named myrelease_188.8.131.52.tar.gz assuming my
> package has the compatibility key is 184.108.40.206.
A package's compatibility key can be obtained either as part of a build
( http://rtsc.eclipse.org/cdoc-tip/index.html#xdc/bld/PackageC ontents.html#version)
or a program's configuration script
During the execution of a build script the only compatibility key
available is that of the package being built (the one contained in the
package.xdc file). During configuration, the compatibility key of any
loaded package is available (this allows a package to check the versions
of any prerequisite packages and handle incompatibilities as necessary).
> Patrick Geremia
Powered by FUDForum
. Page generated in 0.01694 seconds