Janie Lu wrote:
> The pkg build process creates dependencies based on the OS version that
> the *build machine* is running? That doesn't seem right.
>
> Instead, shouldn't pkg be using the OS version that the *source code* is
> based on when creating packages from that code? (This info is available
> in the macro "ONNV_BUILDNUM" in usr/src/Makefile.buildnum)
For packages that comes from ON, yes. But ON depends on many packages
from other consolidations, and all the build knows about is what's installed
on the build machine when you run it.
> GIVEN THAT:
> SUNWcs requires packageX.
> Developer workspace is based on nv_143.
> Developer builds his workspace on a machine running nv_145.
>
>
> CURRENT BEHAVIOR:
> sun...@143 depends on packa...@145.
> Why: IPS uses the build machine OS version to set package
> dependencies, regardless of the source code's OS
> version.
>
> SHOULD BE:
> sun...@143 depends on packa...@143.
> Why: IPS looks at the source code being built to determine the OS
> version and then sets dependencies accordingly.
But if packageX is not from ON, say it's libxml from SFW, libm from DevPro,
libdbus from JDS (all things core pieces of ON depend on), the build has
built with the 145 version of the headers and linked against the 145 version
of the libraries, and has no way of knowing if it's ABI compatible with any
earlier version of those external libraries, or even if they have build
numbers that in any way correspond to the ON build number.
--
-Alan Coopersmith- [email protected]
Oracle Solaris Platform Engineering: X Window System
_______________________________________________
caiman-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/caiman-discuss
