On 10/ 3/11 03:08 PM, Brock Pytlik wrote:
On 10/03/11 14:33, Alan Coopersmith wrote:
Hmm, I've never needed a whitelist for that in the X or CDE builds.
[snip]
Hmm, maybe you're bypassing them, or you don't have external deps, or you're
using a reference repo for pkglint? I think those are the three ways not to need
a whitelist for that check. Tim would know better than me though.
The third one - both CDE & X use reference repos.
The only consolidation I know of with no external deps is what little is left
delivered via the manpage consolidation - everything else depends on something
like libc from ON, libm from DevPro, python from Userland, etc.
On 10/ 3/11 03:15 PM, Tim Foster added:
The one other way to avoid these, would be to exclude the obsolete dependency
check in pkglint via pkglintrc configuration.
Oh, that too - we do two passes of pkglint - the first time, before publishing
to the local repo is done without a reference repo and with a special pkglintrc
that does:
pkglint.exclude = pkg.lint.pkglint_action.PkgActionChecker.dep_obsolete
and then after publishing to the local repo, that's pkglinted using the WOS repo
for reference and the obsolete check enabled.
--
-Alan Coopersmith- [email protected]
Oracle Solaris Platform Engineering: X Window System
_______________________________________________
pkg-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/pkg-discuss
