Skip to content

CONTRIBUTING.md: be more explicit about some of our packaging reqts #60353

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
classabbyamp wants to merge 2 commits into
base: master
Choose a base branch
from
Open

CONTRIBUTING.md: be more explicit about some of our packaging reqts #60353

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
7c2ad9a
CONTRIBUTING.md: be more explicit about some of our packaging reqts
classabbyamp May 3, 2026
05d7d63
fixup! CONTRIBUTING.md: be more explicit about some of our packaging …
classabbyamp May 3, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 6 additions & 0 deletions CONTRIBUTING.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -27,6 +27,9 @@ Such forks require heavy patching, maintenance and hours of build time.

Software need to be used in version announced by authors as ready to use by the general public - usually called releases.
Betas, arbitrary VCS revisions, templates using tip of development branch taken at build time and releases created by the package maintainer won't be accepted.
Software should have an established and mature release history. New projects or those with an excessively frequent release cadence are not good candidates for system packages.

Packages should be submitted by someone other than the developer of the software, though exceptions can be made for established contributors if the software meets other requirements.

## Creating, updating, and modifying packages in Void by yourself

Expand Down Expand Up @@ -73,6 +76,9 @@ Templates must have the name `void-packages/srcpkgs/<pkgname>/template`, where `

For deeper insights on the contents of template files, please read the [manual](./Manual.md), and be sure to browse the existing template files in the `srcpkgs` directory of this repository for concrete examples.

To ensure packages stay maintained, we prefer that they are submitted by those with a history of contributions to existing packages.
Comment thread
classabbyamp marked this conversation as resolved.
A good way to do this is to work on orphaned packages (those maintained by `orphan@voidlinux.org`) that you use.

### Updating a template

At minimum, a template update will consist of changing `version` and `checksum`, if there was an upstream version change, and/or `revision`, if a template-specific change (e.g. patch, correction, etc.) is needed.
Expand Down