Summary: | Unclear statements in "World Update" section | ||
---|---|---|---|
Product: | [OLD] Docs-user | Reporter: | BlueRaven <blue> |
Component: | Portage Manual | Assignee: | Docs Team <docs-team> |
Status: | RESOLVED WORKSFORME | ||
Severity: | normal | ||
Priority: | High | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | All | ||
URL: | http://www.gentoo.org/doc/en/portage-manual.xml#doc_chap3 | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
BlueRaven
2004-03-18 06:41:51 UTC
I'm getting more and more confused... Today, after an emerge sync, Portage caught the updated dependency. :-O And no, I didn't either use -D or put the dependency in the world file. I think it can be classified as a Portage bug now, but I'd still appreciate some words from you. :-) Afaik, the documented behaviour is the expected behaviour. So immediate dependencies should be updated, dependencies of dependencies (and deeper) not unless you add the "-D" tag. I'm marking this as WORKSFORME. |