easy dependency upgrades

Imported: http://tracker.labix.org/issue54
Reason: Review + documentation
further details: https://blueprints.launchpad.net/smart/+spec/bug-reporting-migration

msg1109 (view) Author: lewin Date: 2007-03-03.06:05:16

That is a good idea. I would find that practical too.

msg157 (view) Author: niemeyer Date: 2005-12-06.23:11:25

I understand your suggestion Tom. It makes sense, and I'll keep it in mind.

Notice that you may already look for a provided/required relation right now,
by using something like provides:dependencyname or requires:dependencyname,
either in the GUI search or in the command line.

msg146 (view) Author: TomPh Date: 2005-12-05.22:03:47

On Mon, 05 Dec 2005 20:41:50 +0000
"Mauricio Teixeira (netmask) at Labix Tracker" <email address hidden> wrote:

>
> Mauricio Teixeira (netmask) <email address hidden> added the comment:
>
> After you select to upgrade a package, Smart doesn't do any calculations
> on the dependencies. Those calculations occur right when you select
> "Commit", so then you will have a infomation window showing the package
> upgrade itself and the depedencies which need to be upgraded too.
>
> If it's not what you're talking about, then we're confused and could not
> understand the issue.

There may be various available versions of any dependency for a package. Mandriva (at least?) does not properly upgrade dependant libraries, its policy seems to be not to include library versions in spec files. (Mandriva's suggested approach, in effect to always upgrade _all_ libraries, is totally useless for those of us with limited bandwidth.) A couple of times I've found that successful upgrade of a mandriva package required me to do manual, trial-and-error selection of which dependencies to upgrade.

So when using smart (in gui mode) a scenario is this:
1. find a package that you're interested in (doesn't matter whether installed or not, but in the case that interests me, it is installed).
2. look at that package's dependencies, on the relations tab in the window.
3. allow any such dependency to be selected for installation, in the same way as it could be selected if it were displayed in the upper part of the window.

This approach avoids having to find that dependant package separately, and then selecting it. Unless you open a second smart instance, iterating back and forth between finding a package and finding its dependencies is quite annoying.

Hope this makes it clearer.

Regards
Tom

msg142 (view) Author: netmask Date: 2005-12-05.20:41:50

After you select to upgrade a package, Smart doesn't do any calculations on the
dependencies. Those calculations occur right when you select "Commit", so then
you will have a infomation window showing the package upgrade itself and the
depedencies which need to be upgraded too.

If it's not what you're talking about, then we're confused and could not
understand the issue.

msg133 (view) Author: TomPh Date: 2005-12-02.01:28:09

Package dependencies, displayed on the GUI relations tab, may include various
versions of each such dependency. It would be great to be able to select
dependency updgades directly from the relations treeview, instead of having to
iterate back and forth between finding the 'parent' package and its dependent
package(s), and selecting updgrages for the latter in the main treeview.