On 07/28/11 17:44, Danek Duvall wrote:
Enda O'Connor wrote:
Hi
So what exactly controls which files from a package get installed in
a ipkg zone, I though it was
variant.opensolaris.zone=global
so I have
pkg contents -a variant.opensolaris.zone=global core-os
PATH
lib/svc/bin/svc.startd
...
My ipg zone has
root@zone1:~# pkg contents core-os|grep svc.startd
lib/svc/bin/svc.startd
usr/share/man/man1m/svc.startd.1m
root@zone1:~# pkg contents -a variant.opensolaris.zone=global core-os
pkg: contents: no matching actions found in the listed packages
root@zone1:~#
But my ipkg zone has this file obviously, so what determines if a
file gets provisioned into my ipkg zone exactly.
Not sure if this is right mailing list for this query, but it
appears related to pkg command.
pkg is fine; either pkgdepend or the ON build is a little off. If you look
at the output of pkg contents -m core-os, you'll see that svc.startd is
delivererd both for the global zone as well as for non-global zones. It's
the same file; the difference is that the non-global variant has a
bypass-generate attribute attached to it. I'm not sure how that got there
on just that one variant.
Hi
I logged 7072325 to cover this one.
Enda
Danek
_______________________________________________
pkg-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/pkg-discuss
_______________________________________________
pkg-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/pkg-discuss
