2015-12-29 17:55 Axel Beckert:
Hi Jidanni,
積丹尼 Dan Jacobson wrote:
Aptitude has a neat feature that I am not sure is documented on the man
page:
In the case that some of the packages cannot be retrieved, a second run
of aptitude will install the ones that can!
Indeed.
So perhaps on the man page mention that a second identical run of e.g.,
safe-upgrade, full-upgrade, will proceed to install available packages
that a first run couldn't.
But safe-upgrade and full-upgrade are the wrong examples. They do this
anyway. Also "apt upgrade" and friends do this. That's the idea of all
"upgrade" subcommands: Upgrade (more or less) all upgradable
packages -- independent of if there was a try to upgrade them before.
The nice thing is that aptitude stores installation wishes in general
and the next action will also fulfil them.
E.g. if for "aptitude install pkg1 pkg2" the installation of pkg2
fails, another "aptitude install" without further parameters will try
to install pkg2 again.
All this is documented in the man page, I think:
install
...
As a special case, “install” with no arguments will act on any
stored/pending actions.
Note
Once you enter Y at the final confirmation prompt, the “install”
command will modify aptitude's stored information about what actions
to perform.
Therefore, if you issue (e.g.) the command “aptitude install foo bar”
and then abort the installation once aptitude has started downloading
and installing packages, you will need to run “aptitude remove foo
bar” to cancel that order.
safe-upgrade && full-upgrade
...
If no <package>s are listed on the command line, aptitude will attempt
to upgrade every package that can be upgraded. Otherwise, aptitude
will attempt to upgrade only the packages which it is instructed to
upgrade. The <package>s can be extended with suffixes in the same
manner as arguments to aptitude install, so you can also give
additional instructions to aptitude here; for instance, aptitude
safe-upgrade bash dash- will attempt to upgrade the bash package and
remove the dash package.
Cheers.
--
Manuel A. Fernandez Montecelo <manuel.montez...@gmail.com>
