ANACONDA_EVENT.CON(5)

💖 NAME 💖

okay bestie, welcome to anaconda_event.conf(5) — the LIBREPORT MANUAL page for the configuration file of libreport. It’s giving “little file, big workflow energy” ✨

anaconda_event.conf — configuration file for libreport. periodt. 💅

✨ DESCRIPTION ✨

So this configuration file is basically the matchmaker: it specifies which of the reporting work flow definitions are applicable for particular problem data for problems in the anaconda package. Lowkey iconic.

All applicable reporting work flows are presented to users in the User Interface as possibilities for processing a particular problem in the anaconda package. yup, the UI shows them off 🫶

This configuration file consists of one condition per line. one line = one condition, no cap.

Each condition line must start with EVENT=workflow_NAME, where workflow_ is the constant prefix and workflow_NAME is the base name of the path to the reporting work flow configuration file. That prefix is not decorative, bestie — it’s required 👑

The rest of the condition line has the form VAR=VAL, VAR!=VAL, or VAL~=REGEX, where VAR is the name of a problem directory element to be checked (for example, "executable", "package", hostname", etc.). The condition may consist of as many element checks as it is necessary — stack those checks like friendship bracelets 🌈

🌸 EXAMPLES 🌸

Condition line:

EVENT=workflow_Anaconda component=anaconda

The condition line above expects the existence of /usr/share/libreport/workflows/workflow_Anaconda.xml. slay, path confirmed 💖

🦋 SEE ALSO 🦋

• report-gtk(1) — the other page to check out, iykyk.

👑 AUTHOR 👑

• ABRT team — the authors, the moment, the legends.

---

mwah 💋 — this page is from LIBREPORT 2.17.15, dated 07/15/2024. bye bestie 🫶✨