Project Talk:Portage/FAQ

Small fixes

Talk status

This discussion is done as of 2017-08-01.

I would improve this article with the following things:

Use the Package template for the virtual/editor package: virtual/editor
Add code tags to: "Put an entry such as sys-libs/glibc debug.conf in [...]"
Add the Path template to "using the same format as make.conf"

Fturco (talk) 14:32, 1 August 2017 (UTC)

Sounds good, please do. Zmedico (talk) 16:29, 1 August 2017 (UTC)

All fixed up, y'all! --Maffblaster (talk) 17:53, 1 August 2017 (UTC)

Typos

Talk status

This discussion is done.

"conflict whey I attempt" — should be "when". — The preceding unsigned comment was added by Thaaxaco (talk • contribs)

Thanks, fixed --Grknight (talk) 14:07, 4 September 2019 (UTC)

revdep-rebuild

Talk status

This discussion is still ongoing as of 2021-07-04.

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 ?

Kyoreln (talk) 13:05, 4 July 2021 (UTC)

backtrack: 10 is not always right setting, 1000 could solve some longer dependency chains...

Talk status

This discussion is still ongoing as of 2022-01-15.

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 --backtrack=1000 together with --ask at 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=y 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.

As a general recommendation the use of --ask instead of --pretend has 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 --ask option will also let you confirm to write configuration changes that have been automatically generated by the --autounmask option.

I would change it myself, but I don't have the permission.

Luttztfz (talk) 08:23, 15 January 2022 (UTC)