AUR Beta

From b23b51fbbd3c84a493a68da8c88bde8807c894bc Mon Sep 17 00:00:00 2001 From: eliott Date: Fri, 19 Oct 2007 19:55:31 -0700 Subject: Removed beta.html Seems old. --- web/html/beta.html | 192 ----------------------------------------------------- 1 file changed, 192 deletions(-) delete mode 100644 web/html/beta.html (limited to 'web') diff --git a/web/html/beta.html b/web/html/beta.html deleted file mode 100644 index b1b48ac4..00000000 --- a/web/html/beta.html +++ /dev/null @@ -1,192 +0,0 @@ - - - - - AUR Beta - - -

Arch User Repository (AUR) Beta Test

-The Arch User Repository (AUR) is ready for beta testing. 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!

Audience

-For this test, we are not using the real Arch servers or -network bandwidth. As a result, you will find that -bandwidth will be somewhat limited. Please don't upload many large -packages, except where doing so helps to test a particular feature (or -misfeature) of the system.
-
-We expect this beta testing to be performed by TUs and a -handful of other users who are interested enough to subscribe to the TU -mailing list or otherwise seek out this information. Please do not advertise this beta site -information widely; we will not have the network -bandwidth to sustain a high load on the test platform and will need to -cut the beta short. -Once the beta is over, the real AUR will be hosted on the main Arch -Linux -servers and will be able to handle the greater demands of the whole -community.
-
-

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 AUR -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 "Unsupported" 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 AUR 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 AUR 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 -developers. Alternately, if a TU loses interest in a package, the TU -may abandon the package or remove it from the AUR repository altogether.
-
-

Feedback

-The most important part of this beta test is 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.
-
-

Schedule

-The AUR beta is starts now, around February 23. It should run until -about the first week in March. At that point, it will look at the remaining -problems, fix them, and launch the AUR sometime in mid-to-late March on the -production servers.
-

Using the AUR Repository

-To access the AUR repository from pacman, add the following to your -pacman.conf:
-
-

[aur]

-Server = ftp://subzero.elys.com/arch/aur

-
-

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:
-

Set yourself up to access the AUR repository, if desired, by -adding the above lines to your pacman.conf.
-
Visit the AUR Beta Site.
Create a new user account.
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.)
-
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.

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:
-

Set your machine up to access the AUR repository.
Run pacman -S tupkg to download the TU package -download tool.
-
Visit the AUR Beta Site.
Create a new user account, using your usual user id.
-
Email Paul (paul at mattal dot com) and ask to have your login -modified to have TU/developer status.
-This -step is necessary so we can make sure that the right people are getting -the right access. We will migrate this information to the production -system, so you won't have to do it again.
-
Check out the CVS tree for the AUR repository. To do this, -execute the following commands:
-
- export -CVSROOT=":pserver:<userid>@cvs.archlinux.org:/home/cvs-aur-test" -cvs login -cvs co aur-test
-
-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.
-
Build binary packages for things you wish to place in the AUR, -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
-
-
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.
-
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>
-
-
In 5-10 minutes, the automated script will add them to the AUR -repository. Verify that they appear both in the web interface and -become -available via pacman -Sy <package> from the aur -repository.
Select the newly added or updated package in the AUR web -interface and set yourself as the maintainer.
-

- - -- cgit v1.2.3-24-g4f1b