-
Notifications
You must be signed in to change notification settings - Fork 298
apply to become a packager
NOTICE: For Chinese developer, please read the Chinese version, this document may not be up to date with Chinese one
If you would like to join us as a packager, please read the directions in this page.
Here are some basic requirements for every packagers. You should have:
- Enough time to update and maintain your own packages
- Experience with shell scripts, makepkg, PKGBUILD, basic git usage, compiler options, and the ability to look into the package dependencies and error messages.
- Endurance and responsibility. Orphan packages will be dropped within one week from our repo.
Send your application to the following email please:
The formatting of the application
- Who are you, your ID in community and GitHub, your name.
- What can you do for Arch/Linux/Community.
- Your identity information and contact, for example, your job, current city/company/school and so on, and your other reliable contacts. (We would never leak your privacy information to any third-party, we ask these information only for identity verification and assigns responsibilities.
Note
Please attach your SSH public key in the application, if the application pass, you will get the log info about community repo server and compilation server, you need the relevant private key to log the server. Before you upload some packages, make sure that the relevant PKGBUILD is uploaded to the repo already. Take a look at the naming format in the repo: You should create a relevant source directory for every package, and contains PKGBUILD and other files to built it.
lilac.yaml
wiki:
Https://archlinuxcn.github.io/lilac/
build.archlinuxcn.org
's execute sudo cleanup-package-files <pkgname>
to list the files to be deleted, and confirm delete them by adding the --real
parameter.