jan/feature/20260608-app-get-libname-don-t-use-get-proj-refs into master | Author | SHA1 | Message | Date | |
|---|---|---|---|---|
3f47abb29a
|
App.get_libname(): Don't use get_proj_refs()
All checks were successful
CI / Packaging - Kali Linux (pull_request) Successful in 3m16s
CI / Packaging - OpenSUSE Tumbleweed (pull_request) Successful in 3m12s
CI / Packaging test (pull_request) Successful in 0s
CI / Packaging - Kali Linux (push) Successful in 3m17s
CI / Packaging - OpenSUSE Tumbleweed (push) Successful in 3m18s
CI / Packaging test (push) Successful in 0s
App.get_projects_refs() is a versatile tool, but what it does isn't obvious. Use the simpler method .get_value() instead for get_libname(), and return None if a project doesn't provide a linkable library. This is similar to fix Signed-off-by: Jan Lindemann <jan@janware.com> |
|||
|
c538447cc5
|
App.__get_project_refs(): Code beautification
In __get_project_refs(): - Rename variable dep and deps to val and vals, respectively,
because that's more what they are values of key-value pairs. In
some cases that can represent dependencies, in some case other
things. - Make a scope case distinction a little clearer by mentioning all
possible cases in a match / case block Signed-off-by: Jan Lindemann <jan@janware.com> |