don't set $EESSI_SILENT

[boegel]

I just spent some time trying to figure out why the EESSI init script was only producing this when using in a GitHub Actions workflow:

Environment set up to use EESSI (2023.06), have fun!

It took me a while to realize that this was because $EESSI_SILENT was set somehow.
And then it took me some more time to figure out what was setting $EESSI_SILENT... :)

I don't see the point for suppressing output produced by the init script in the context of a GitHub Actions workflow, why would we use a different default there than what the init script does?

[ocaisa]

@boegel This has conflicts as you based it off an old commit...but also this is really a personal preference (with mine being different to yours 😛 ).

My plan is actually to move to using the module files for initiating EESSI to add more flexibility and make it optional whether the EESSI module is loaded or not when the action is triggered

[boegel]

@ocaisa Migrating towards using the module makes sense, but we should there probably start supporting $EB_VERBOSE?

I like getting the output, it helps me double-check and catch issue early on.

And especially in GitHub Actions, I think it's useful. A couple of extra lines of output don't exactly get in the way in that environment?

[ocaisa]

You mean implement an EESSI_VERBOSE? This action is more about the EESSI environment than the EasyBuild settings (which I see being handled by EESSI-extend)