Difference between revisions of "Arch User Repository (正體中文)"

From ArchWiki
Jump to: navigation, search
(新建頁面)
 
Line 35: Line 35:
 
{{Related articles end}}
 
{{Related articles end}}
  
The Arch User Repository (AUR) is a community-driven repository for Arch users. It contains package descriptions ([[PKGBUILD]]s) that allow you to compile a package from source with [[makepkg]] and then install it via [[pacman]]. The AUR was created to organize and share new packages from the community and to help expedite popular packages' inclusion into the [[#community|community]] repository. This document explains how users can access and utilize the AUR.
+
Arch 使用者軟體倉庫 (AUR) 是由社群推動的使用者軟體庫。它包含了軟體包描述單 ([[PKGBUILD]]),可以用 [[makepkg]] 從原始碼編譯軟體包,並透過 [[pacman (正體中文)|Pacman]] 安裝。
 +
透過 AUR 可以在社群間分享、組織新進軟體包,熱門的軟體包有機會被收錄進 [[#community|community]] 軟體庫。這份文件將解釋如何存取、使用 AUR。
  
A good number of new packages that enter the official repositories start in the AUR.  In the AUR, users are able to contribute their own package builds (PKGBUILD and related files). The AUR community has the ability to vote for or against packages in the AUR.  If a package becomes popular enough — provided it has a compatible license and good packaging technique — it may be entered into the ''community'' repository (directly accessible by [[pacman]] or [[ABS|abs]]).
+
官方軟體庫中有不少發跡於 AUR 的新軟體包。在 AUR 下,使用者可以貢獻自己的軟體包組建資料 (PKGBUILD 與相關檔案)。AUR 社群可以投票支持/反對 AUR 的軟體包。若一個軟體包變得熱門 — 加上授權相容和優良的打包技術 — 就有機會被收錄進 ''community'' 軟體庫 (可直接透過 [[pacman (正體中文)|Pacman]] [[Arch Build System (正體中文)|ABS]] 存取)
  
 
== 入門知識 ==
 
== 入門知識 ==
  
Users can search and download PKGBUILDs from the [https://aur.archlinux.org AUR Web Interface]. These PKGBUILDs can be built into installable packages using [[makepkg]], then installed using pacman
+
使用者可以從 [https://aur.archlinux.org AUR 網路介面]搜尋並下載各種軟體的 PKGBUILD。使用 [[makepkg]] 可以將這些 PKGBUILD 組建成軟體包,並使用 pacman 安裝。
  
* Ensure the {{Grp|base-devel}} group package is installed ({{ic|pacman -S --needed base-devel}}).
+
* 確定已經安裝 {{Grp|base-devel}} 群組的軟體包 ({{ic|pacman -S --needed base-devel}})
* Read the remainder of this article for more info and a short tutorial on installing AUR packages.
+
* 本文後面的章節有更多相關資訊,以及安裝 AUR 軟體包的簡短教學。
* Visit the [https://aur.archlinux.org AUR Web Interface] to inform yourself on updates and happenings. There you will also find statistics and an up-to-date list of newest available packages available in AUR.
+
* 有關 AUR 軟體的升級與相關事件,請至 [https://aur.archlinux.org AUR 網頁介面]。您可以在那裡找到統計數據和 AUR 可用軟體包的最新清單。
* Glance over the [[#FAQ]] for answers to the most common questions.
+
* 常見問題請參考 [[#FAQ]]
* You may wish to adjust {{ic|/etc/makepkg.conf}} to better optimize for your processor prior to building packages from the AUR.  A significant improvement in compile times can be realized on systems with multi-core processors by adjusting the MAKEFLAGS variable. Users can also enable hardware-specific optimizations in GCC via the CFLAGS variable.  See [[makepkg.conf]] for more information.
+
* 在組建 AUR 軟體包之前,可以考慮調整 {{ic|/etc/makepkg.conf}},讓編譯器能針對您的處理器作效能優化。多核處理器的系統可以調整 MAKEFLAGS 變數,這樣編譯效率可以獲得明顯提升。使用者也可以透過 CFLAGS 變數來啟用 GCC 對特定硬體的優化。更多資訊請參閱 [[makepkg.conf]]
  
 
== 歷史 ==
 
== 歷史 ==
Line 59: Line 60:
 
== 搜尋 ==
 
== 搜尋 ==
  
The AUR web interface can be found [https://aur.archlinux.org/ here], and an interface suitable for accessing the AUR from a script (for example) can be found [https://aur.archlinux.org/rpc.php here].
+
AUR 網頁介面請到[https://aur.archlinux.org/ 這裡], and an interface suitable for accessing the AUR from a script (for example) can be found [https://aur.archlinux.org/rpc.php here].
  
 
Queries search package names and descriptions via a MySQL LIKE comparison. This allows for more flexible search criteria (e.g. try searching for {{ic|tool%like%grep}} instead of {{ic|tool like grep}}). If you need to search for a description that contains {{ic|%}}, escape it with {{ic|\%}}.
 
Queries search package names and descriptions via a MySQL LIKE comparison. This allows for more flexible search criteria (e.g. try searching for {{ic|tool%like%grep}} instead of {{ic|tool like grep}}). If you need to search for a description that contains {{ic|%}}, escape it with {{ic|\%}}.
Line 77: Line 78:
 
[[AUR Helpers]] add seamless access to the AUR. They vary in their features but can ease in searching, fetching, building, and installing from PKGBUILDs found in the AUR. All of these scripts can be found in the AUR.
 
[[AUR Helpers]] add seamless access to the AUR. They vary in their features but can ease in searching, fetching, building, and installing from PKGBUILDs found in the AUR. All of these scripts can be found in the AUR.
  
{{Warning|There is not and will never be an ''official'' mechanism for installing build material from the AUR. '''All AUR users should be familiar with the build process.'''}}
+
{{警告|There is not and will never be an ''official'' mechanism for installing build material from the AUR. '''All AUR users should be familiar with the build process.'''}}
  
 
=== 預備條件 ===
 
=== 預備條件 ===
Line 97: Line 98:
 
For more information on ABS read the [[Arch Build System]] article. The example will use {{ic|~/builds}} as the build directory.
 
For more information on ABS read the [[Arch Build System]] article. The example will use {{ic|~/builds}} as the build directory.
  
=== 獲取組建用檔案 ===
+
=== 獲取組建檔案 ===
  
 
Locate the package in the AUR. This is done using the search feature (text field at the top of the [https://aur.archlinux.org/ AUR home page]). Clicking the application's name in the search list brings up an information page on the package. Read through the description to confirm that this is the desired package, note when the package was last updated, and read any comments.
 
Locate the package in the AUR. This is done using the search feature (text field at the top of the [https://aur.archlinux.org/ AUR home page]). Clicking the application's name in the search list brings up an information page on the package. Read through the description to confirm that this is the desired package, note when the package was last updated, and read any comments.
Line 131: Line 132:
 
=== 安裝軟體包 ===
 
=== 安裝軟體包 ===
  
Install the package using pacman.  A tarball should have been created named:
+
使用 pacman 安裝軟體包。A tarball should have been created named:
  
 
  <''application name''>-<''application version number''>-<''package revision number''>-<''architecture''>.pkg.tar.xz
 
  <''application name''>-<''application version number''>-<''package revision number''>-<''architecture''>.pkg.tar.xz
Line 228: Line 229:
  
 
{{FAQ
 
{{FAQ
|question=What is the AUR?
+
|question=什麼是 AUR?
 
|answer=The AUR (Arch User Repository) is a place where the Arch Linux community can upload [[PKGBUILD]]s of applications, libraries, etc., and share them with the entire community. Fellow users can then vote for their favorites to be moved into the ''community'' repository to be shared with Arch Linux users in binary form.}}
 
|answer=The AUR (Arch User Repository) is a place where the Arch Linux community can upload [[PKGBUILD]]s of applications, libraries, etc., and share them with the entire community. Fellow users can then vote for their favorites to be moved into the ''community'' repository to be shared with Arch Linux users in binary form.}}
  
 
{{FAQ
 
{{FAQ
|question=What kind of packages are permitted on the AUR?
+
|question=AUR 許可什麼類型的軟體包?
 
|answer=The packages on the AUR are merely "build scripts", i.e. recipes to build binaries for pacman. For most cases, everything is permitted, subject to the abovementioned usefulness and scope guidelines, as long as you are in compliance with the licensing terms of the content. For other cases, where it is mentioned that "you may not link" to downloads, i.e. contents that are not redistributable, you may only use the file name itself as the source. This means and requires that users already have the restricted source in the build directory prior to building the package. When in doubt, ask.}}
 
|answer=The packages on the AUR are merely "build scripts", i.e. recipes to build binaries for pacman. For most cases, everything is permitted, subject to the abovementioned usefulness and scope guidelines, as long as you are in compliance with the licensing terms of the content. For other cases, where it is mentioned that "you may not link" to downloads, i.e. contents that are not redistributable, you may only use the file name itself as the source. This means and requires that users already have the restricted source in the build directory prior to building the package. When in doubt, ask.}}
  
 
{{FAQ
 
{{FAQ
|question=How can I vote for packages in AUR?
+
|question=我要如何投票給 AUR 軟體包?
 
|answer=Sign up on the [https://aur.archlinux.org/ AUR website] to get a "Vote for this package" option while browsing packages.}}
 
|answer=Sign up on the [https://aur.archlinux.org/ AUR website] to get a "Vote for this package" option while browsing packages.}}
  
 
{{FAQ
 
{{FAQ
|question=What is a TU?
+
|question=什麼是 TU?
 
|answer=A [[AUR Trusted User Guidelines|TU (Trusted User)]] is a person who is chosen to oversee AUR and the ''community'' repository. They are the ones who maintain popular PKGBUILDs in ''community'', and overall keep the AUR running.}}
 
|answer=A [[AUR Trusted User Guidelines|TU (Trusted User)]] is a person who is chosen to oversee AUR and the ''community'' repository. They are the ones who maintain popular PKGBUILDs in ''community'', and overall keep the AUR running.}}
  
 
{{FAQ
 
{{FAQ
|question=What is the difference between the Arch User Repository and ''community''?
+
|question=Arch 使用者倉庫和 ''community'' 的不同?
 
|answer=The Arch User Repository is where all PKGBUILDs that users submit are stored, and must be built manually with [[makepkg]]. When PKGBUILDs receive enough community interest and the support of a TU, they are moved into the ''community'' repository (maintained by the TUs), where the binary packages can be installed with [[pacman]].}}
 
|answer=The Arch User Repository is where all PKGBUILDs that users submit are stored, and must be built manually with [[makepkg]]. When PKGBUILDs receive enough community interest and the support of a TU, they are moved into the ''community'' repository (maintained by the TUs), where the binary packages can be installed with [[pacman]].}}
  
 
{{FAQ
 
{{FAQ
|question=How many votes does it take to get a PKGBUILD into ''community''?
+
|question=要多少個投票推薦才會讓 PKGBUILD 進入 ''community''
 
|answer=Usually, at least 10 votes are required for something to move into ''community''. However, if a TU wants to support a package, it will often be found in the repository.}}
 
|answer=Usually, at least 10 votes are required for something to move into ''community''. However, if a TU wants to support a package, it will often be found in the repository.}}
  
 
{{FAQ
 
{{FAQ
|question=How do I make a PKGBUILD?
+
|question=如何建立一份 PKGBUILD?
 
|answer=The best resource is [[Creating Packages]]. Remember to look in AUR before creating the PKGBUILD as to not duplicate efforts.}}
 
|answer=The best resource is [[Creating Packages]]. Remember to look in AUR before creating the PKGBUILD as to not duplicate efforts.}}
  
 
{{FAQ
 
{{FAQ
|question=I'm trying to run "pacman -S foo"; it is not working but I know it is in ''community''
+
|question=我確定 "foo" ''community'' 庫,可是執行 "pacman -S foo" 卻失敗了。
 
|answer=You probably have not enabled ''community'' in your {{ic|/etc/pacman.conf}}. Just uncomment the relevant lines.
 
|answer=You probably have not enabled ''community'' in your {{ic|/etc/pacman.conf}}. Just uncomment the relevant lines.
 
If ''community'' is enabled in your {{ic|/etc/pacman.conf}} try running {{ic|pacman -Syu}} first to synchronize the pkgcache and update your system before trying to install ''foo'' again.}}
 
If ''community'' is enabled in your {{ic|/etc/pacman.conf}} try running {{ic|pacman -Syu}} first to synchronize the pkgcache and update your system before trying to install ''foo'' again.}}
  
 
{{FAQ
 
{{FAQ
|question=Foo in AUR is outdated; what do I do?
+
|question=AUR 的某個軟體已經過期,我該怎麼做?
 
|answer=For starters, you can flag packages out-of-date. If it stays out-of-date for an extended period of time, the best thing to do is email the maintainer. If there is no response from the maintainer after two weeks, you could send mail to the aur-general mailing list to have a TU orphan the PKGBUILD if you are willing to maintain it yourself. When we are talking about a package which is flagged out of date for more than 3 months and is in general not updated for a long time, please add this in your orphan request.}}
 
|answer=For starters, you can flag packages out-of-date. If it stays out-of-date for an extended period of time, the best thing to do is email the maintainer. If there is no response from the maintainer after two weeks, you could send mail to the aur-general mailing list to have a TU orphan the PKGBUILD if you are willing to maintain it yourself. When we are talking about a package which is flagged out of date for more than 3 months and is in general not updated for a long time, please add this in your orphan request.}}
  
 
{{FAQ
 
{{FAQ
|question=I have a PKGBUILD I would like to submit; can someone check it to see if there are any errors?
+
|question=我打算提交一份 PKGBUILD,有沒有好心人可以幫忙檢查有沒有錯誤?
 
|answer=If you would like to have your PKGBUILD critiqued, post it on the aur-general mailing list to get feedback from the TUs and fellow AUR members. You could also get help from the [[ArchChannel|IRC channel]], #archlinux on irc.freenode.net. You can also
 
|answer=If you would like to have your PKGBUILD critiqued, post it on the aur-general mailing list to get feedback from the TUs and fellow AUR members. You could also get help from the [[ArchChannel|IRC channel]], #archlinux on irc.freenode.net. You can also
 
use [[namcap]] to check your PKGBUILD and the resulting package for errors.}}
 
use [[namcap]] to check your PKGBUILD and the resulting package for errors.}}
  
 
{{FAQ
 
{{FAQ
|question=Foo in AUR does not compile when I run makepkg; what should I do?
+
|question=我從 AUR 下載某個軟體,執行 makepkg 卻無法編譯;我該怎麼做?
 
|answer=You are probably missing something trivial.
 
|answer=You are probably missing something trivial.
  
Line 281: Line 282:
  
 
{{FAQ
 
{{FAQ
|question=How can I speed up repeated build processes?
+
|question=重復性的組建過程有什麼方法可以加速?
 
|answer=If you frequently compile code that uses gcc - say, a git or SVN package - you may find [[ccache]], short for "compiler cache", useful.}}
 
|answer=If you frequently compile code that uses gcc - say, a git or SVN package - you may find [[ccache]], short for "compiler cache", useful.}}
  
Line 289: Line 290:
  
 
{{FAQ
 
{{FAQ
|question=How can I upload to AUR without using the web interface?
+
|question=如何在不使用網頁介面的情況下上傳資料至 AUR?
 
|answer=You can use {{pkg|burp}}, {{AUR|aurploader}} or {{AUR|aurup}} &mdash; these are command-line programs.}}
 
|answer=You can use {{pkg|burp}}, {{AUR|aurploader}} or {{AUR|aurup}} &mdash; these are command-line programs.}}
  

Revision as of 04:13, 27 January 2014

Arch 使用者軟體倉庫 (AUR) 是由社群推動的使用者軟體庫。它包含了軟體包描述單 (PKGBUILD),可以用 makepkg 從原始碼編譯軟體包,並透過 Pacman 安裝。 透過 AUR 可以在社群間分享、組織新進軟體包,熱門的軟體包有機會被收錄進 community 軟體庫。這份文件將解釋如何存取、使用 AUR。

官方軟體庫中有不少發跡於 AUR 的新軟體包。在 AUR 下,使用者可以貢獻自己的軟體包組建資料 (PKGBUILD 與相關檔案)。AUR 社群可以投票支持/反對 AUR 的軟體包。若一個軟體包變得熱門 — 加上授權相容和優良的打包技術 — 就有機會被收錄進 community 軟體庫 (可直接透過 PacmanABS 存取)。

入門知識

使用者可以從 AUR 網路介面搜尋並下載各種軟體的 PKGBUILD。使用 makepkg 可以將這些 PKGBUILD 組建成軟體包,並使用 pacman 安裝。

  • 確定已經安裝 base-devel 群組的軟體包 (pacman -S --needed base-devel)。
  • 本文後面的章節有更多相關資訊,以及安裝 AUR 軟體包的簡短教學。
  • 有關 AUR 軟體的升級與相關事件,請至 AUR 網頁介面。您可以在那裡找到統計數據和 AUR 可用軟體包的最新清單。
  • 常見問題請參考 #FAQ
  • 在組建 AUR 軟體包之前,可以考慮調整 /etc/makepkg.conf,讓編譯器能針對您的處理器作效能優化。多核處理器的系統可以調整 MAKEFLAGS 變數,這樣編譯效率可以獲得明顯提升。使用者也可以透過 CFLAGS 變數來啟用 GCC 對特定硬體的優化。更多資訊請參閱 makepkg.conf

歷史

The following items are listed for historical purposes only. They have since been superseded by the AUR and are no longer available.

At the beginning, there was ftp://ftp.archlinux.org/incoming, and people contributed by simply uploading the PKGBUILD, the needed supplementary files, and the built package itself to the server. The package and associated files remained there until a Package Maintainer saw the program and adopted it.

Then the Trusted User Repositories were born. Certain individuals in the community were allowed to host their own repositories for anyone to use. The AUR expanded on this basis, with the aim of making it both more flexible and more usable. In fact, the AUR maintainers are still referred to as TUs (Trusted Users).

搜尋

AUR 網頁介面請到這裡, and an interface suitable for accessing the AUR from a script (for example) can be found here.

Queries search package names and descriptions via a MySQL LIKE comparison. This allows for more flexible search criteria (e.g. try searching for tool%like%grep instead of tool like grep). If you need to search for a description that contains %, escape it with \%.

軟體包安裝

Installing packages from the AUR is a relatively simple process. Essentially:

  1. Acquire the tarball which contains the PKGBUILD and possibly other required files, like systemd-units and patches (but often not the actual code).
  2. Extract the tarball (preferably in a folder set aside just for builds from the AUR) with tar -xzf foo.tar.gz.
  3. Run makepkg in the directory where the files are saved (makepkg -s will automatically resolve dependencies with pacman). This will download the code, compile it and pack it.
  4. Look for a README file in src/, as it might contain information needed later on.
  5. Install the resulting package with pacman:
# pacman -U /path/to/pkg.tar.xz

AUR Helpers add seamless access to the AUR. They vary in their features but can ease in searching, fetching, building, and installing from PKGBUILDs found in the AUR. All of these scripts can be found in the AUR.

警告: There is not and will never be an official mechanism for installing build material from the AUR. All AUR users should be familiar with the build process.

預備條件

First ensure that the necessary tools are installed. The package group base-devel should be sufficient; it includes make and other tools needed for compiling from source.

警告: Packages in the AUR assume the base-devel group is installed, and AUR packages will not list members of this group as dependencies even if the package cannot be built without them. Please ensure this group is installed before complaining about failed builds.
# pacman -S --needed base-devel

Next choose an appropriate build directory. A build directory is simply a directory where the package will be made or "built" and can be any directory. Examples of commonly used directories are:

~/builds

or if using ABS (the Arch Build System):

/var/abs/local

For more information on ABS read the Arch Build System article. The example will use ~/builds as the build directory.

獲取組建檔案

Locate the package in the AUR. This is done using the search feature (text field at the top of the AUR home page). Clicking the application's name in the search list brings up an information page on the package. Read through the description to confirm that this is the desired package, note when the package was last updated, and read any comments.

Download the necessary build files by clicking on the "Download tarball" link under "Package actions" on the right hand side. This file should be saved to the build directory or otherwise copied to the directory after downloading. In this example, the file is called "foo.tar.gz" (standard format is pkgname.tar.gz, if it has been properly submitted).

Alternatively you can download the tarball from the terminal, changing directories to the build directory first:

$ cd ~/builds
$ curl -O https://aur.archlinux.org/packages/fo/foo/foo.tar.gz

組建軟體包

Change directories to the build directory if not already there, then extract the previously downloaded package:

$ cd ~/builds
$ tar -xvzf foo.tar.gz

This should create a new directory called "foo" in the build directory.

Warning: Carefully check all files. cd to the newly created directory and carefully check the PKGBUILD and any .install file for malicious commands. PKGBUILDs are bash scripts containing functions to be executed by makepkg: these functions can contain any valid commands or Bash syntax, so it is totally possible for a PKGBUILD to contain dangerous commands through malice or ignorance on the part of the author. Since makepkg uses fakeroot (and should never be run as root), there is some level of protection but you should never count on it. If in doubt, do not build the package and seek advice on the forums or mailing list.
$ cd foo
$ nano PKGBUILD
$ nano foo.install

Make the package. After manually confirming the integrity of the files, run makepkg as a normal user.

$ makepkg -s

The -s switch will use sudo to install any needed dependencies. If the use of sudo is undesirable, manually install required dependencies beforehand and exclude the -s in the above command.

安裝軟體包

使用 pacman 安裝軟體包。A tarball should have been created named:

<application name>-<application version number>-<package revision number>-<architecture>.pkg.tar.xz

This package can be installed using pacman's "upgrade" command:

# pacman -U foo-0.1-1-i686.pkg.tar.xz   

These manually installed packages are called foreign packages — packages which have not originated from any repository known to pacman. To list all foreign packages:

$ pacman -Qm 
Note: The above example is only a brief summary of the package building process. A visit to the makepkg and ABS pages will provide more detail and is highly recommended, especially for first-time users.

回饋

The AUR Web Interface has a comments facility that allows users to provide suggestions and feedback on improvements to the PKGBUILD contributor. Avoid pasting patches or PKGBUILDs into the comments section: they quickly become obsolete and just end up needlessly taking up lots of space. Instead email those files to the maintainer, or even use a pastebin.

One of the easiest activities for all Arch users is to browse the AUR and vote for their favourite packages using the online interface. All packages are eligible for adoption by a TU for inclusion in community repository, and the vote count is one of the considerations in that process; it is in everyone's interest to vote!

軟體包分享與維護

Users can share PKGBUILDs using the Arch User Repository. It does not contain any binary packages but allows users to upload PKGBUILDs that can be downloaded by others. These PKGBUILDs are completely unofficial and have not been thoroughly vetted, so they should be used at your own risk.

提交軟體包

警告: Before attempting to submit a package you are expected to familiarize yourself with Arch Packaging Standards and all articles, mentioned at the bottom of it.

After logging in to the AUR web interface, a user can submit a gzipped tarball (.tar.gz) of a directory containing build files for a package. The directory inside the tarball should contain a PKGBUILD, .AURINFO, any .install files, patches, etc. (absolutely no binaries). Examples of what such a directory should look like can be seen inside /var/abs if the Arch Build System was installed.

The tarball can be created with the following command:

$ makepkg --source

Note that this is a gzipped tarball; assuming you are uploading a package called libfoo, when you create the file it should look similar to this:

$ tar tf libfoo-0.1-1.src.tar.gz
libfoo/
libfoo/PKGBUILD
libfoo/libfoo.install

When submitting a package, observe the following rules:

  • Check the official package database for the package. If any version of it exists, do not submit the package. If the official package is out-of-date, flag it as such. If the official package is broken or is lacking a feature, then please file a bug report.
  • Check the AUR for the package. If it is currently maintained, changes can be submitted in a comment for the maintainer's attention. If it is unmaintained, the package can be adopted and updated as required. Do not create duplicate packages.
  • Verify carefully that what you are uploading is correct. All contributors must read and adhere to the Arch Packaging Standards when writing PKGBUILDs. This is essential to the smooth running and general success of the AUR. Remember that you are not going to earn any credit or respect from your peers by wasting their time with a bad PKGBUILD.
  • Packages that contain binaries or that are very poorly written may be deleted without warning.
  • If you are unsure about the package (or the build/submission process) in any way, submit the PKGBUILD to the AUR mailing list or the AUR forum on the Arch forums for public review before adding it to the AUR.
  • Make sure the package is useful. Will anyone else want to use this package? Is it extremely specialized? If more than a few people would find this package useful, it is appropriate for submission.
  • The AUR and official repositories are intended for packages which install generally software and software-related content, including one or more of the following: executable(s); config file(s); online or offline documentation for specific software or the Arch Linux distribution as a whole; media intended to be used directly by software.
  • Gain some experience before submitting packages. Build a few packages to learn the process and then submit.
  • If you submit a package.tar.gz with a file named package in it you will get an error: "Could not change to directory /home/aur/unsupported/package/package". To resolve this, rename the file named package to something else; for example, package.rc. When it is installed in the pkg directory, you may rename it back to package.

維護軟體包

  • If you maintain a package and want to update the PKGBUILD for your package just resubmit it.
  • Check for feedback and comments from other users and try to incorporate any improvements they suggest; consider it a learning process!
  • Please do not just submit and forget about packages! It is the maintainer's job to maintain the package by checking for updates and improving the PKGBUILD.
  • If you do not want to continue to maintain the package for some reason, disown the package using the AUR web interface and/or post a message to the AUR Mailing List.

其他要求

  • Disownment requests and removal requests go to the aur-general mailing list for Trusted Users and other users to decide upon.
  • Include package name and URL to AUR page, preferably with a footnote [1].
  • Disownment requests will be granted two weeks after the current maintainer has been contacted by email and did not react.
  • Package merging has been implemented, users still have to resubmit a package under a new name and may request merging of the old version's comments and votes on the mailing list.
  • Removal requests require the following information:
    • Package name and URL to AUR page
    • Reason for deletion, at least a short note
      Notice: A package's comments does not sufficiently point out the reasons why a package is up for deletion. Because as soon as a TU takes action, the only place where such information can be obtained is the aur-general mailing list.
    • Include supporting details, like when a package is provided by another package, if you are the maintainer yourself, it is renamed and the original owner agreed, etc.

Removal requests can be disapproved, in which case you will likely be advised to disown the package for a future packager's reference.

community 庫

The community repository, maintained by Trusted Users, contains the most popular packages from the AUR. It is enabled by default in /etc/pacman.conf. If community has been disabled or removed, it can be enabled by uncommenting or adding these two lines:

/etc/pacman.conf
...
[community]
Include = /etc/pacman.d/mirrorlist
...

This repository, unlike the AUR, contains binary packages that can be installed directly with pacman and the build files can also be accessed with the ABS. Some of these packages may eventually make the transition to the core or extra repositories as the developers consider them crucial to the distribution.

Users can also access the community build files by editing /etc/abs.conf and enabling the community repository in the REPOS array.

Git 庫

A Git Repo of the AUR is maintained by Thomas Dziedzic providing package history among other things. It is updated at least once a day. To clone the repository (several hundred MB):

$ git clone git://pkgbuild.com/aur-mirror.git

More informations: Web interface, forum thread.

FAQ

Template:FAQ

Template:FAQ

Template:FAQ

Template:FAQ

Template:FAQ

Template:FAQ

Template:FAQ

Template:FAQ

Template:FAQ

Template:FAQ

Template:FAQ

Template:FAQ

Template:FAQ

Template:FAQ

另請參閱