Package request: revisit distrobox inclusion
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 35/100
- Issue type
- Feature
- Clarity
- Needs clarification
- Activity status
- Active
- Domain
- tooling
Research direction
Review the upstream distrobox project and the package requirements stated in this issue, then read the earlier requests in #36341 and #50512 to understand why inclusion was rejected. Done means establishing whether the request now meets the repository's requirements and whether package inclusion should proceed.
Written by the indexing model from the issue text.
Description
Package name
distrobox
Package homepage
https://github.com/89luca89/distrobox
Description
Hello, can this be reconsidered? I have both my own container runtime and podman, but when doing certain experiments, it would really be useful to just quickly "distrobox stuff".
Dristobox minimizes lot of podman spelunking and other unproductive and lost time. Especially when you are not running "app containers" but are using containers for dev and research purposes.
According to my research distrobox wraps podman so the deps should be minimal, if podman is already present...
Distrobox request was originally rejected in #36341and #50512. I am creating 3rd issue, because normal users don't have right to reopen old issues.
Does the requested package meet the package requirements?
Compiled, System
Is the requested package released?
Yes
- Dominant language
- Shell
- Stars
- 3.5k
- Forks
- 2.8k
- Avg merge
- 1d 23h
- Merged PRs (30d)
- 325
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing 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.
More from void-linux/void-packages
-
bug needs-testing
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
void-linux/void-packages#63249 · 3 comments ·
Maintainers usually reply within 1 day
-
xmlto: sources no longer available from upstreamPossibly taken @L1TerminalFault claimed this 5 days ago. Openbug needs-testing
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
void-linux/void-packages#63237 ·
Maintainers usually reply within 1 day
-
AI 🤖 bug needs-testing
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
void-linux/void-packages#63041 · 1 comment ·
Maintainers usually reply within 1 day
-
request
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
void-linux/void-packages#63016 ·
Maintainers usually reply within 1 day
-
nextcloud-client: VFS plugins installed where the client does not searchMay be free again A pull request for this issue was closed without being merged. Openbug needs-testing
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
void-linux/void-packages#62700 ·
Maintainers usually reply within 1 day
All issues in void-linux/void-packages
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
danielmiessler/LifeOS#2567 ·
Maintainers usually reply within 9 days
-
area:docs documentation good first issue priority:medium
Difficulty 1/5 Under an hour Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
PostHog/posthog-js#5524 ·
Maintainers usually reply within 2 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
paperclipai/paperclip#18671 ·
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day