No variant OS groups matched by update.sh
Open
Beginner friendly
Nobody has claimed this yet.
build process
- Dominant language
- Dockerfile
- Stars
- 8.6k
- Forks
- 2k
- Avg merge
- 10h 19m
- Merged PRs (30d)
- 16
Description
Problem
The update.sh script requires an exact match of the VARIANT option when targeting specific variants. No grouping within operating system families is provided for.
Current matching
| VARIANT | matches | does not match |
|---|---|---|
| alpine | - | alpine3.23 alpine3.24 |
| bullseye | bullseye | bullseye-slim |
| bookworm | bookworm | bookworm-slim |
| trixie | trixie | trixie-slim |
Solution
Suggest to allow grouping by operating system when VARIANT specified with wildcard (*).
Suggested matching
| VARIANT | matches |
|---|---|
| alpine* | alpine3.23 alpine3.24 |
| bullseye* | bullseye bullseye-slim |
| bookworm* | bookworm bookworm-slim |
| trixie* | trixie trixie-slim |
| alpine | - |
| bullseye | bullseye |
| bookworm | bookworm |
| trixie | trixie |
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reading update.sh and locate how the VARIANT option is matched. Use the issue's current and suggested matching tables as acceptance criteria, including wildcard grouping for OS families while preserving exact matching without a wildcard. Verify the behavior against the listed Alpine, Bullseye, Bookworm, and Trixie examples.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, shell
- Domain
- build-system, devops
- Issue type
- Feature
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 72/100