You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Originally posted by arjunsuresh November 5, 2024
Currently CM script meta is not having an option to update env variables based on some conditions and these updates need to happen in customize.py. This works fine for small scripts but for generic scripts like get-generic-python-lib this increases the complexity of the code in customize.py.
Any deps can update a ENV variables - for example detect-cpu can set CPU_ARCHITECTURE as x86 and if get-generic-sys-util has selected a package say X we can update the installation source for X on x86 in _cm.yml itself if we can have the below construct.
Discussed in #482
Originally posted by arjunsuresh November 5, 2024
Currently CM script meta is not having an option to update env variables based on some conditions and these updates need to happen in customize.py. This works fine for small scripts but for generic scripts like
get-generic-python-lib
this increases the complexity of the code in customize.py.Any
deps
can update a ENV variables - for exampledetect-cpu
can setCPU_ARCHITECTURE
asx86
and ifget-generic-sys-util
has selected a package sayX
we can update the installation source forX
onx86
in_cm.yml
itself if we can have the below construct.Here, we can use
skip_if_env
,enable_if_env
,skip_if_any_env
andenable_if_any_env
which we currently use to conditionally turn on dependencies.The text was updated successfully, but these errors were encountered: