On 18/03/2010 12:28, Danek Duvall wrote:
Darren J Moffat wrote:
I believe I know how to implement a "--force" for 'pkg install' that
would allow the update on the live image, but before I code it up I
want to be sure that it would be accepted into the gate.
Are you trying to avoid the reboot entirely, or are you just trying to
reduce the number of BEs being created?
In this particular case just avoid the number of BE's because it is the
file-system/zfs package I'm updating and I have to reboot for that to
take effect.
Would you be happy bouncing back and forth between two BEs -- update B from
A, boot into it, update A from B, boot back to that, etc?
Yes that would be good.
I'd rather see BE management get smarter than allow unsafe operations, even
with big warnings and no documentation.
Me too.
And if it's just a handful of binaries, then maybe cp really is the right
answer. You're a developer, after all, and a system of yours in rapid
development isn't necessarily going to be 100% polished w.r.t. the
packaging.
Indeed. What will pkg do if I copy binaries in place and then later do
a 'pkg image-update' because I've run a full build and now want all of
onnv ? Will it complain that the binaries I copied over don't match or
fix them up with the correct new versions anyway ? [ I wouldn't want the
old ones left in place in this case ].
--
Darren J Moffat
_______________________________________________
pkg-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/pkg-discuss
