From fc40fc4ce14baf42045e506975cb720e20c3e796 Mon Sep 17 00:00:00 2001 From: Kevin Mihelich Date: Mon, 8 Apr 2013 21:43:43 -0600 Subject: [PATCH] Update README.md --- README.md | 20 ++++++++++++-------- 1 file changed, 12 insertions(+), 8 deletions(-) diff --git a/README.md b/README.md index 854ea03f4..26ed4759b 100644 --- a/README.md +++ b/README.md @@ -1,4 +1,4 @@ -# pkgbuilds.git - README - 2012-12-03 +# pkgbuilds.git - README - 2013-04-08 This repository hosts [PKGBUILDs](https://wiki.archlinux.org/index.php/PKGBUILD) that have been modified from the upstream [Arch Linux](http://archlinux.org) release in order @@ -11,9 +11,9 @@ http://archlinuxarm.org ## Layout -New packages should be placed in the correct locations, with the packages base +New packages should be placed in the correct locations, with the package's base folder name reflecting the 'pkgname' for single-package PKGBUILDs, or 'pkgbase' -for multiple-package PKGBUILDs. In the case of non-alarm packages, naming +for multiple-package PKGBUILDs. In the case of non-ALARM packages, naming should exactly match the base folder or package name as used upstream or in the AUR, respectively. This will ensure correct package->version matching in the build system update routines. @@ -31,28 +31,32 @@ feel belong within the scope of these repos. ### aur Contains a selection of packages from the [AUR](https://aur.archlinux.org/ -"Arch User Repository") that have been requested by the community to be +"Arch User Repository") that have been highly requested by the community to be pre-compiled and easily installed. However, you're free to use the AUR just as you would on Arch, and we have included Yaourt to compile and install directly from AUR (`yaourt -AS packagename`). ### alarm -Contains packages we have created or have been submitted to us, to enable +Contains packages we have created or have been submitted to us to enable functionality on ARM systems in use by the community. These are our own or have changed significantly enough from upstream or AUR to no longer qualify as being in those respective locations here. ##Custom PKGBUILD variables for the build system +These variables are used to help control the build system used by Arch Linux +ARM, and are not a part of the official PKGBUILD specification. ### noautobuild If non-zero, the build system will mark the package as done and not build it -for any architecture. +for any architecture. This should not be employed in regular use, and requires +access to a non-public interface for getting built packages into the repos. ### buildarch A bitmask of architectures to build the package for. This must be set to the -decimal equivalent of the bitmask (the number in parenthesis). -Sub-architectures must be specifically requested, they won't build by default. +decimal equivalent of the bitmask (the number in parenthesis). The values can +be combined (bitwise AND) to select more than one architecture. Without being +specified, the package will build for all architectures. * `0000 0001` (1) = *the default*, package will be built for all architectures * `0000 0010` (2) = the package will be built only for armv5