| Commit message (Collapse) | Author | Age | Files | Lines | |
|---|---|---|---|---|---|
| * | solver: fix potential install_if processing failure, fixes #8237 | Timo Teräs | 2017-12-12 | 1 | -0/+20 |
| | | | | | | | | | | In discovery phase, there was logic to not process packages multiple times. However, that logic failed to account the package's depth and install_if state for the name being processed. This caused install_if processing failure in certain topologies of the dependency graph. Adds also a test case that should catch this issue reliably. | ||||
| * | solver: reintroduce install_if support | Timo Teräs | 2011-08-18 | 1 | -0/+48 |
| * each package name has two sorting positions, one which causes install_if triggers to be run, and other for bulk dependencies * fix also inverted ordering of package installations | |||||
 |
index : aports | |
| Main aports tree | gitolite |
| aboutsummaryrefslogtreecommitdiffstats |