I would improve this article with the following things:
- Use the Package template for the virtual/editor package:
- Add code tags to: "Put an entry such as
sys-libs/glibc debug.confin [...]"
- Add the Path template to "using the same format as make.conf"
This page recommends running revdep-rebuild after depclean, however I think this is no longer necessary, as stated in Gentoolkit#revdep-rebuild.
I'm not sure either if the preserve-libs FEATURE is set by default, and if this is the case, if it perhaps won't be set for those who's system predates the change.
Can anyone confirm all this ?
backtrack: 10 is not always right setting, 1000 could solve some longer dependency chains...
In section What should I do when emerge reports a lot of dependency conflicts involving built slot-operator (foo/bar:X/Y=) dependencies?, the second paragraph looks like this:
- It addition to the --pretend and --ignore-built-slot-operator-deps=y options mentioned above, it can also be helpful to temporarily add --backtrack=0 to the emerge options, so that the dependency resolver does not spend extra time backtracking before it ultimately fails.
1st, there is a typo "It addition to" instead of "In addition to", second instead of repeating the options the sentence could be rephrases like so:
- In addtition to the above mentioned options, ...
Also, I'd like to point out that some conflicts are not solved due to the contrary logic: adding --backtrack=1000 can solve some dependencies that might be further than 10 atoms away... I've encountered this problem a couple of times, where you'd get unresolved dependencies and don't know what's going on, but with setting --backtrack=1000 everything is resolved.
My suggestion for a rewritten second paragraph:
- It is recommended to try
--askat least once, as this will catch uncommon longer dependency chains, although this will take considerably longer to resolve. If the dependency conflict persists, in addition to
--ignore-built-slot-operator-deps=ymentioned above, it can also be helpful to temporarily add
--backtrack=0to the emerge options, so that the dependency resolver does not spend extra time backtracking before it ultimately fails.
- As a general recommendation the use of
--pretendhas certain advantages, as it will save re-runs in the case of a positive result, whereas with
--pretend, should the output be satisfactory, the command has to be run again (and take time again) to actually perform the emerge action. The
--askoption will also let you confirm to write configuration changes that have been automatically generated by the
I would change it myself, but I don't have the permission.