Moving to GetSolusThis document walks the end user through moving their developer related tooling and repositories over to GetSolus (dev.getsol.us).
Package Inclusion PolicyThis policy sets forth the criteria for a package to be accepted for inclusion into the Solus repositories or rejected.
Package.ymlAll packages consist of a single build file, which provides all of the required metadata for the package manager, plus the build steps involved to produce a package. This follows the YAML specification.
Packaging PracticesThe primary goal of ypkg is ease of maintenance. In order to do so we ensure packages in the binary repository adhere to a strict set of conventions and practices.
Release ProcessesThis post is intended as both information to users, and guidelines for developers and contributors of Solus. Solus employs a formal architecture to enable the curated rolling release model, which is made possible through the use of ferryd, solbuild and a split-repository model.
Requesting a PackagePackages are how users install Software in Solus, however if we are missing one you can let us know using our Task Tracker.
Requesting a Package Update Packages updates are typically provided by community or dedicated package maintainers, however if we are not shipping the latest stable release of a package, you can let us know using our Task Tracker
Submitting the PackageThis article will walk you through submitting a patch for a package for review and inclusion in the Solus repository.