As the title suggested, I was talking about the issue that the CLI arguments are not working. So this issue is a specific occurrence of #3998 (when using redshift).

Otherwise, I’ll reach out to you once it’s merged into master 😃

Yes, perfect! Let us look into the CLI arguments afterwards.

To make such issues easier to debug

💖

redshift will only work in a very limited manner.

Maybe we should even fail. I don’t think anyone wants to have software where CLI arguments do not work.

@markus2330 I believe this was caused by missing dependencies on your system! To make such issues easier to debug, I have:

• improved the usability of redshift to provide more helpful info messages during execution and more details about problems.
• extended CONTRIBUTING.md to make clearer, that without installing the dependencies, redshift will only work in a very limited manner.

I’ll get back to you on this issue (and ask you to retest) once #3998 is closed!

@markus2330 I’m reposting my questions here, looking forward to your response!

Unfortunately, I’m having trouble reproducing that when specification is properly mounted. Could you please provide more information?

1. Does src/redshift -v (lower-case v -> verbose) and other CLI options like --fade work?

2. What is the output of …

• src/redshift --elektra-spec
• src/redshift --help
• kdb ls spec:/sw/redshift/#0/current/
• kdb meta-show spec:/sw/redshift/#0/current/version
• kdb meta-show /sw/redshift/#0/current/version
• kdb get /sw/redshift/#0/current/version ?

1. Maybe your build contains a broken specification (see https://github.com/jonls/redshift/pull/837#discussion_r706612067). Could you please pull my latest changes with the fix and then unmount both mointpoints, make distclean, bootstrap, configure, make, execute redshift-conf.mount.sh (and optionally make install) and finally src/redshift -v.