Old packages will be automatically deleted on the server, so you need not worry about removing them yourself. Be careful to add real binary packages and not symlinks or any other file that may deceive you.

Old packages will be automatically deleted on the server, so you need not worry about removing them yourself. Be careful to add real binary packages and not symlinks or any other file that may deceive you.

Packaging

Getting Started

Anyone and everyone keen on contributing to the buildscripts (PKGBUILDs and related files) can start immediately. You only have to take the time to get in touch with either schivmeister or jonkristian with a password hash. The fastest way is to log on to IRC (#archaudio@Freenode) and look for them, but a more straightforward approach is to simply e-mail them directly:

Password Hashing

Simply enter a username and password, select either SHA-1 or MD5 (up to you), then click on "encrypt password". The output is what we want.

Or if you prefer an offline method:

htpasswd -cs hashForArchAudio.txt $preferred_username # you need to install 'apache' for this tool

In this example, the file 'hashForArchAudio.txt' will be created with your new password hash. Either send the file itself or copy the hash (the whole line). Don't worry, you're only sharing the cryptographic hash of your password - and not the password itself - so that you can be authenticated.

Buildscript Contributor

Binary Contributor

It is mandatory that you be well-acquainted with Arch Linux packaging before applying to become a (binary) packager. If you maintain packages in AUR you are on the right path.

The only difference here is that you have to do a second, non-recursive checkout for the private packages area, where the binaries are contained and pushed. Although Subversion will not track this directory, we're going to keep it under the main checkout for the sake of consistency. We've already made the necessary amendments so that SVN does not display the '?' symbol as the directory's status:

So you would navigate to the proper repository and architecture directory, copy the (binary) package that you built, add it to SVN, and finally commit the addition. Optionally, you may clear out the directory again to maintain the 'sparseness':

Old packages will be automatically deleted on the server, so you need not worry about removing them yourself. Be careful to add real binary packages and not symlinks or any other file that may deceive you.

Subversion Maintenance

It is always a good idea to make the following sanity checks a routine: