Ok some examples:
We need to show the user:
Installed:
Installable: <-- what will go on their system, established from the plan
Latest: <-- what's the latest in the repository, only show this, if
Installable is not equal to Latest.
That way they can better understand why when upgrading a package from
0.3 which has a later version of say 0.5 in the repo they can only go to
0.4.
The plan will tell them they can go to 0.4, but we want to see if this
is the latest version or not. If it is not then we flag this to the user
and explain that they can only get the latest version 0.5 by doing the
equivalent of an image-update in the GUI using Updates.
JR
Shawn Walker wrote:
John Rice wrote:
Shawn - its to support the Packge Verison Info we discussed before.
This was a corner case that we had not come across.
You have an installed package and want to check if its installable or
not. We run the plan and it comes back with information on what is
I assume you mean updatable since the package is already installed?
Yep
local, what's remote and what the plan can do. In this particular
instance, the local and remote versions are different, but the plan
and remote versions are the same. So we can tell the user they can
install the latest version.
I'm a bit confused. The plan should tell you what version can be
installed, you shouldn't need to compare remote_info and local_info at
all.
See above.
Looking at the code should we also be checking the version, in
addtion to the build_release and branch, to establish what the user
can and cannot upgrade to? If that's the case then I will take this
bit out of the current webrev, and spin a new one for changes in
__after_get_info().
The plan is what determines what the user can and cannot upgrade to.
Agreed.
_______________________________________________
pkg-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/pkg-discuss
