On Wed, 2011-07-27 at 16:09 -0700, Brock Pytlik wrote: > (or that an exclude dependency exists).
That's actually a bug in pkglint at the moment - it doesn't handle exclude dependencies anywhere it finds conflicts unfortunately. I'm not sure it's been filed yet though (I'll do so now) Apart from that, this code would report an error on the example you cited, namely: timf@linn[1068] pkglint p1.mf p2.mf 2>&1 | grep dupaction ERROR pkglint.dupaction001.1 path foo is a duplicate delivered by pkg://opensolaris.org/[email protected],1.0 pkg://opensolaris.org/[email protected],1.0 under all variant combinations ERROR pkglint.dupaction009.7 path foo has both overlay and non-overlay actions across pkg://opensolaris.org/[email protected],1.0, pkg://opensolaris.org/[email protected],1.0 ERROR pkglint.dupaction009.5 path foo uses 'overlay=true' actions but has no corresponding 'overlay=allow' actions across pkg://opensolaris.org/[email protected],1.0, pkg://opensolaris.org/[email protected],1.0 timf@linn[1069] tail -1 p1.mf p2.mf ==> p1.mf <== file path=foo overlay=true mode=0644 owner=root group=sys ==> p2.mf <== file path=foo mode=0644 owner=root group=sys cheers, tim _______________________________________________ pkg-discuss mailing list [email protected] http://mail.opensolaris.org/mailman/listinfo/pkg-discuss
