On Sat, 17 Jun 2006 10:53:17 +0200, Hemmann, Volker Armin wrote: > > Could you be more specific, please? How is it harmful? What happens to > > your system when you use --deep? > > because sometimes a lib/dependency may be upgraded to an incompatible > version, resulting in open and hidden breakage.
If the later version is incompatible with installed software, that
software should block the update. this behaviour indicates a broken
ebuild.
The main risk with using deep, particularly on a ~arch system, is that
you get the updates when they come out, instead of waiting until they
are needed. not using deep lets others hit the problems and get them
sorted out before you need an update.
> Code Listing 13: Updating your system
> # emerge --update --ask world
>
> owever, it will only verify the versions for the applications you have
> explicitly installed - not the dependencies. If you want to update
> every single package on your system, add the --deep argument:
That's wrong.
"emerge package" checks only the package.
"emerge --update package" check package and any first-level dependencies
and updates them all. Even if package has not been updated, if a
first-level dependency has, it will be installed. First level
dependencies are those listed in the package's ebuild.
"emerge --update --deep package" follows the complete dependency tree for
package.
Even "emerge --update --deep world" may not update everything. If a
package is not in your world file, nor a dependency of something in your
world file, it will not be updated.
> Oh, and it says 'sometimes to catch security updates'. Not 'everytime
> you update'.
>
> You can catch the security updates by being on the gentoo-announce
> mailing list. No need for --deep.
Or by running "glsa-check --test all" every time you sync or from a cron
task.
--
Neil Bothwick
QOTD:
The only easy way to tell a hamster from a gerbil is that the
gerbil has more dark meat.
signature.asc
Description: PGP signature
