devenv: Add a c10s version

[cgwalters]

Let's make this one a possible option too.

[gemini-code-assist]

Summary of Changes

Hello @cgwalters, I'm Gemini Code Assist¹! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request significantly enhances the development environment by introducing a CentOS Stream 10 option, alongside the existing Debian setup. This change provides greater flexibility for developers, allowing them to choose their preferred Linux distribution for the development container. The underlying build system has been refactored to support these distinct environments, ensuring a clear separation and maintainability of dependencies and configurations for each base OS.

Highlights

• New CentOS Stream 10 Devenv: Introduced a new development environment based on CentOS Stream 10 (c10s), providing an alternative to the existing Debian-based setup.
• Justfile Updates: The Justfile has been updated to include specific build targets for both Debian (devenv-build-debian) and CentOS Stream 10 (devenv-build-c10s) devenv images, with devenv-build now defaulting to the Debian version.
• Refactored Containerfiles and Package Lists: The existing Debian devenv configuration has been moved to devenv/Containerfile.debian, devenv/packages-debian.txt, and devenv/build-deps-debian.txt. Corresponding new files (devenv/Containerfile.c10s, devenv/packages-c10s.txt, devenv/build-deps-c10s.txt) have been added for the CentOS Stream 10 environment.
• Dockerignore Adjustments: The .dockerignore file was modified to explicitly include the newly introduced Debian and CentOS Stream 10 specific package and build dependency list files, ensuring they are available during image builds.

Ignored Files

• Ignored by pattern: .github/workflows/** (1)
  • .github/workflows/build-devcontainer.yml

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature	Command	Description
Code Review	/gemini review	Performs a code review for the current pull request in its current state.
Pull Request Summary	/gemini summary	Provides a summary of the current pull request in its current state.
Comment	@gemini-code-assist	Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help	/gemini help	Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩

[gemini-code-assist]

Code Review

This pull request introduces a CentOS Stream 10 version of the development environment, complementing the existing Debian-based one. The changes are well-structured, with new Containerfiles for each distribution and updated Justfile targets. My review includes a few suggestions to improve the shell scripting within the new container files for better maintainability and clarity.