[ansible/gui] Install qt5-webview from AUR for Arch family

[goldyfruit]

Try to make GUI still running on Arch distributions.

Summary by CodeRabbit

• New Features
  • Added support for installing qt5-webview package on Arch-based systems using AUR
• Chores
  • Improved formatting of repository list for better readability

[coderabbitai]

Walkthrough

The pull request introduces a new Ansible task specifically designed for Arch-based Linux systems to install the qt5-webview package from the Arch User Repository (AUR). The task utilizes the kewlfft.aur.aur module and is configured to run with elevated user privileges. The change also includes a minor formatting improvement for repository list readability, maintaining the existing functionality while enhancing visual presentation.

Changes

File	Change Summary
ansible/roles/ovos_installer/tasks/virtualenv/gui.yml	Added AUR package installation task for qt5-webview on Arch systems; improved repository list formatting

Poem

🐰 In Arch's digital garden, a package takes flight,
Qt5-webview, installed with rabbit-like might!
AUR's magic, a task so precise,
Elevating privileges, oh so nice!
A whisker of code, a leap of delight! 🚀

---

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Generate unit testing code for this file.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai generate unit testing code for this file.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read src/utils.ts and generate unit testing code.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai generate docstrings to generate docstrings for this PR. (Beta)
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.

[coderabbitai]

Actionable comments posted: 1

🧹 Nitpick comments (1)

ansible/roles/ovos_installer/tasks/virtualenv/gui.yml (1)

117-123: Document AUR dependency in README

Since this introduces an AUR dependency for Arch-based systems, please update the project's documentation to mention this requirement and any necessary user setup steps.

Let's check if documentation exists:

#!/bin/bash
# Look for relevant documentation files
fd -g "README*" -x grep -l "AUR" {} \;

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 21b411c and 4a97d67.

📒 Files selected for processing (1)

• ansible/roles/ovos_installer/tasks/virtualenv/gui.yml (1 hunks)

⏰ Context from checks skipped due to timeout of 90000ms (1)

• GitHub Check: ansible-lint

🔇 Additional comments (2)

ansible/roles/ovos_installer/tasks/virtualenv/gui.yml (2)

131-145: LGTM! Improved formatting enhances readability

The repository list reformatting makes the code more maintainable while preserving functionality.

---

120-122: Verify AUR helper module availability

The task requires the kewlfft.aur.aur collection. Ensure it's listed in requirements.yml or documented as a prerequisite.

✅ Verification successful

Collection requirement properly documented

The kewlfft.aur collection is correctly listed in requirements.yml with version 0.11.1.

🏁 Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Check if the collection is properly required
fd -g "requirements.yml" -x cat {} \;

Length of output: 276

[goldyfruit]

Closes as well #233