RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

+++ This bug was initially created as a clone of Bug #1031009 +++

This bug is a bit related to bug #1029795, so see there for backgroud.

It seems like the only documentation about using generic actions other than "enable" right now is probably the only thing what scl(1) says:
"<action> is a script name to execute in a bash environment before the application itself takes in executed. Currently only enable scriptlet is mandatory which is needed to update search paths, etc."

This is really not what scl command does right now. Bug #1029795 tried to fix the behaviour in order to correspond with such documentation, but it is actually a change of behaviour. Until it is fixed (if at all), we should change the documentation to correspond with the current status, how the things actually work.

Particularly, according to the scl(1) man page, other actions shouldn't enable SCL environment, but in reality X_SCLS is adjusted for every action now. So I guess something like the following can be in the documentation when describing what "scl <action> <collection1> [<collection2> ...] <command>" actually does:
 * marks specified collection(s) as enabled
 * executes the script, which is expected to set proper environment
 * executes the command in the end

Please, also ensure that help will be aligned with the current behaviour. It's mostly the same issue there.