On 05/27/11 21:24, Brock Pytlik wrote:
On 05/27/11 03:24, Peter Dennis wrote:
[snip]
Indeed it does.
What is the expected interaction if a package is frozen and it is
part of a greater incorporation ?
I presume that trying to move forwards at the incorporation level
will fail with a message to indicate that the 'frozen package'
has prevented the move forwards.
Yep, that's what I anticipate at least.
It would also be good to have an option to indicate why something
has been frozen (ie for the reasons you state above: "new version
not certified for business process").
pkg freeze [-c "reason text"] (fmri|pattern|pkg_name) ...
pkg unfreeze [-c "reason text"] pkg_name|pattern ...
That's a really good idea. I'll add it unless I hear some objections.
And then when trying to move forwards, and the freeze has prevented
the move, if present the comment is displayed.
What interactions should/could there be with zones ?
Not sure what you mean. If you do pkg freeze in the global zone, it
doesn't freeze any packages in the NGZ. If the package you've frozen is
a sync package, then that could prevent that package from moving forward
in the NGZ because of the sync. What interactions were you
hoping/thinking for/of?
That sounds fine - just wanted to see what would happen.
thanks!
pete
Brock
Thanks
pete
[snip]
_______________________________________________
pkg-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/pkg-discuss
