https://wiki.archlinux.org/index.php/Localized name of translated page
طبعاً مع أستبدال Localized name of translated page بأسم الصفحة الذي تريده باللغة العربية. و اﻷن أدخل +
طبعاً مع استبدال Localized name of translated page باسم الصفحة الذي تريده باللغة العربية. و الآن ادخل:
#REDIRECT [[Some_Page_(العربية)]]
كمحتوى وحيد فيها مع اﻷنتباه الى أستبدال some_page بعنوان صفحتك المترجمة +
كمحتوى وحيد فيها مع الانتباه إلى استبدال some_page بعنوان صفحتك المترجمة.
LPROF is an ICC profiler with a graphical user interface listed under lprofAUR[broken link: package not found] in the AUR. +
LPROF is an ICC profiler with a graphical user interface listed under lprofAUR[broken link: package not found] in the AUR.
colord was already running, you need to restart colord.service.
xcalib is a lightweight monitor calibration loader which can load an ICC monitor profile to be shared across desktop applications. Installation: install the package xcalib. -
-Load profile P221W-sRGB.icc in /usr/share/color/icc on display host:0 when X server starts
+
xcalib is a lightweight monitor calibration loader which can load an ICC monitor profile to be shared across desktop applications. Install the package xcalib.
-#!/bin/bash - -/usr/bin/xcalib -d :0 /usr/share/color/icc/P221W-sRGB.icc-
Load profile P221W-Native.icc in /usr/local/share/color/icc on display host:0 when JWM starts
+
To load profile P221W-sRGB.icc in /usr/share/color/icc:
<StartupCommand>xcalib -d :0 /usr/local/share/color/icc/P221W-Native.icc</StartupCommand>+$ xcalib -d :0 /usr/share/color/icc/P221W-sRGB.icc+This can be autostarted at the start of the Xorg server, the desktop environment or the window manager. +
dispwin
dispwin is a part of argyllcms.
-Xinitrc example
-Load profile
-906w-6500K.iccin/home/arch/.color/iccon display 0 when X server starts -#!/bin/bash - -/usr/bin/dispwin -d0 /home/arch/.color/icc/906w-6500K.icc--JWM <StartupCommand> example -
-Load Argyll calibration file
906w-7000K.calin/usr/local/share/color/iccon display 1 when JWM starts +To load the profile
-906w-6500K.iccin/home/archie/.color/icc:<StartupCommand>dispwin -d1 /usr/local/share/color/icc/906w-7000K.cal</StartupCommand>+$ dispwin -d0 /home/archie/.color/icc/906w-6500K.icc-You can easily use one of these loaders to apply the color profile in early boot stage when starting a display manager, e.g. using LightDM startup script. This allows to load a single icc profile file. This will not work with loading several profile files when using a multi monitopr setup. +
This can be autostarted at the start of the Xorg server, the desktop environment or the window manager.
Wayland
Wayland supports color management through color profiles, but the user interface for managing these profiles is currently not implemented properly. However, you can manually add a color profile through the following steps: @@ -625,7 +573,7 @@
See also
IMWheel is a tool for tweaking mouse wheel behavior, on a per-program basis. It can map mouse wheel input to keyboard input, increase mouse wheel speed, and has support for modifier keys. +
IMWheel is a tool for tweaking mouse wheel behavior, on a per-program basis. It can map mouse wheel input to keyboard input, increase mouse wheel speed, and has support for modifier keys.
The root image can be found on one of the mirrors under iso/latest/arch/x86_64/. The squashfs format is not editable, so we unsquash the root image and mount it.
To unsquash the root image, run @@ -630,8 +630,8 @@
After=graphical.target Type=oneshot User=root --
Here you have an example systemd unit file. Feel free to modify to your laptop configuration. -
-/etc/systemd/system/i915-gvt.service-
[Unit] -Description=Create i915 gvt virtual gpu - -[Service] -Type=simple - -Environment="GVT_PCI=0000:00:02.0" -Environment="GVT_TYPE=i915-GVTg_V5_4" -Environment="GVT_GUID=58012773-8161-470b-8e86-f23216adeed2" - -# load kernel modules -ExecStartPre=/usr/bin/modprobe kvmgt -ExecStartPre=/usr/bin/modprobe vfio-iommu-type1 -ExecStartPre=/usr/bin/modprobe mdev - -# create virtual gpu -ExecStart=bash -c 'echo $GVT_GUID > /sys/devices/pci0000:00/$GVT_PCI/mdev_supported_types/$GVT_TYPE/create' - -# set access rights -ExecStartPost=bash -c 'chown :kvm -R /sys/bus/mdev/devices/$GVT_GUID/' -ExecStartPost=bash -c 'chmod 770 -R /sys/bus/mdev/devices/$GVT_GUID/' -ExecStartPost=bash -c 'chown :kvm -R /dev/vfio/18' -ExecStartPost=bash -c 'chmod 770 -R /dev/vfio/18' - -# Do not execute ExecStop immediately -RemainAfterExit=true - -# remove virtual gpu -ExecStop=bash -c 'echo 1 > /sys/devices/pci0000:00/$GVT_PCI/$GVT_GUID/remove' - -# unload kernel modules -ExecStopPost=/usr/bin/rmmod kvmgt -ExecStopPost=/usr/bin/rmmod vfio-iommu-type1 -ExecStopPost=/usr/bin/rmmod mdev - -[Install] -WantedBy=multi-user.target -
If you run qemu or libvirtd as a regular user, it may complain that some path /dev/vfio/number is not writeable. You need to enable write access to that path for the account, with chmod or setfacl.
@@ -714,7 +662,7 @@
We will go with the last option because it does not involve patching anything. (Note: if the link and the archive go down, the OpROM can be extracted from the kernel patch by hand.)
-i915ovmfPkg may be considered as well, it is a currently the most advanced GVT-g ROM for use with OVMF, see this discussion. +
i915ovmfAUR is available, which is an up-to-date fork of the archived i915ovmfPkg, it is a currently the most advanced GVT-g ROM for use with OVMF, see this discussion. The AUR package installs the UEFI rom file as /var/lib/libvirt/qemu/drivers/i915ovmf.rom . First boot can take a while, especially if the guest OS needs to install drivers, as is the case with Windows 10.
Download vbios_gvt_uefi.rom and place it somewhere world-accessible (we will use / to make an example).
Optionally, third-party graphical and terminal user interface front-ends can be installed: +
+The iwd package provides the client program iwctl, the daemon iwd and the Wi-Fi monitoring tool iwmon.
iwgtkAUR provides a GUI front-end for iwd and an indicator (tray) icon. -
-impalaAUR provides a TUI (Terminal User Interface) for iwd. -
Start/enable iwd.service so it can be controlled through the iwctl command or through iwgtk.
Then reload the systemd manager configuration.
-A low entropy pool can cause connection problems in particular noticeable after reboot. See Random number generation for suggestions to increase the entropy pool. -
Since version 1.0, iwd disables predictable renaming of wireless device. It installs the following systemd network link configuration file which prevents udev from renaming the interface to wlp#s#:
arch=(...) with one or more architectures (but not any) indicates the package can be compiled for any of the specified architectures, but is architecture-specific once compiled. For these packages, specify all architectures that the PKGBUILD officially supports. For official repository and AUR packages, this means arch=('x86_64'). Optionally, AUR packages may choose to additionally support other known working architectures.arch=(...) with one or more architectures (but not any) indicates the package can be compiled for any of the specified architectures, but is architecture-specific once compiled. For these packages, specify all architectures that the PKGBUILD officially supports. For official repository and AUR packages, this means arch=('x86_64'). Optionally, AUR packages may choose to additionally support other known working architectures.The target architecture can be accessed with the variable $CARCH during a build.
+
The target architecture can be accessed with the variable CARCH during a build.
The URL of the official site of the software being packaged. @@ -615,13 +606,13 @@
The license under which the software is distributed. Arch Linux uses SPDX license identifiers. Each license must have a corresponding entry in /usr/share/licenses/.
For common licenses (like 'GPL-3.0-or-later'), package licenses delivers all the corresponding files. The package is installed by default, as it is a dependency of base meta package, and the files may be found in /usr/share/licenses/spdx/. Simply refer to the license using its SPDX license identifier from the list of SPDX identifiers.
+
For common licenses (like GPL-3.0-or-later), package licenses delivers all the corresponding files. The package is installed by default, as it is a dependency of base meta package, and the files may be found in /usr/share/licenses/spdx/. Simply refer to the license using its SPDX license identifier from the list of SPDX identifiers.
License families like BSD or MIT are, strictly speaking, not a single license and each instance requires a separate license file. In license variable refer to them using a common SPDX identifier (e.g. 'BSD-3-Clause' or 'MIT'), but then provide the corresponding file as if it was a custom license.
+
License families like BSD or MIT are, strictly speaking, not a single license and each instance requires a separate license file. In license variable refer to them using a common SPDX identifier (e.g. BSD-3-Clause or MIT), but then provide the corresponding file as if it was a custom license.
For custom licenses the identifier should be either LicenseRef-license-name or custom:license-name, if they are not covered by the common families mentioned above. The corresponding license text must be placed in directory /usr/share/licenses/pkgname. To install the file a following code snippet may be used in package() section:
install -Dm644 LICENSE "$pkgdir/usr/share/licenses/$pkgname/LICENSE" +install -Dm644 LICENSE "${pkgdir}/usr/share/licenses/${pkgname}/LICENSE"Combining multiple licenses or adding exceptions should follow the SPDX syntax. For example a package released under either GNU/GPL 2.0 or GNU/LGPL 2.1 could use
@@ -661,7 +652,7 @@'GPL-2.0-or-later OR LGPL-2.1-or-later', a package released under Apache 2.0 with LLVM exception would use'Apache-2.0 WITH LLVM-exception'and a package released with part under the BSD 3 clause, others under GNU/LGPL 2.1 and some under GNU/GPL 2.0 would use'BSD-3-Clause AND LGPL-2.1-or-later AND GPL-2.0-or-later'[2]. Note that this must be a single string, so the entire expression has to be enclosed in quotes. As for November 2023 SPDX list of exceptions is limited, so usually the custom license route must be used.depends
Dependencies should normally include the requirements for building all optional features of a package. Alternatively, any feature whose dependencies are not included should be explicitly disabled via a configure option. Failure to do this can lead to packages with "automagic dependencies" build-time optional features that are unpredictably enabled due to transitive dependencies or unrelated software installed on the build machine, but which are not reflected in the package dependencies.
-If the dependency name appears to be a library, e.g.
depends=('libfoobar.so'), makepkg will try to find a binary that depends on the library in the built package and append the soname version needed by the binary. Appending the version yourself disables automatic detection, e.g.depends=('libfoobar.so=2'). +If the dependency name appears to be a library, e.g.
depends=(libfoobar.so), makepkg will try to find a binary that depends on the library in the built package and append the soname version needed by the binary. Appending the version yourself disables automatic detection, e.g.depends=('libfoobar.so=2').makedepends
An array of packages that are only required to build the package. The minimum dependency version can be specified in the same format as in the
dependsarray. The packages in thedependsarray are implicitly required to build the package, they should not be duplicated here. @@ -697,10 +688,15 @@Package relations Note: Additional architecture-specific arrays can be added by appending an underscore and the architecture name, e.g.
conflicts_x86_64=().provides
-An array of additional packages that the software provides the features of, including virtual packages such as
cronorshand all external shared libraries. Packages providing the same item can be installed side-by-side, unless at least one of them uses aconflictsarray. +An array of additional packages that the software provides the features of, including virtual packages such as cron or sh and all external shared libraries. Packages providing the same item can be installed side-by-side, unless at least one of them uses a
conflictsarray.-Note: The version that the package provides should be mentioned (+Note: +pkgverand potentially thepkgrel), in case packages referencing the software require one. For instance, a modified qt package version 3.3.8, named qt-foobar, should useprovides=('qt=3.3.8'); omitting the version number would cause the dependencies that require a specific version of qt to fail. Do not addpkgnameto theprovidesarray, as it is done automatically.
pkgver and potentially the pkgrel), in case packages referencing the software require one. For instance, a modified qt package version 3.3.8, named qt-foobar, should use provides=('qt=3.3.8'); omitting the version number would cause the dependencies that require a specific version of qt to fail.pkgname to the provides array, as it is done automatically.An array of packages that conflict with, or cause problems with the package, if installed. All these packages and packages providing this item will need to be removed. The version properties of the conflicting packages can also be specified in the same format as the depends array.
An array of files needed to build the package. It must contain the location of the software source, which in most cases is a full HTTP or FTP URL. The previously set variables pkgname and pkgver can be used effectively here; e.g. source=("https://example.com/$pkgname-$pkgver.tar.gz").
+
An array of files needed to build the package. It must contain the location of the software source, which in most cases is a full HTTP or FTP URL. The previously set variables pkgname and pkgver can be used effectively here; e.g. source=("https://example.com/${pkgname}-${pkgver}.tar.gz").
Files can also be supplied in the same directory where the PKGBUILD is located, and their names added to this array. Before the actual build process starts, all the files referenced in this array will be downloaded or checked for existence, and makepkg will not proceed if any is missing.
.install files are recognized automatically by makepkg and should not be included in the source array. Files in the source array with extensions .sig, .sign, or .asc are recognized by makepkg as PGP signatures and will be automatically used to verify the integrity of the corresponding source file.
source=('unique_package_name::file_uri'); e.g. source=("$pkgname-$pkgver.tar.gz::https://github.com/coder/program/archive/v$pkgver.tar.gz").
+Warning: The downloaded source filename must be unique because the SRCDEST directory can be the same for all packages. For instance, using the version number of the project as a filename potentially conflicts with other projects with the same version number. In this case, the alternative unique filename to be used is provided with the syntax source=('unique_package_name::file_uri'); e.g. source=("${pkgname}-${pkgver}.tar.gz::https://github.com/coder/program/archive/v${pkgver}.tar.gz").
source_x86_64=(). There must be a corresponding integrity array with checksums, e.g. sha256sums_x86_64=().file:// URL to point to a directory or a file in your computer filesystem. For example, a local Git repository can be specified as "$pkgname"::"git+file:///path/to/repository".file:// URL to point to a directory or a file in your computer filesystem. For example, a local Git repository can be specified as "${pkgname}::git+file:///path/to/repository".DLAGENT and using the magnet:// uri prefix instead of the canonical magnet:?.source=("http://foo.org/bar/foobar.tar.xz")
noextract=('foobar.tar.xz')
-To extract nothing, you can do something like this: +
To extract nothing, you can do something like this:
source contains only plain URLs without custom file names, strip the source array before the last slash:noextract=("${source[@]##*/}")These variables are arrays whose items are checksum strings that will be used to verify the integrity of the respective files in the source array. You can also insert SKIP for a particular file, and its checksum will not be tested.
The checksum type and values should always be those provided by upstream, such as in release announcements. When multiple types are available, the strongest checksum is to be preferred: b2 over sha512, sha512 over sha384, sha384 over sha256, sha256 over sha224, sha224 over sha1, sha1 over md5, and md5 over ck. This best ensures the integrity of the downloaded files, from upstream's announcement to package building.
+
The checksum type and values should always be those provided by upstream, such as in release announcements. When multiple types are available, the strongest checksum is to be preferred: b2 over sha512, sha512 over sha384, sha384 over sha256, sha256 over sha224, sha224 over sha1, sha1 over md5, and md5 over ck. This best ensures the integrity of the downloaded files, from upstream announcement to package building.
sha256sums_x86_64=().An array CRC32 checksums (from UNIX-standard cksum) of the files listed in the source array.
+
An array of BLAKE2 checksums with digest size of 512 bits.
-An array of 128-bit MD5 checksums of the files listed in the source array.
+
An array of SHA-2 checksums with digest sizes 512, 384, 256 and 224 bits, respectively. sha256sums is the most common of them.
An array of 160-bit SHA-1 checksums of the files listed in the source array.
An array of SHA-2 checksums with digest size of 256 bits. -
-An array of SHA-2 checksums with digest sizes 224, 384, and 512 bits, respectively. These are less common alternatives to sha256sums.
+
An array of 128-bit MD5 checksums of the files listed in the source array.
An array of BLAKE2 checksums with digest size of 512 bits. +
An array CRC32 checksums (from UNIX-standard cksum) of the files listed in the source array.
Install the pptpclient package. @@ -574,8 +574,8 @@
pam_mount can be used to automatically mount an encrypted home partition (encrypted with, for example, LUKS or ECryptfs) on user log in. +
pam_mount can be used to automatically mount an encrypted home partition (encrypted with, for example, LUKS or ECryptfs) on user log in.
It will mount your /home (or whatever mount point you like) when you log in using your login manager or when logging in on console. The encrypted drive's passphrase should be the same as your linux user's password, so you do not have to type in two different passphrases to login.