On 01/13/13 06:34 PM, Gabriele Bulfon wrote:
Hi,
I was trying to publish latest jdk using userland build framework, by letting makefile install the original shell into the prototype area.
The p5m built has no knowledge of what java will do at runtime, so it misses some links the runtime will solve, like motif21 and the javavm chosen for the 64 arch.
Even after modifying the p5m to link some defaults, after pkg lint, I get many errors like "library xxx rpath has $ORIGIN", or complaints about non standard 64 library folder.
How can I get rid of these tests during component build/publish?
Without the specific output, these sound like they are part of the
userland pkglint checks in tools/python/pkglint/userland.py. You can
turn checks on a specific action by adding the attribute pkg.linted=true
attributes to the offending actions in your manifest (see
openssl/openssl-1.0.0/openssl-1.0.0.p5m (wanboot-openssl.o) for an
example). You can target the checks you want to turn off by using
pkg.linted.userland.{specific-check}=true. You can also use a bigger
hammer and tell pkglint that you are happy with the entire contents of
the manifest with 'set pkg.linted=true' in the manifest (see
openscap/openscap.p5m for an example)
pkglint(1) describes how to turn of various checks.
-Norm
_______________________________________________
pkg-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/pkg-discuss
