From 9c004010e3251d8d1b4f7430db22d3d721623577 Mon Sep 17 00:00:00 2001 From: simo Date: Wed, 8 Jun 2005 01:00:24 +0000 Subject: Committing New AUR Guidelines from Ben --- web/html/guidelines.html | 267 ++++++++++++++++++++++++++++++++--------------- 1 file changed, 185 insertions(+), 82 deletions(-) (limited to 'web/html') diff --git a/web/html/guidelines.html b/web/html/guidelines.html index 47f64e41..b3aa520a 100644 --- a/web/html/guidelines.html +++ b/web/html/guidelines.html @@ -1,19 +1,16 @@ - +AUR Guidelines + + + + + - - - AUR Guidelines - - - -

AUR Guidelines

-
April 15, 2005
-
1.0.2
+
Jun 08, 2005
+
1.1.0
Ben Mazer @@ -44,8 +41,7 @@
  • Adding a TU
  • Removing a TU
  • Other Duties
    • - -
  • Guidelines for Package Maintenance +
  • Guidelines for Package Maintenance
    1. Accessing the Repo
    2. Adopting a package
      3. @@ -53,118 +49,225 @@
    3. Packaging Etiquette
    • - - + + + +
  • Frequently Asked Questions
    • +

    Purpose

    - The AUR is a community of Arch users, where packages outside of the core Arch distribution are maintained. The AUR Community Repo is a supplement to the EXTRA and CURRENT repositories; less popular packages will be maintained as a service to the general Arch-using population. Packages in the AUR will depend on EXTRA and CURRENT.

    - The AUR was created to lift the burden on the developers. They should be allowed to focus on adding new features, rather than doing the mundane job of package maintenance. Therefore, all packages start inside the AUR, and as developers consider them crucial to the distribution, they will be adopted into EXTRA/CURRENT. The AUR was also created to allow easy participation. Arch is completely volunteer-based, and needs help from its users. Lastly, the AUR helps to further the Arch philosophy of KISS. The Arch Core (EXTRA/CURRENT/UNSTABLE) is a complete distribution, but it does not attempt to provide every single package. The AUR helps by maintaining less popular packages; but the AUR also follows KISS, and only popular packages from UNSUPPORTED will make it into the official AUR repository. -

    + The AUR +is a community of Arch users, where packages outside of the core Arch +distribution are maintained. The AUR Community Repo is a supplement to +the EXTRA and CURRENT repositories; less popular packages will be +maintained as a service to the general Arch-using population. Packages +in the AUR will depend on EXTRA and CURRENT.

    The AUR was +created to lift the burden on the developers. They should be allowed to +focus on adding new features, rather than doing the mundane job of +package maintenance. Therefore, all packages start inside the AUR, and +as developers consider them crucial to the distribution, they will be +adopted into EXTRA/CURRENT. The AUR was also created to allow easy +participation. Arch is completely volunteer-based, and needs help from +its users. Lastly, the AUR helps to further the Arch philosophy of +KISS. The Arch Core (EXTRA/CURRENT/UNSTABLE) is a complete +distribution, but it does not attempt to provide every single package. +The AUR helps by maintaining less popular packages; but the AUR also +follows KISS, and only popular packages from UNSUPPORTED will make it +into the official AUR repository.

    The User

    +

    Users of the +AUR can do many things, the main function being to download and use +packages. One can access the AUR by adding this to their pacman.conf +file:

    + [community]
    Server = ftp://ftp.archlinux.org/community/os/i686/

    +But a user can also help with package maintenance, by: submitting +packages (and then maintaining them while they remain in UNSUPPORTED), +filing bug reports, reporting out-of-date packages, helping with other +user-submitted PKGBUILDs, and voting for packages that should be +maintained by the TUs. Once a user account has been created, all +functions can be performed inside the web interface.

    Submitting Packages

    - Users of the AUR can do many things, the main function being to download and use packages. One can access the AUR by adding this to their pacman.conf file:

    - [community]
    Server = ftp://ftp.archlinux.org/community/os/i686/

    - - But a user can also help with package maintenance, by: submitting packages (and then maintaining them while they remain in UNSUPPORTED), filing bug reports, reporting out-of-date packages, helping with other user-submitted PKGBUILDs, and voting for packages that should be maintained by the TUs. Once a user account has been created, all functions can be performed inside the web interface. -

    Submitting Packages

    -

    - Inside the web interface, a user can submit a tarball (tar.gz) of a directory containing build files for a package. The directory inside the tarball should contain a PKGBUILD, any .install files, patches, etc (no binaries). Examples of what a directory looks like can be seen inside /var/abs.

    +Inside the web interface, a user can submit a tarball (tar.gz) of a +directory containing build files for a package. The directory inside +the tarball should contain a PKGBUILD, any .install files, patches, etc +(no binaries). Examples of what a directory looks like can be seen inside /var/abs.

    When submitting a package, observe the following rules: -