locker: ensure correct handling of extras export
Previously, when determining nested dependencies, the check for activated extras/features of top level dependencies were done after the nested dependencies were processed. This lead to exports containing in active extras. This change resolves this by pre-selecting top level packages prior to identifying nested dependencies. (cherry picked from commit 2b6f82e9494b99bdb04d0dac90f87eb23548e4a5)
Showing
Please
register
or
sign in
to comment