https://wiki.archlinux.org/api.php?action=feedcontributions&user=Demyze&feedformat=atomArchWiki - User contributions [en]2024-03-28T10:15:28ZUser contributionsMediaWiki 1.41.0https://wiki.archlinux.org/index.php?title=Talk:Users_and_groups&diff=264637Talk:Users and groups2013-06-28T20:53:49Z<p>Demyze: /* Empty? */</p>
<hr />
<div>== Wheel ==<br />
<br />
Where did the name "wheel" come from and why? - [[User:KitchM|KitchM]] 11:25, 9 March 2010 (EST)<br />
:Really old question, but for anyone curious http://unix.stackexchange.com/questions/1262/where-did-the-wheel-group-get-its-name/1271#1271 [[User:Demyze|Demyze]] ([[User talk:Demyze|talk]]) 20:51, 28 June 2013 (UTC)<br />
<br />
== Group of Groups? ==<br />
<br />
Would it be possible to make a group of groups? So one could have an admin group that has other groups like optical, video, etc. --[[User:Matthewbauer|Matthewbauer]] 16:35, 18 April 2010 (EDT)<br />
<br />
== Empty? ==<br />
<br />
Is it possible to have an empty group? In other words, can a group have no members? If so, why do they exist? If not, why do they exist? Let's address these issues in the wiki. Thanks. - [[User:KitchM|KitchM]] 17:10, 26 April 2010 (EDT)<br />
:A group is just a group, it doesn't belong to users. Empty groups exists to restrict permissions to only certain users, even if there's not yet any users who have said permission it's useful to have a list of groups for programs to know about. [[User:Demyze|Demyze]] ([[User talk:Demyze|talk]]) 20:53, 28 June 2013 (UTC)</div>Demyzehttps://wiki.archlinux.org/index.php?title=Talk:Users_and_groups&diff=264636Talk:Users and groups2013-06-28T20:51:39Z<p>Demyze: /* Wheel */ forgot to sign..</p>
<hr />
<div>== Wheel ==<br />
<br />
Where did the name "wheel" come from and why? - [[User:KitchM|KitchM]] 11:25, 9 March 2010 (EST)<br />
:Really old question, but for anyone curious http://unix.stackexchange.com/questions/1262/where-did-the-wheel-group-get-its-name/1271#1271 [[User:Demyze|Demyze]] ([[User talk:Demyze|talk]]) 20:51, 28 June 2013 (UTC)<br />
<br />
== Group of Groups? ==<br />
<br />
Would it be possible to make a group of groups? So one could have an admin group that has other groups like optical, video, etc. --[[User:Matthewbauer|Matthewbauer]] 16:35, 18 April 2010 (EDT)<br />
<br />
== Empty? ==<br />
<br />
Is it possible to have an empty group? In other words, can a group have no members? If so, why do they exist? If not, why do they exist? Let's address these issues in the wiki. Thanks. - [[User:KitchM|KitchM]] 17:10, 26 April 2010 (EDT)</div>Demyzehttps://wiki.archlinux.org/index.php?title=Talk:Users_and_groups&diff=264635Talk:Users and groups2013-06-28T20:51:12Z<p>Demyze: /* Wheel */</p>
<hr />
<div>== Wheel ==<br />
<br />
Where did the name "wheel" come from and why? - [[User:KitchM|KitchM]] 11:25, 9 March 2010 (EST)<br />
:Really old question, but for anyone curious http://unix.stackexchange.com/questions/1262/where-did-the-wheel-group-get-its-name/1271#1271<br />
<br />
== Group of Groups? ==<br />
<br />
Would it be possible to make a group of groups? So one could have an admin group that has other groups like optical, video, etc. --[[User:Matthewbauer|Matthewbauer]] 16:35, 18 April 2010 (EDT)<br />
<br />
== Empty? ==<br />
<br />
Is it possible to have an empty group? In other words, can a group have no members? If so, why do they exist? If not, why do they exist? Let's address these issues in the wiki. Thanks. - [[User:KitchM|KitchM]] 17:10, 26 April 2010 (EDT)</div>Demyzehttps://wiki.archlinux.org/index.php?title=Talk:Canon_CAPT&diff=243651Talk:Canon CAPT2013-01-13T01:20:45Z<p>Demyze: /* systemd */ new section</p>
<hr />
<div>There is a new version for the Linux_CAPT_PrinterDriver, at least for the lbp-3200 printer, V240:<br />
http://www.canon.es/Support/Consumer_Products/products/printers/Laser/LBP-3200.aspx?DLtcmuri=tcm:86-846500&page=1&type=download<br />
<br />
<br />
<br />
== Requirements ==<br />
<br />
lib32-heimdal does not exist in the official repos neither in the aur.--[[User:Simbioz|Simbioz]] ([[User talk:Simbioz|talk]]) 12:59, 4 November 2012 (UTC)<br />
<br />
== systemd ==<br />
<br />
Needs to be updated for systemd --[[User:Demyze|Demyze]] ([[User talk:Demyze|talk]]) 01:20, 13 January 2013 (UTC)</div>Demyzehttps://wiki.archlinux.org/index.php?title=Unofficial_user_repositories/Repo-ck&diff=240396Unofficial user repositories/Repo-ck2012-12-15T12:25:38Z<p>Demyze: Moved AUR note for global BFQ to the global section</p>
<hr />
<div>[[Category:Kernel]]<br />
{{Article summary start}}<br />
{{Article summary text|<br />
Article details setup and usage of the an unofficial Arch Linux repo containing generic and CPU-optimized kernel and support packages containing the ck1 patchset featuring the Brain Fuck Scheduler by Con Kolivas.}}<br />
{{Article summary heading|Related}}<br />
{{Article summary wiki|Linux-ck}} - Main article.<br />
{{Article summary wiki|Linux-ck/Changelog}} - Linux-ck Changelog.<br />
{{Article summary wiki|http://repo-ck.com/stats.pdf Repo Statistics}} - Popularity of packages, # of downloads, etc.<br />
{{Article summary end}}<br />
<br />
== TL; DR Summary ==<br />
'''Packages Provided:'''<br />
*{{AUR|linux-ck}} - Kernel and headers.<br />
*{{AUR|nvidia-ck}} - Matched nVidia modules.<br />
*{{AUR|nvidia-304xx-ck}} - Matched nVidia legacy modules.<br />
*{{AUR|broadcom-wl-ck}} - Matched broadcom-wl modules.<br />
*{{AUR|virtualbox-ck-modules}} - Matched virtualbox-host and virtualbox-guest modules.<br />
<br />
'''CPU-Optimized Flavors:'''<br />
*Generic - Any x86_64 or i686 CPU.<br />
*Atom - Optimized packages for Intel Atom CPUs.<br />
*Core2 - Optimized packages for Intel C2D/C2Q CPUs.<br />
*Nehalem - Optimized packages for First Generation Intel Core i3/i5/i7 CPUs.<br />
*Sandybridge - Optimized packages for Second Generation Intel Core i3/i5/i7 CPUs.<br />
*Ivybridge - Optimized packages for Third Generation Intel Core i3/i5/i7 CPUs.<br />
*P4 - Optimized packages for Intel Pentium 4 CPUs.<br />
*Pentm - Optimized packages for Intel Pentium-M CPUs.<br />
*Kx - Optimized packages for AMD K7/K8/K10 CPUs.<br />
*Barcelona - Optimized packages for AMD Barcelona CPUs.<br />
*Bulldozer - Optimized packages for AMD Bulldozer CPUs.<br />
*Piledriver - Optimized packages for AMD Piledriver CPUs.<br />
<br />
'''Setup:'''<br />
See the [[Repo-ck#Setup]] section below to enable and use the repo.<br />
<br />
== Details ==<br />
The repo contains generic packages as well as CPU-specific packages. Many ARCH users are familiar with the concept of a generic kernel package. The official ARCH kernel is available in two flavors (either i686 or x86_64) which are ''generic'' packages in that i686 will work with ''any'' compatible x86 CPU and x86_64 will work with ''any'' compatible x86_64 CPU.<br />
<br />
Users have a choice between the corresponding generic linux-ck packages or CPU-specific and optimized linux-ck packages:<br />
<br />
''GENERIC''<br />
*'''ck-generic''' ==> Compiled with generic optimizations suitable for ''any'' compatible CPU just like the official ARCH linux package. This is true for both Intel and AMD processors.<br />
<br />
''CPU SPECIFIC AND OPTIMIZED''<br />
*'''ck-atom''' ==> Intel Atom platform specific optimizations. Intel Atom CPUs have an in-order pipelining architecture and thus can benefit from accordingly optimized code.<br />
*'''ck-core2''' ==> Intel Core 2-family including Dual and Quads (Core 2/Newer Xeon/Mobile Celeron based on Core2).<br />
*'''ck-nehalem''' ===> Intel 1st Generation Core i3/i5/i7-family specific optimizations.<br />
*'''ck-sandybridge''' ==> Intel 2nd Generation Core i3/i5/i7-family specific optimizations.<br />
*'''ck-ivybridge''' ==> Intel 3rd Generation Core i3/i5/i7-family specific optimizations.<br />
*'''ck-p4''' ==> Intel Pentium-4 specific optimizations (P4/P4-based Celeron/Pentium-4 M/Older Xeon).<br />
*'''ck-pentm''' ==> Intel Pentium-M specific optimizations (Pentium-M notebook chips/not Pentium-4 M).<br />
*'''ck-kx''' ==> AMD K7 (Athlon/Athlon XP)/K8 (Athlon 64, Athlon 64 X2, 23xx Quad-Core Barcelona, Sempron, Sempron 64)/K10-family (Athlon X2 7x50, Phenom X3/X4, Phenom II, Athlon II X2/X3/X4, Sempron 64 [Socket AM3 only], 61xx Eight-Core Magny-Cours) specific optimizations. Enables use of some extended instructions, and passes appropriate optimization flags to GCC.<br />
*'''ck-barcelona''' ==> AMD Barcelona CPUs.<br />
*'''ck-bulldozer''' ==> Optimized packages for AMD Bulldozer CPUs.<br />
*'''ck-piledriver''' ==> Optimized packages for AMD Piledriver CPUs.<br />
<br />
CPU-specific optimization are invoked at compilation by selecting the corresponding option under '''Processor type and features>Processor family''' or by setting-up the .config file accordingly. These changes setup make specific gcc options including the $CFLAGS. <br />
<br />
{{Note|Repo packages include the BFQ I/O Scheduler compiled as a module. Read the [[#How_to_Enable_the_BFQ_I.2FO_Scheduler|section]] below for instructions to load it and enable it should you wish to do so.}}<br />
<br />
[[http://pgp.mit.edu:11371/pks/lookup?op=get&search=0x6D605D846176ED4B Graysky's public key]] used for package signing. Pacman v4 will automatically query the public key server, but if users would rather download and manually add the key, do so from the link.<br />
<br />
== Setup ==<br />
1) Add the following to {{ic|/etc/pacman.conf}} (I placed my entry at the bottom of the file):<br />
<br />
[repo-ck]<br />
SigLevel = PackageRequired<br />
Server = http://repo-ck.com/$arch<br />
<br />
To sign graysky's key, do the following:<br />
# pacman-key -r 5EE46C4C<br />
# pacman-key --lsign-key 5EE46C4C<br />
<br />
2) Refresh via ''pacman -Syy''<br />
<br />
That's it. To see the contents of the repo, just search as such:<br />
<br />
$ pacman -Sl repo-ck<br />
<br />
== Installation Examples ==<br />
Use the '''ck-X''' group and select the desired packages for installation. There are 6 groups corresponding to the 12 package sets: '''ck-generic, ck-atom, ck-core2, ck-nehalem, ck-sandybridge, ck-ivybridge, ck-p4, ck-pentm, ck-kx, ck-barcelona, ck-bulldozer, ck-piledriver'''<br />
<br />
{{bc|1=# pacman -S ck-generic<br />
:: There are 7 members in group ck-generic:<br />
:: Repository repo-ck<br />
1) broadcom-wl-ck 2) linux-ck 3) linux-ck-headers 4) nvidia-304xx-ck 5) nvidia-ck<br />
6) virtualbox-ck-guest-modules 7) virtualbox-ck-host-modules<br />
<br />
Enter a selection (default=all):}}<br />
<br />
Alternatively, simply direct pacman to install the packages directly:<br />
# pacman -S linux-ck linux-ck-headers<br />
<br />
== How to Determine Which CPU Optimized Package Set to Select ==<br />
Users unsure which package set to use can always install the '''ck-generic''' group which will drive any compatible CPU. For those wanting CPU-specific optimized packages, the following links can be used to help determine which package set to select.<br />
<br />
*http://en.gentoo-wiki.com/wiki/Safe_Cflags/Intel<br />
*http://en.gentoo-wiki.com/wiki/Safe_Cflags/AMD<br />
*http://www.linuxforge.net/docs/linux/linux-gcc.php <br />
*http://gcc.gnu.org/onlinedocs/gcc/i386-and-x86_002d64-Options.html<br />
<br />
== How Much Faster Are the CPU Optimized Packages ==<br />
The answer is not ''that'' much faster. Extensive testing comparing the effect of gcc compile options on resulting binaries have been conducted by others with varying result from no change to rather significant speed ups.<br />
<br />
*[http://www.phoronix.com/scan.php?page=home phoronix labs]<br />
*[https://bbs.archlinux.org/viewtopic.php?id=154333 Kernel patch for more CPU families offers measurable speed increases].<br />
<br />
Readers are encouraged to add to this list.<br />
<br />
== How to Enable the BFQ I/O Scheduler ==<br />
Since release 3.0.4-2, the BFQ patchset is applied to the package by default. Users must enable the BFQ scheduler to use it; it is dormant by default.<br />
<br />
=== Globally (for all devices) ===<br />
<br />
Add {{ic|1=elevator=bfq}} to boot loader [[Kernel parameters]].<br />
{{Note|Users building the PKG from the AUR have an option in the PKGBUILD itself to globally use the BFQ as the default I/O scheduler.}}<br />
<br />
=== Selectively (for only specified devices) ===<br />
<br />
Direct the kernel to use it on a device-by-device basis. For example, to enable it for {{ic|/dev/sda}} simply:<br />
# echo bfq > /sys/block/sda/queue/scheduler<br />
<br />
To confirm, simply ''cat'' the same file:<br />
# cat /sys/block/sda/queue/scheduler<br />
noop deadline cfq [bfq] <br />
<br />
Setting this way will not survive a reboot. To make the change automatically at the next system boot, create the following tmpfile where "X" is the letter for the SSD device.<br />
<br />
{{hc| /etc/tmpfiles.d/set_IO_scheduler.conf |<nowiki><br />
w /sys/block/sdX/queue/scheduler - - - - noop<br />
</nowiki>}}<br />
<br />
== Package Trivia/Repo Statistics ==<br />
*Various package sets are compiled via a Bash wrapper script for makepkg. The script is publicly accessible at graysky's [https://github.com/graysky2/repo-ck github] repo.<br />
*Repo [http://repo-ck.com/stats.pdf statistics] are available (popularity of packages, which CPU is most popular, # of downloads, etc.).<br />
{{Note|The statistics are not updated daily but do give a snapshot of the data.}}<br />
<br />
== Troubleshooting ==<br />
=== Forum Support ===<br />
Please use [https://bbs.archlinux.org/viewtopic.php?id=111715 this discussion thread] to voice comments, questions, suggestions, requests, etc. Note from graysky, "I can add other CPU-specific builds upon request. I just wanna be sure people will actually use them if I take the time to compile them."</div>Demyzehttps://wiki.archlinux.org/index.php?title=Arch_User_Repository&diff=234216Arch User Repository2012-11-07T09:24:01Z<p>Demyze: /* Git Repo */ Added warning: Git repo has stopped synching</p>
<hr />
<div>[[Category:Arch User Repository]]<br />
[[Category:Package development]]<br />
[[Category:Package management]]<br />
[[cs:Arch User Repository]]<br />
[[da:Arch User Repository]]<br />
[[el:Arch User Repository]]<br />
[[es:Arch User Repository]]<br />
[[fi:AUR]]<br />
[[fr:AUR]]<br />
[[it:Arch User Repository]]<br />
[[ja:Arch User Repository]]<br />
[[nl:Arch User Repository]]<br />
[[pl:Arch User Repository]]<br />
[[pt:Arch User Repository]]<br />
[[ro:AUR]]<br />
[[ru:Arch User Repository]]<br />
[[sr:Arch User Repository]]<br />
[[tr:Arch_Kullanıcı_Deposu]]<br />
[[uk:Arch User Repository]]<br />
[[zh-CN:Arch User Repository]]<br />
{{Article summary start}}<br />
{{Article summary text|The Arch User Repository is a collection of user-submitted [[PKGBUILD]]s that supplement software available from the [[official repositories]]. This article describes how to build ''unsupported'' software packages from the AUR.}}<br />
{{Article summary heading|Overview}}<br />
{{Article summary text|{{Package management overview}}}}<br />
{{Article summary heading|Related}}<br />
{{Article summary wiki|AUR Helpers}}<br />
{{Article summary wiki|AurJson}}<br />
{{Article summary wiki|AUR Trusted User Guidelines}}<br />
{{Article summary heading|Resources}}<br />
{{Article summary link|AUR Web Interface|https://aur.archlinux.org}}<br />
{{Article summary link|AUR Mailing List|http://www.archlinux.org/mailman/listinfo/aur-general}}<br />
{{Article summary end}}<br />
<br />
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 [[#.5Bcommunity.5D|[community]]] repository. This document explains how users can access and utilize the AUR.<br />
<br />
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 &mdash; provided it has a compatible license and good packaging technique &mdash; it may be entered into the [community] repository (directly accessible by [[pacman]] or [[ABS|abs]]).<br />
<br />
== Getting started ==<br />
<br />
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. <br />
<br />
* Ensure the {{Grp|base-devel}} group package is installed ({{ic|pacman -S base-devel}}).<br />
* Read the remainder of this article for more info and a short tutorial on installing AUR packages.<br />
* 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.<br />
* Glance over the [[#FAQ]] for answers to the most common questions.<br />
* 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.<br />
<br />
== History ==<br />
<br />
The following items are listed for historical purposes only. They have since been superseded by the AUR and are no longer available.<br />
<br />
At the beginning, there was {{ic|<nowiki>ftp://ftp.archlinux.org/incoming</nowiki>}}, 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.<br />
<br />
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).<br />
<br />
== Searching ==<br />
<br />
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].<br />
<br />
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 '\%'.<br />
<br />
== Installing packages ==<br />
<br />
Installing packages from the AUR is a relatively simple process. Essentially:<br />
<br />
# Acquire the tarball which contains the [[PKGBUILD]] and possibly other required files.<br />
# Extract the tarball (preferably in a folder set aside just for builds from the AUR).<br />
# Run {{ic|makepkg}} in the directory where the files are saved ({{ic|makepkg -s}} will automatically resolve dependencies with pacman).<br />
# Install the resulting package with [[pacman]]:<br />
<br />
: {{bc|# pacman -U /path/to/pkg.tar.xz}}<br />
<br />
[[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.<br />
<br />
{{Note|There is not and will never be an ''official'' mechanism for installing build material from the AUR. '''All users should be familiar with the build process.'''}}<br />
<br />
What follows is a detailed example of installation of a package called "foo".<br />
<br />
=== Prerequisites ===<br />
<br />
First ensure that the necessary tools are installed. The package group {{grp|base-devel}} should be sufficient; it includes {{pkg|make}} and other tools needed for compiling from source.<br />
<br />
{{Warning|Packages in the AUR assume the {{grp|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.}}<br />
<br />
# pacman -S base-devel<br />
<br />
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:<br />
<br />
~/builds<br />
<br />
or if using ABS (the [[Arch Build System]]):<br />
<br />
/var/abs/local<br />
<br />
For more information on ABS read the [[Arch Build System]] article. The example will use {{ic|~/builds}} as the build directory.<br />
<br />
=== Acquire build files ===<br />
<br />
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.<br />
<br />
Download the necessary build files. From the package's information page download the build files by clicking the "Tarball" link on the left-hand side near the end of the package details. 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).<br />
<br />
=== Build the package ===<br />
<br />
Extract the tarball. Change directories to the build directory if not already there and extract the build files.<br />
<br />
$ cd ~/builds<br />
$ tar -xvzf foo.tar.gz<br />
<br />
This should create a new directory called "foo" in the build directory.<br />
<br />
{{Warning|'''Carefully check all files.''' {{ic|cd}} to the newly created directory and carefully check the {{ic|PKGBUILD}} and any {{ic|.install}} file for malicious commands. {{ic|PKGBUILD}}s are bash scripts containing functions to be executed by {{ic|makepkg}}: these functions can contain ''any'' valid commands or Bash syntax, so it is totally possible for a {{ic|PKGBUILD}} to contain dangerous commands through malice or ignorance on the part of the author. Since {{ic|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.}}<br />
<br />
$ cd foo<br />
$ nano PKGBUILD<br />
$ nano foo.install<br />
<br />
Make the package. After manually confirming the integrity of the files, run [[makepkg]] as a normal user in the build directory.<br />
<br />
$ makepkg -s<br />
<br />
The {{ic|-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 {{ic|-s}} in the above command.<br />
<br />
=== Install the package ===<br />
<br />
Install the package using pacman. A tarball should have been created named:<br />
<br />
<''application name''>-<''application version number''>-<''package revision number''>-<''architecture''>.pkg.tar.xz<br />
<br />
This package can be installed using pacman's "upgrade" command:<br />
<br />
# pacman -U foo-0.1-1-i686.pkg.tar.xz <br />
<br />
These manually installed packages are called foreign packages &mdash; packages which have not originated from any repository known to pacman. To list all foreign packages:<br />
$ pacman -Qm <br />
<br />
{{Note|The above example is only a brief summary of the package building process. A visit to the [[makepkg]] and [[Arch Build System|ABS]] pages will provide more detail and is highly recommended, especially for first-time users.}}<br />
<br />
== Feedback ==<br />
<br />
The [https://aur.archlinux.org 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 Clients|pastebin]].<br />
<br />
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], and the vote count is one of the considerations in that process; it is in everyone's interest to vote!<br />
<br />
== Sharing and maintaining packages ==<br />
<br />
The user plays an essential role in the AUR, which cannot fulfill its potential without the support, involvement, and contribution of the wider user community. The life-cycle of an AUR package starts and ends with the user and requires the user to contribute in several ways.<br />
<br />
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.<br />
<br />
=== Submitting packages ===<br />
<br />
After logging in to the AUR web interface, a user can [https://aur.archlinux.org/pkgsubmit.php submit] a gzipped tarball ({{ic|.tar.gz}}) of a directory containing build files for a package. The directory inside the tarball should contain a [[PKGBUILD]], any {{ic|.install}} files, patches, etc. ('''absolutely''' no binaries). Examples of what such a directory should look like can be seen inside {{ic|/var/abs}} if the [[Arch Build System]] was installed.<br />
<br />
The tarball can be created with the following command:<br />
<br />
$ makepkg --source <br />
<br />
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:<br />
<br />
{{hc|$ tar tf libfoo-0.1-1.src.tar.gz #List contents of tarball.|<br />
libfoo/<br />
libfoo/PKGBUILD<br />
libfoo/libfoo.install}}<br />
<br />
When submitting a package, observe the following rules:<br />
<br />
* Check the [https://www.archlinux.org/packages/ package database] for the package. If it exists, '''do not''' submit the package. If the current package is broken or is lacking an included feature then please file a [https://bugs.archlinux.org/ bug report].<br />
* 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.<br />
* 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.<br />
* Packages that contain binaries or that are very poorly written may be deleted without warning.<br />
* If you are unsure about the package (or the build/submission process) in any way, submit the PKGBUILD to the [https://mailman.archlinux.org/mailman/listinfo/ AUR Mailing List] or the [https://bbs.archlinux.org/viewforum.php?id=4 AUR boards] on the forum for public review before adding it to the AUR.<br />
* 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.<br />
* 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.<br />
* Gain some experience before submitting packages. Build a few packages to learn the process and then submit.<br />
* If you submit a {{ic|package.tar.gz}} with a file named '{{ic|package}}' in it you will get an error: 'Could not change to directory {{ic|/home/aur/unsupported/package/package}}'. To resolve this, rename the file named '{{ic|package}}' to something else, for example, '{{ic|package.rc}}'. When it is installed in the {{ic|pkg}} directory you may rename it back to '{{ic|package}}'. Make sure to also read [[Arch Packaging Standards#Submitting packages to the AUR]].<br />
<br />
=== Maintaining packages ===<br />
<br />
* If you maintain a package and want to update the PKGBUILD for your package just resubmit it.<br />
* Check for feedback and comments from other users and try to incorporate any improvements they suggest; consider it a learning process!<br />
* 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.<br />
* If you do not want to continue to maintain the package for some reason, {{ic|disown}} the package using the AUR web interface and/or post a message to the AUR Mailing List.<br />
<br />
=== Other requests ===<br />
<br />
* Disownment requests and removal requests go to the aur-general mailing list for TUs and other users to decide upon.<br />
* '''Include package name and URL to AUR page''', preferably with a footnote [1].<br />
* Disownment requests will be granted two weeks after the current maintainer has been contacted by email and did not react.<br />
* '''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.<br />
* Removal requests require the following information:<br />
** Package name and URL to AUR page<br />
** Reason for deletion, at least a short note <br> '''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.<br />
** Include supporting details, like when a package is provided by another package, if you are the maintainer yourself, it's renamed and the original owner agreed, etc.<br />
<br />
Removal requests can be disapproved, in which case you'll likely be advised to disown the package for a future packager's reference.<br />
<br />
== [community] ==<br />
<br />
The [community] repository, maintained by [[Trusted Users]], contains the most popular packages from the AUR. It is enabled by default in {{ic|/etc/pacman.conf}}. If [community] has been disabled or removed, it can be enabled by uncommenting or adding these two lines: <br />
<br />
{{hc|/etc/pacman.conf|2=<br />
...<br />
[community]<br />
Include = /etc/pacman.d/mirrorlist<br />
...}}<br />
<br />
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 [[Arch Build System|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.<br />
<br />
Users can also access the [community] build files by editing {{ic|/etc/abs.conf}} and enabling the [community] repository in the {{ic|REPOS}} array.<br />
<br />
== Git Repo ==<br />
<br />
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):<br />
<br />
$ git clone <nowiki>git://pkgbuild.com/aur-mirror.git</nowiki><br />
<br />
More informations: [http://pkgbuild.com/git/aur-mirror.git/ Web interface], [http://pkgbuild.com/~td123/readme readme], [http://bbs.archlinux.org/viewtopic.php?id=113099 forum thread].<br />
<br />
{{Warning|The git repository has stopped syncing since 2012-10-26.}}<br />
<br />
== FAQ ==<br />
<br />
{{FAQ<br />
|question=What is the AUR?<br />
|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.}}<br />
<br />
{{FAQ<br />
|question=What kind of packages are permitted on the AUR?<br />
|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.}}<br />
<br />
{{FAQ<br />
|question=What is a TU?<br />
|answer=A [[AUR Trusted User Guidelines|TU (Trusted User)]] is a person who is chosen to oversee AUR and the [community] repository. They're the ones who maintain popular PKGBUILDs in [community], and overall keep the AUR running.}}<br />
<br />
{{FAQ<br />
|question=What's the difference between the Arch User Repository and [community]?<br />
|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 votes, they are moved into the [community] repository, where the TUs maintain binary packages that can be installed with [[pacman]].}}<br />
<br />
{{FAQ<br />
|question=How many votes does it take to get a PKGBUILD into [community]?<br />
|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.}}<br />
<br />
{{FAQ<br />
|question=How do I make a PKGBUILD?<br />
|answer=The best resource is [[Creating Packages]]. Remember to look in AUR before creating the PKGBUILD as to not duplicate efforts.}}<br />
<br />
{{FAQ<br />
|question=I'm trying to run "pacman -S foo"; it isn't working but I know it's in [community]<br />
|answer=You probably haven't enabled [community] in your {{ic|/etc/pacman.conf}}. Just uncomment the relevant lines.<br />
If [community] is enabled in your {{ic|/etc/pacman.conf}} try running {{ic|pacman -S -y}} first to synchronize the pkgcache before trying your package again.}}<br />
<br />
{{FAQ<br />
|question=Foo in AUR is outdated; what do I do?<br />
|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're 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.}}<br />
<br />
{{FAQ<br />
|question=I have a PKGBUILD I would like to submit; can someone check it to see if there are any errors?<br />
|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<br />
use [[namcap]] to check your PKGBUILD and the resulting package for errors.}}<br />
<br />
{{FAQ<br />
|question=Foo in AUR doesn't compile when I run makepkg; what should I do?<br />
|answer=You are probably missing something trivial.<br />
<br />
# Run {{ic|pacman -Syyu}} before compiling anything with {{ic|makepkg}} as the problem may be that your system is not up-to-date.<br />
# Ensure you have both "base" and "base-devel" groups installed.<br />
# Try using the "{{ic|-s}}" option with {{ic|makepkg}} to check and install all the dependencies needed before starting the build process.<br />
<br />
Be sure to first read the PKGBUILD and the comments on the AUR page of the package in question.<br />
The reason might not be trivial after all. Custom CFLAGS, LDFLAGS and MAKEFLAGS can cause failures. It's also possible that the PKGBUILD is broken for everyone. If you cannot figure it out on your own, just report it to the maintainer e.g. by posting the errors you are getting in the comments on the AUR page.}}<br />
<br />
{{FAQ<br />
|question=How can I speed up repeated build processes?<br />
|answer=If you frequently compile code that uses gcc - say, a git or SVN package - you may find [[ccache]], short for "compiler cache", useful.}}<br />
<br />
{{FAQ<br />
|question=How do I access unsupported packages?<br />
|answer=See [[#Installing packages]]}}<br />
<br />
{{FAQ<br />
|question=How can I upload to AUR without using the web interface?<br />
|answer=You can use {{pkg|burp}}, {{AUR|aurploader}} or {{AUR|aurup}} &mdash; these are command-line programs.}}</div>Demyzehttps://wiki.archlinux.org/index.php?title=Dvorak&diff=233078Dvorak2012-11-01T20:03:55Z<p>Demyze: /* Typing Tutors */ Changed the ktouch llink yo point to the search result instead if a direct link to the 64-bit version</p>
<hr />
<div>[[Category:Keyboards]]<br />
[[da:Dvorak]]<br />
[[fr:Dvorak]]<br />
[[zh-CN:Dvorak]]<br />
This is a quick blurb for setting or converting your keymaps to dvorak instead of qwerty.<br />
<br />
==Setting Dvorak On The Console==<br />
To convert to dvorak on the console, type<br />
loadkeys dvorak<br />
If you are using the left-handed dvorak layout,please type<br />
loadkeys dvorak-l<br />
or type<br />
loadkeys dvorak-r<br />
if you are using the right-handed dvorak layout.<br />
<br />
To make this change permanently, set<br />
KEYMAP="dvorak"<br />
in {{ic|/etc/vconsole.conf}}.<br />
<br />
==Setting Dvorak In X==<br />
To change to the dvorak layout in X, see [[Xorg#Keyboard_settings]]<br />
<br />
==Setting Dvorak International In X==<br />
<br />
Setting your system to the dvorak international layout (with dead keys) is a simple matter of changing the {{ic|XkbVariant}} option to {{ic|dvorak-intl}}. It should look as follows:<br />
<br />
Option "XkbVariant" "dvorak-intl"<br />
<br />
Your {{ic|XkbLayout}} should already be set to {{ic|us}}.<br />
<br />
In a small aside, you can test your configuration in a new X by entering the following into a shell:<br />
<br />
$ xinit -- :1<br />
<br />
This will work if you have {{ic|xinit}} installed. If you are not using a custom {{ic|.xinitrc}}, this will open a terminal in the new X session. From that terminal you can test your setup and exit that session by typing {{ic|exit}} in the terminal. If you are using your own {{ic|.xinitrc}}, you will have to exit in whatever way is provided by your setup.<br />
<br />
==For International Users==<br />
===Swedish===<br />
Swedish people interested in trying dvorak can find the swedish "version", called svorak, at [http://www.aoeu.info aoeu.info]! To convert to svorak in X you do not need to download any additional files from www.aoeu.info.<br />
===Spanish===<br />
You can install the AUR {{AUR|dvorak-es-loadkeys}} package, and then use {{ic|dvorak-es}} instead of {{ic|dvorak}}, both in loadkeys and {{ic|/etc/vconsole.conf}} to use the spanish dvorak variant.<br />
<br />
On X, you don't need to install anything, just edit {{ic|/etc/X11/xorg.conf.d/01-keyboard-layout.conf}} and put:<br />
Section "InputClass"<br />
Identifier "Keyboard-layout"<br />
Driver "evdev"<br />
MatchIsKeyboard "yes"<br />
Option "XkbLayout" "es(dvorak)"<br />
EndSection<br />
<br />
==Typing Tutors==<br />
Console: {{AUR|DvorakNG}}<br />
<br />
GUI: [https://www.archlinux.org/packages/?q=ktouch KTouch] (includes Dvorak lessons in English, French, German & Spanish)</div>Demyze