| 1 |
On Sat, 17 Jun 2006 10:53:17 +0200, Hemmann, Volker Armin wrote: |
| 2 |
|
| 3 |
> > Could you be more specific, please? How is it harmful? What happens to |
| 4 |
> > your system when you use --deep? |
| 5 |
> |
| 6 |
> because sometimes a lib/dependency may be upgraded to an incompatible |
| 7 |
> version, resulting in open and hidden breakage. |
| 8 |
|
| 9 |
If the later version is incompatible with installed software, that |
| 10 |
software should block the update. this behaviour indicates a broken |
| 11 |
ebuild. |
| 12 |
|
| 13 |
The main risk with using deep, particularly on a ~arch system, is that |
| 14 |
you get the updates when they come out, instead of waiting until they |
| 15 |
are needed. not using deep lets others hit the problems and get them |
| 16 |
sorted out before you need an update. |
| 17 |
|
| 18 |
> Code Listing 13: Updating your system |
| 19 |
> # emerge --update --ask world |
| 20 |
> |
| 21 |
> owever, it will only verify the versions for the applications you have |
| 22 |
> explicitly installed - not the dependencies. If you want to update |
| 23 |
> every single package on your system, add the --deep argument: |
| 24 |
|
| 25 |
That's wrong. |
| 26 |
|
| 27 |
"emerge package" checks only the package. |
| 28 |
|
| 29 |
"emerge --update package" check package and any first-level dependencies |
| 30 |
and updates them all. Even if package has not been updated, if a |
| 31 |
first-level dependency has, it will be installed. First level |
| 32 |
dependencies are those listed in the package's ebuild. |
| 33 |
|
| 34 |
"emerge --update --deep package" follows the complete dependency tree for |
| 35 |
package. |
| 36 |
|
| 37 |
Even "emerge --update --deep world" may not update everything. If a |
| 38 |
package is not in your world file, nor a dependency of something in your |
| 39 |
world file, it will not be updated. |
| 40 |
|
| 41 |
> Oh, and it says 'sometimes to catch security updates'. Not 'everytime |
| 42 |
> you update'. |
| 43 |
> |
| 44 |
> You can catch the security updates by being on the gentoo-announce |
| 45 |
> mailing list. No need for --deep. |
| 46 |
|
| 47 |
Or by running "glsa-check --test all" every time you sync or from a cron |
| 48 |
task. |
| 49 |
|
| 50 |
|
| 51 |
-- |
| 52 |
Neil Bothwick |
| 53 |
|
| 54 |
QOTD: |
| 55 |
The only easy way to tell a hamster from a gerbil is that the |
| 56 |
gerbil has more dark meat. |
Archives