Difference between revisions of "Arch terminology (简体中文)"

From ArchWiki
Jump to: navigation, search
(AUR: Translate.)
(PKGBUILD: Translate.)
Line 41: Line 41:
  
 
==PKGBUILD==
 
==PKGBUILD==
[[PKGBUILD]]s are small scripts that are used to build Arch Linux packages. See [[Creating packages]] for more detail.
+
[[PKGBUILD]] 是编译 Arch Linux 软件包使用的脚本。详情参考 [[Creating packages (简体中文)]].
  
 
==TU, Trusted User==
 
==TU, Trusted User==

Revision as of 06:47, 16 March 2016

Tango-preferences-desktop-locale.png本页面需要更新翻译,内容可能已经与英文脱节。要贡献翻译,请访问简体中文翻译组Tango-preferences-desktop-locale.png

附注: please use the first argument of the template to provide more detailed indications.

本页面试图揭开 Arch Linux 社区术语的神秘面纱。您可以自由的添加或更改任何术语,但是请使用某个章节的编辑选项。如果想添加新术语请按照字母顺序。

Arch Linux

应该用下面术语指代 Arch:

  • Arch Linux
  • Arch (Linux implied)
  • archlinux (UNIX name)

Archlinux、ArchLinux、archLinux、aRcHlInUx 等等称呼都不是标准的。

'Arch' 在 "Arch Linux" 中的官方读音是 /ˈɑrtʃ/ ,就像单词 "archer",或者 "arch-nemesis" 中的读音,但不是在单词 "ark" 或者 "archangel" 中的读音。

ABS

Arch 编译系统 (ABS) 可以:

  • 为没有打包的软件制作软件包
  • 定制/修改已有的软件包,满足您的需求(启用或禁用选项)
  • 用自定义的编译选项编译整个系统,"类似 Gentoo"
  • 让内核模块在自定义内核上工作

ABS 不是必须的,但是很有用。

Arch Linux Archive

Arch Linux Archive (a.k.a ALA), 之前被称为 Arch Linux Rollback Machine (a.k.a ARM), 保存历史上的官方软件仓库快照,ISO 镜像和 boot straps 压缩包。

AUR

Arch用户软件仓库(Arch User Repository,AUR)是为用户而建、由用户主导的Arch软件仓库。AUR中的软件包以软件包生成脚本(PKGBUILD)的形式提供,用户自己通过makepkg生成包,再由pacman安装。创建AUR的初衷是方便用户维护和分享新软件包,并由官方定期从中挑选软件包进入community仓库。本文介绍用户访问和使用AUR的方法。

许多官方仓库软件包都来自AUR。通过AUR,大家相互分享新的软件包生成脚本(PKGBUILD和其他相关文件)。用户还可以为软件包投票。如果一个软件包投票足够多、没有协议问题、打包质量好,那么它就很有希望被收录进官方[community]仓库(以后就可以直接通过pacmanabs 安装了)。

通过这个页面可以访问 AUR。

PKGBUILD

PKGBUILD 是编译 Arch Linux 软件包使用的脚本。详情参考 Creating packages (简体中文).

TU, Trusted User

A trusted user is someone who maintains the AUR and the [community] repository. Trusted Users may move a package into the [community] repository if it has been voted as popular. TUs are appointed by a majority vote by the existing TUs.

Trusted users follow the AUR Trusted User Guidelines and TU by-laws

bbs

Bulletin board system, but in Arch's case, it is just the support forum located here.

community/[community]

The [community] repository is where pre-built packages are made available by Trusted Users. A majority of the packages in [community] come from the AUR.

To access the [community] repository, uncomment it in /etc/pacman.conf.

core/[core]

The [core] repository contains the bare packages needed for an Arch Linux system. [core] has everything needed to get a working command-line system.

custom/user repository

Anyone can create a repository and put it online for other users. To create a repository, you need a set of packages and a pacman-compatible database file for your packages. Host your files online and everyone will be able to use your repository by adding it as a regular repository.

See Custom local repository.

Developer

Half-gods working to improve Arch for no financial gain. Developers are outranked only by our gods, Judd Vinet and Aaron Griffin, who in turn are outranked by tacos.

extra/[extra]

Arch's official package set is fairly streamlined, but we supplement this with a larger, more complete "extra" repository that contains a lot of the stuff that never made it into our core package set. This repository is constantly growing with the help of packages submitted from our strong community. This is where desktop environments, window managers and common programs are found.

initramfs

See mkinitcpio.

initrd

Obsolete. Nowadays often used as a synonym for initramfs.

makepkg

makepkg will build packages for you. makepkg will read the metadata required from a PKGBUILD file. All it needs is a build-capable Linux platform, wget, and some build scripts. The advantage to a script-based build is that you only really do the work once. Once you have the build script for a package, you just need to run makepkg and it will do the rest: download and validate source files, check dependencies, configure the build time settings, build the package, install the package into a temporary root, make customizations, generate meta-info, and package the whole thing up for pacman to use.

