AUR Trusted User 导引 (简体中文)

From ArchWiki

Jump to: navigation, search


i18n
English
简体中文
Image:Tango-preferences-desktop-locale.png This page was marked to be translated.
If you understand both "original" and "target" languages of this page, please help complete the translation.

Contents

Trusted User (TU)

Trusted User (TU) 是那些提供 AUR 的社区成员。他们维护热门的包,并且参与管理公共事务的表决。 TU 由现任的 TU 从活跃的社区成员中民主选举产生。 TU 是唯一拥有决定 AUR 发展方向权利的群体。

TU们依靠TUbylaws来管理社区。

TU 职责

TU 和 UNSUPPORTED

TUs 应该努力检查那些被提交到UNSUPPORTED分类中的软件是否含有恶意代码,以及PKGBUILD包是否符合标准。 在UNSUPPORTED中,大约 80% 的PKGBUILD项目非常简单,TU团队可以很快的检查其可用性以及安全性。

TUs 也应该检查一些小错误,建议修改以及改进包。TU 应该努力确认所有的软件包(pkgs)遵循了Arch Packging Guidelines/Standards,为了努力提升发行版本的质量,请将您关于打包的技巧分享给其他打包者。

TUs are also in an excellent position to document recommended practices.

"安全标志(Flag Safe)" 导引

在AUR中有一项新功能将允许TUs给包打上安全标记。不过用户依然有责任自己检查PKGBUILDs。

TU 和 [community], 包维护导引

Accessing the Repo

Follow these instructions for uploading/modifying packages once you have become a TU:

  1. Install the "aurtools" package. Make sure you read the AURtools
  2. You will need to email your the output of "htpasswd -n" to whoever is in charge of the AUR CVS repo ( Paul Mattal = paul@mattal.com ). It comes with Apache.
  3. htpasswd -n <userid>
    
  4. Run the following commands to checkout the AUR CVS:
     export CVSROOT=":pserver:<userid>@cvs.archlinux.org:/home/cvs-community"
     cvs login
     cvs co community
  5. To add a new package:
  6.  cvs add <directory>
     cd <directory>
     cvs add PKGBUILD
    
  7. Make a commit:
  8. cvs commit
    
  9. To upload a binary package:
  10. Please note that AUR password is to be used with tupkg (NOT the CVS password)

    tupkg --user <userid> --password <aur-password> <packagefile.pkg.tar.gz>
    
  11. After uploading a package and committing the build files, tag the files with this command:
  12. cvs tag -cFR CURRENT <newpackagebuilddir>
    

    Package changes should be available within 10 minutes. Verify everything was uploaded properly, then select the newly added or updated package in the web interface and set yourself as the maintainer.

Note: Steps 5-7 can be run with communitypkg in one command as mentioned below in the AURtools tutorial.

Adopting Packages

A TU may adopt any package at any time. But because the TU's time is limited, he should try to only adopt popular packages. The voting mechanism in the AUR allows a TU to quickly gage which packages users want.

A maintainer should adopt his selected package(s) via the web interface. That maintainer is then responsible for bug fixes and new version updates. Packages must be properly cleaned and fixed after adoption.

Disowning packages

You can disown packages by choosing "Disown Packages" in the AUR webinterface. If a TU can't or doesn't want to maintain a package any longer, a notice should be posted to the AUR Mailing List, so another TU can maintain it. A package can still be disowned even if no other TU wants to maintain it, but the TUs should try not to drop many packages (they shouldn't take on more than they have time for). If a package has become obsolete or isn't used any longer, it can be removed completely as well.

If a package has been removed completely, it can be uploaded once again (fresh) to UNSUPPORTED, where a regular user can maintain the package instead of the TU.

Deleting packages from [community]

Removing a package from [community] is easy but not straightforward. After you've removed it from community, you could re-add it to unsupported (make sure to keep a copy!) and orphan it, for adoption by some other user in unsupported.

To remove a package, all you really need to do is remove the CURRENT tag from the PKGBUILD. You do this by doing:

 cvs tag -d CURRENT PKGBUILD

If you wish to remove the package materials from CVS for future revisions (because you don't want the old stuff lying around), you can do the following FROM THE PACKAGE'S DIRECTORY in your checked out version of the community repo (this is very important!):

 cd /path/to/<packagedirname>
 cvs tag -dl CURRENT
 cvs rm -fl
 cvs commit

BE VERY CAREFUL with CVS delete commands! By untagging current on the whole repo you risk removing EVERYTHING in [community]. I've suggested commands that hope to minimize that possibility, but there's still danger where delete is involved. Especially note that the tag delete takes IMMEDIATELY before committing, so be very careful.

Also, due to weirdness of CVS, actually removing the package directory is impossible. It will still show up in a checked out version. This is CVS and we have to live with it, at least for now.

Any TU can remove any package in [community] so keep this in mind and be extra super careful with this ability, lest you accidentally wipe out someone else's package.

AURtools

To help the Trusted Users with their duties, the AURtools were written based on the tupkg tool. If you are Trusted User, it is highly recommended that you use the AURtools.

Personal tools