mirror of
git://git.yoctoproject.org/layerindex-web.git
synced 2025-07-19 12:49:01 +02:00
f4f2146370
The previous commit broke the layer order, e.g.: A -> B -> C -> D The algorithm is checking the dependencies one by one, and until we find D, add D to layerquery_sorted, and add it "collections", the one in "collections" means it's dependencies are OK, then C, B and A will check against collections, so that update_layer.py will update them one by one. The previous commit added A/B/C/D to collections directly, so that when check against it, all the dependencies are met, thus broke the layer sorting, and then there would be failures if we pass layer A to update_layer.py before B, C and D (suppose they are newly to database). This commit fix the problem. BTW., why I use collections to record the one whose dependencies are matched, but not directly use layerquery_sorted, it is because collections contains both the ones to be added/updated and the ones in database, but layerquery_sorted only contains the ones to be updated/added. Signed-off-by: Robert Yang <liezhi.yang@windriver.com> Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com> |
||
|---|---|---|
| .. | ||
| migrations | ||
| static | ||
| templatetags | ||
| tools | ||
| __init__.py | ||
| admin.py | ||
| bulkchange.py | ||
| context_processors.py | ||
| forms.py | ||
| layerconfparse.py | ||
| models.py | ||
| querysethelper.py | ||
| recipedesc.py | ||
| recipeparse.py | ||
| restperm.py | ||
| restviews.py | ||
| simplesearch.py | ||
| tasks.py | ||
| update_layer.py | ||
| update.py | ||
| urls_branch.py | ||
| urls.py | ||
| utils.py | ||
| views.py | ||