Consider this scenario:
auth1 contains [EMAIL PROTECTED]
auth2 contains [EMAIL PROTECTED]
An image starts out with auth1 as the preferred authority.
pkg install foo
installs [EMAIL PROTECTED]
Next:
pkg image-update
does nothing. All ok so far.
Now the preferred authority is changed to auth2:
pkg set-authority -P auth2
Now:
pkg image-update
installs [EMAIL PROTECTED]
Is this behavior a bug or a feature?
Argument for it being a bug is that [EMAIL PROTECTED] was installed from
authority
auth1, so since packages are supposed to stay with the authority from
which they were installed, you shouldn't get [EMAIL PROTECTED] from auth2
unless you
explicitly ask for it.
Argument for it being a feature is that [EMAIL PROTECTED] was installed from
the
preferred authority (at the time it was installed), and the [EMAIL PROTECTED]
update
came from the preferred authority (at the time of the image-update), so
everything is working as it should. Changing the preferred authority for
an image means that all packages that were installed from the preferred
authority should now start getting their updates from the new preferred
authority.
I'm guessing this is a feature because the PRE_ is stored in the
installed file to remember which packages came from the preferred
authority. Is that right?
Thanks.
Tom
_______________________________________________
pkg-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/pkg-discuss