namcap

namcap is a package analysis utility that looks for problems with Arch Linux packages or their PKGBUILD files. It can apply rules to the file list, the files themselves, or individual PKGBUILD files.

Rules return lists of messages. Each message can be one of three types: error, warning, or information (think of them as notes or comments). Errors (designated by 'E:') are things that namcap is very sure are wrong and need to be fixed. Warnings (designated by 'W:') are things that namcap thinks should be changed but if you know what you are doing then you can leave them. Information (designated 'I:') are only shown when you use the info argument. Information messages give information that might be helpful but is not anything that needs changing.

package

A package is an archive containing

  • all of the (compiled) files of an application
  • metadata about the application, such as application name, version, dependencies, ...
  • installation files and directives for pacman
  • (optionally) extra files to make your life easier, such as a start/stop script

Arch's package manager pacman can install, update, and remove those packages. Using packages instead of compiling and installing programs yourself has various benefits:

  • easily updatable: pacman will update existing packages as soon as updates are available
  • dependency checks: pacman handles dependencies for you, you only need to specify the program and pacman installs it together with every other program it needs
  • clean removal: pacman has a list of every file in a package. This way, no files are left behind when you decide to remove a package.
Note: Different GNU/Linux distributions use different packages and package managers, meaning that you cannot use pacman to install a Debian package on Arch.

Package maintainer

The role of the package maintainer is to update packages as new versions become available upstream and to field support questions relating to bugs in said packages. The term may be applied to any of the following:

  • A core Arch Linux developer who maintains a software package in one of the official repositories (core, extra, or testing).
  • A Trusted User of the community who maintains software packages in the unsupported/unofficial community repository.
  • A normal user who maintains a PKGBUILD and local source files in the AUR.

The maintainer of a package is the person currently responsible for the package. Previous maintainers should be listed as contributors in the PKGBUILD along with others who have contributed to the package.

pacman

The pacman package manager is one of the great highlights of Arch Linux. It combines a simple binary package format with an easy-to-use build system (see ABS). Pacman makes it possible to easily manage and customize packages, whether they be from the official Arch repositories or the user's own creations. The repository system allows users to build and maintain their own custom package repositories, which encourages community growth and contribution (see AUR).

Pacman can keep a system up to date by synchronizing package lists with the master server, making it a breeze for the security-conscious system administrator to maintain. This server/client model also allows you to download/install packages with a simple command, complete with all required dependencies (similar to Debian's apt-get).

NB: Pacman was written by Judd Vinet, the creator of Arch Linux. It is used as a package management tool by other distributions as well, such as FrugalWare, Rubix, UfficioZero (in Italy, based on Ubuntu), and, of course, Arch based distributions such as Archie and AEGIS.

pacman.conf

This is the configuration file of pacman. It is located in /etc. For a full explanation of its powers, type this at the command line:

man pacman.conf

repository/repo

The repository has the pre-compiled packages of one or (usually) more PKGBUILDs. Official repositories are

  • [core]: containing the latest version of packages required for a full CLI system
  • [extra]: containing the latest version of packages not needed for a working system but are needed for an enjoyable system ;)
  • [community]: containing packages that came from AUR and got enough user votes

Pacman uses these repositories to search for packages and install them. A repository can be local (i.e. on your own computer) or remote (i.e. the packages are downloaded before they are installed).

RTFM

"Read The Fucking (or Fine) Manual". This simple message is replied to a lot of new Linux/Arch users who ask about the functionality of a program when it is clearly defined in the program's manual.

It is often used when a user fails to make any attempt to find a solution to the problem themselves. If someone tells you this, they are not trying to offend you; they are just frustrated with your lack of effort.

The best thing to do if you are told to do this is to read the manual page.

  • To read the program manual page for a particular program, type this at the command line:
man PROGRAM-NAME

where PROGRAM-NAME is the name of the program you need more information about.

If you do not find the answer to your question in the program manual, there are more ways to find the answer. You can:

taurball

The tarballed PKGBUILD and local source files that are required by makepkg to create an installable binary package. The name is derived from the practice of uploading such tarballs to the AUR, hence "tAURball".

testing/[testing]

This is the repository where major packages/updates to packages are kept prior to release into the main repositories, so they can be bug tested and upgrade issues can be found. It is disabled by default but can be enabled in /etc/pacman.conf

udev

udev provides a dynamic device directory containing only the files for actually present devices. It creates or removes device node files in the /dev directory, or it renames network interfaces.

Usually udev runs as udevd(8) and receives uevents directly from the kernel if a device is added/removed to/from the system.

If udev receives a device event, it matches its configured rules against the available device attributes provided in sysfs to identify the device. Rules that match may provide additional device information or specify a device node name and multiple symlink names and instruct udev to run additional programs as part of the device event handling.

wiki

This! A place to find documentation about Arch Linux. Anyone can add and modify the documentation.