On 12/10/11 01:09 PM, [email protected] wrote:
This is essentially for testing. We'd like to have some well known pkg
to install/uninstall that we know is likely to require a reboot.
Rather than relying on a well-known package, I suggest that you should
create and publish your own test package with a simple 'file' action
that your test suite generates automatically (perhaps a file containing
a current datestamp) and tag that action with a 'reboot-needed' actuator.
Assuming that a "well known" package is always going to contain a
reboot-needed actuator will make your tests more brittle than they need
to be.
cheers,
tim
On 12/9/2011 4:01 PM, Danek Duvall wrote:
Alta Elstad wrote:
Wouldn't -n do it?
Yes, assuming you're not trying to do this programatically. Shri didn't
mention what problem he was actually trying to solve, so I assumed a
situation where he needed programmatic access to that information, rather
than just "what'll happen if I try to install/upgrade xyz@123?".
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
_______________________________________________
pkg-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/pkg-discuss
