From 71b5b9e6b7e92fe1f2c0c49f47af1c1255f41e24 Mon Sep 17 00:00:00 2001 From: pjmattal Date: Wed, 6 Apr 2005 02:54:11 +0000 Subject: many changes in prep for launch new doc page added changed AUR to community lower-cased unsupported fixed half of the bug with changing categories: categories now can't be changed for packages in community however they can still be changed out from under maintainers by joe users for unsupported packages debugged problem with package details not found when unsupported uploads were with Category 0 (changed default to 19) --- web/html/user_docs.html | 165 ++++++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 165 insertions(+) create mode 100644 web/html/user_docs.html (limited to 'web/html/user_docs.html') diff --git a/web/html/user_docs.html b/web/html/user_docs.html new file mode 100644 index 0000000..15f232b --- /dev/null +++ b/web/html/user_docs.html @@ -0,0 +1,165 @@ + + + + + AUR User Documentation + + +

Arch User Repository (AUR)

+The Arch User Repository (AUR) is ready! This release +does not contain every feature everyone wanted, but at this stage we +think we've implemented the most important features, and we need you to +help us make sure they are working properly and reliably. A few months +after the initial release, we'll start to prioritize +features necessary for the next revision. We'll weigh the suggestions +given and decide what additional features to add.
+

Leave your feedback in Flyspray!

+

Introduction to the AUR
+

+The AUR is a place for community members and TUs (Trusted Users) to +work together to bring new packages to Arch Linux users. A TU is a +special community member who has earned the trust of the core +Arch developers and who wants to help build, test, and debug new Arch +packages contributed by members of the community. Only a TU can build a +binary package and add it to the "community" +repository, which is then accessible via pacman -S.
+
+Any community member may upload new PKGBUILD directory tarballs +from the AUR +web interface. Those packages will appear in the unsupported +repository, and +can be viewed and built by other community members, even though they +are not yet available in binary form via pacman -S.
+
+The AUR system +incorporates a voting system which allows members to vote for the +packages in the unsupported repo that they think are useful or interesting. If +a TU thinks a package is interesting or has received enough votes, +the TU may choose to adopt the package. The TU builds the package, +performs some rudimentary testing, and adds it +to the community repository, where it can be accessed by any user subscribing +to the AUR repository by running pacman -S. From that point on, the TU +will maintain the +package in the community repository, and all updates for the package must go +through a TU.
+
+If a package gets enough votes or is otherwise deemed interesting by +the core Arch development team, the package may be +promoted into the extra or current repository. At that point, the +package is removed from the AUR and is maintained by the core Arch +developers. Alternately, if a TU loses interest in a package, the TU +may abandon the package or remove it from the AUR altogether.
+
+

Feedback

+We will need your feedback. There is a project +set up in Flyspray for the AUR. Please leave your feedback there. +Though it will be tempting to email the AUR developers, remember that +they will get a lot of email and they won't be able to find yours later +when they're going through the feedback. If you put your bugs, +comments, and suggestions in Flyspray, they are guaranteed not to get +lost.
+
+Flyspray is incredibly easy to use. Take a moment to create an account +as soon as you can.
+
+

Using the AUR Repository

+To access the AUR repository from pacman, add the following to your +pacman.conf:
+
+[community]
+ Server = ftp://ftp.archlinux.org/community
+
+

What The AUR Means to a Community Member

+If you're an Arch Linux community member, the AUR represents a giant +step forward in your ability to effectively contribute your work in +building Arch packages to the rest of the Arch Linux community. The +following steps must ye take to get started:
+
    +
  1. Set yourself up to access the community repository, if desired, by +adding the above lines to your pacman.conf.
    +
    2. +
  2. Visit the AUR Site.
    3. +
  3. Create a new user account.
    4. +
  4. Begin uploading packages you have created. You should upload a +.tar.gz file containing the PKGBUILD directory. You should not include +a binary package file in your upload, just the PKGBUILD and related +necessary files for building the package. (Imagine your package had +been accepted into current or extra; we want just the files that would +be fetched by abs in /var/abs.)
    +
    5. +
  5. Review the other packages in the repository, and vote for the +ones you find most interesting. If you're especially interested, browse +the package contents and build other packages yourself.
    6. +
+

What The AUR Means to a Trusted User (TU) or an Arch Developer
+

+If you are an Arch Linux Trusted User (TU) or an Arch developer, and +you want to get started on the beta, do the following:
+
    +
  1. Set your machine up to access the community repository.
    2. +
  2. Run pacman -S tupkg to download the TU package +download tool.
    +
    3. +
  3. Visit the AUR Site.
    4. +
  4. Create a new user account, using your usual user id.
    +
    5. +
  5. Email on the TU or developer email list list and ask to have your login modified to modified to have TU/developer status.
    +This +step is necessary so we can make sure that the right people are getting the right access.
    +
    6. +
  6. Check out the CVS tree for the community repository. To do this, +execute the following commands:
    +
    + # export +CVSROOT=":pserver:<userid>@cvs.archlinux.org:/home/cvs-community"
    +# cvs login
    +# cvs co community
    +
    +If you're +a TU, you should already have an account in this new +repository. If you are a developer, email Jason (jason at archlinux dot +org) and he'll set up access for you.
    +
    7. +
  7. Build binary packages for things you wish to place in the community repo, +and add the PKGBUILD and accompanying necessary files to the CVS +repository. You can do this with:
    +
    + cvs add <directory>
    +cd <directory>
    +cvs add PKGBUILD
    +.
    +.
    +cvs commit
    +
    +
    8. +
  8. Upload the binary packages using the "tupkg" tool. Run:
    +
    +tupkg +--host +subzero.elys.com --user <userid> --password <password> +<packagefile.pkg.tar.gz>
    +
    +Note that this is your AUR login +password -- the one you assign when you create your account, not +your CVS password, in case they are different.
    +
    9. +
  9. Once your packages are uploaded successfully, tag the newly +created package files with the CURRENT tag in cvs. You can do this with:
    +
    +cvs tag -cFR CURRENT <newpackagebuilddir>
    +
    +
    10. +
  10. In 5-10 minutes, the automated script will add them to the community +repository. Verify that they appear both in the web interface and +become +available via pacman -Sy <package> from the community +repository.
    11. +
  11. Select the newly added or updated package in the AUR web +interface and set yourself as the maintainer.
    +
    12. +
+ + -- cgit v1.2.3-70-g09d2