Release Types Shell Script APT Repository makedeb Package Repository Docker


PKGBUILD Syntax Distro/Architecture Specific Variables Differences from makepkg Comparisons to Other Tools

Using the MPR

Introduction Mist - The MPR CLI Installing Packages Uploading Packages Support Policy


Introduction Getting Started Adding Packages

MPR User Guidelines

Marking Maintainers in a PKGBUILD Package Relationships Using Experimental makedeb Features


Obtaining Support Community Events makedeb Team Ways to Support makedeb Reporting Security Vulnerabilities


The makedeb Package Repository (abbreviated MPR) is a user-maintained repository of build files (PKGBUILDs) that can be built with makedeb and then installed with APT.

The MPR takes its roots in the Arch User Repository, from which the code of the platform was originally conceived.

The MPR was designed to aid users who use makedeb to more easily find and build their favorite packages that might not be in their distribution’s repositories.

The MPR was also made to solve a lingering problem with alternatives such as PPAs: centralization.

With PPAs, you only get a select group of packages with each repository. On top of this, PPAs require adding extra signing keys to your system, can become out of date easily, and can become tedious to deal with when you want to remove them from your system.

Everything in the MPR is inside of a central repository, meaning you don’t have to scour for the packages you want across multiple repositories.

If you want to remove the MPR from your system, there’s also no configuration files to remove. Just uninstall the offending packages, and you’re done.

The MPR also makes it easier for users to start sharing their own packages through the use of the PKGBUILD package format. Other Debian-based build utilities often require configuring multiple files, and require a more complex setup compared to PKGBUILDs, which, in most circumstances, only consists of a single file.