Manjaro - User contributions [en]

Pacman Overview/fr

2021-11-14T18:03:31Z

Mioufou:

<languages/>
__TOC__

=Aperçu=

Le gestionnaire de paquets de Manjaro, [[Special:MyLanguage/Pamac|Pamac]], est fourni avec la plupart des éditions de Manjaro. Toutes les éditions de Manjaro incluent [https://www.archlinux.org/pacman/ pacman], le gestionnaire de paquets de la version amont d'Arch Linux. Pacman comprend certaines fonctionnalités avancées que l'on ne trouve pas dans Pamac.

Points clés à connaître :

<div class="mw-translate-fuzzy">
* Pacman est installé par défaut dans Manjaro Linux.
* Pacman est principalement développé et maintenu par les développeurs d'Arch Linux
* Pacman ne peut être utilisé qu'en ligne de commande. Si vous préférez un gestionnaire de paquets graphique, veuillez consulter [[Special:MyLanguage/Pamac|Pamac]] ou [[Special:MyLanguage/Octopi|Octopi]].
* Pacman ne peut utiliser que le dépôt officiel de Manjaro [[Special:MyLanguage/Repositories_and_Servers|repository]]. Il existe des articles distincts pour accéder au [[Special:MyLanguage/Arch_User_Repository|Arch User Repository(AUR)]], pour utiliser [[Special:MyLanguage/Flatpak|flatpaks]] ou pour utiliser [[Special:MyLanguage/Snaps|snaps]]
</div>

=Mises à jour=

Pour mettre à jour la base de données de paquets et tout les paquets du système
{{UserCmd|command=sudo pacman -Syu}}

Pour forcer un rafraîchissement complet de la base de données de paquets et mettre à jour tout les paquets du système. Vous devez le faire lorsque vous [[Special:MyLanguage/Switching_Branches|changez de branche]] ou [[Special:MyLanguage/Pacman-mirrors|changez de mirroir]].
{{UserCmd|command=sudo pacman -Syyu}}

Pour forcer un rafraîchissement complet de la base de données de paquets, mettre à jour les paquets du système et autoriser les paquets à être rétrograder.
Le rétrogradage devrait être seulement nécessaire lors d'un changement de branche. Par exemple passer de Testing à Stable
{{UserCmd|command=sudo pacman -Syyuu}}

=Recherche de paquets=

Pour chercher les paquets disponibles dans les dépôts de Manjaro, vous pouvez utiliser {{ic|pacman -Ss mot-clé}}. Cela va chercher le mot-clé dans le nom du paquet et dans la description. Par exemple, pour chercher les paquets contenant le mot-clé smplayer, vous pouvez utiliser :
{{UserCmd|command=pacman -Ss smplayer}}

Vous pouvez chercher dans vos paquets installés de la même façon en utilisant {{ic|-Qs}} à la place de {{ic|-Ss}}. Pour chercher smplayer dans vos paquets installés :
{{UserCmd|command=pacman -Qs smplayer}}

Lorsque vous avez trouvé un paquet vous pouvez utiliser {{ic|pacman -Qi}} pour obtenir plus d'informations sur un paquet installé ou {{ic|pacman -Si}} pour un paquet dans un dépôt. En suivant l'exemple ci-dessus, vous pouvez utiliser :
{{UserCmd|command=pacman -Si smplayer}}

Finalement, pour obtenir la liste de tout les paquets installés sur votre système, entrez la commande suivante :
{{UserCmd|command=pacman -Ql}}

=Installation de paquets=

{{warning|N'installez jamais un paquet sans d'abord mettre à jour le système. Sur un système en version continue, cela peut conduire à un système non amorçable.}}

To install a software package, the basic syntax is {{ic|pacman -S packagename}}. However, installing a package without updating the system will lead to a partial upgrade situation so all the examples here will use {{ic|pacman -Syu packagename}} which will install the package and ensure the system is up to date. For example, to install smplayer the command is:
{{UserCmd|command=sudo pacman -Syu smplayer}}

You will then be presented a list of software to install. You may notice this list has more packages than you requested. This is because many packages also have dependencies which are packages that must be installed in order for the software you selected to function properly.

Pacman can also directly install packages from the local system or a location on the internet. The format of that command is {{ic|pacman -U packagelocation}}. For example, to install a copy of your package cache you could do something like:
{{UserCmd|command=sudo pacman -U /var/cache/pacman/pkg/smplayer-19.5.0-1-x86_64.pkg.tar.xz}}

Alternatively, you could get it directly from one of Manjaro's mirrors:
{{UserCmd|command=sudo pacman -U <nowiki>https://mirror.alpix.eu/manjaro/stable/community/x86_64/smplayer-19.5.0-1-x86_64.pkg.tar.xz</nowiki>}}

{{warning|Lorsque vous utilisez pacman -U, il vous appartient de vous assurer que le paquet que vous installez est entièrement compatible avec votre système.}}

=Suppression de paquets=

{{warning|vérifiez toujours la liste des paquets avant de confirmer lors de la suppression des paquets. Si vous ne faites pas attention, vous pouvez facilement supprimer tout votre bureau en raison de dépendances.}}

To remove a software package, the basic syntax is {{ic|sudo pacman -R packagename}}. We could remove the smplayer package we installed above with:
{{UserCmd|command=sudo pacman -R smplayer}}

This will remove the package, but will leave all the dependencies behind. If you also want to remove the unneeded dependencies you could use {{ic|pacman -Rsu packagename}} as seen in this example:
{{UserCmd|command=sudo pacman -Rsu smplayer}}

Sometimes when you try to remove a package you will not be able to because there are other packages which depend on it. You can use {{ic|pacman -Rc packagename}} to remove a package and everything that depends on it. Be careful to heed the above warning when using this option.
{{UserCmd|command=sudo pacman -Rc smplayer}}

The most nuclear option is {{ic|pacman -Rcs packagename}}. This will remove everything that depends on packagename and continue to do so on its dependencies. This should really only be used in exceptional circumstances such as when removing an entire desktop environment and trying not to leave anything behind.

Pacman usually also creates backup configuration files when deleting packages. To remove those, you can add {{ic|n}} to any of the examples above. For example:
{{UserCmd|command=sudo pacman -Rn smplayer}}
{{UserCmd|command=sudo pacman -Rsun smplayer}}
{{UserCmd|command=sudo pacman -Rcn smplayer}}

=Affichage et suppression des orphelins=

To list all ''orphans'', installed packages that are not used by anything else and should no longer be needed:
{{UserCmd|command=pacman -Qdt}}

To remove all the orphans:
{{UserCmd|command=sudo pacman -Rs $(pacman -Qdtq)}}

=Téléchargement de paquets sans installation=

In some cases it may be useful to download a package without installing. For example, to install on a different system that is not connected to the internet. This can be done with {{ic|pacman -Sw packagename}}. For example:
{{UserCmd|command=sudo pacman -Sw smplayer}}

The package and any rerquired dependencies will be downloaded to your pacman cache at {{ic|/var/cache/pacman/pkg}}

=Déterminer quel paquet possède un fichier=

It is often useful to understand which package installed a file on your system. This is easy to do with pacman using {{ic|pacman -Qo /path/to/filename}}. For example:
{{UserCmd|command=pacman -Qo /usr/bin/smplayer}}

=Nettoyage du cache=

When pacman installs packages, it keeps a copy of all the old packages you have downloaded. This cache can be very useful if you have to install older packages in an emergency. However, left unchecked, this cache will grow very large over time. Systems running [[Special:MyLanguage/Pamac|Pamac]] will already have access to its automated pacman cache cleaning functions. It is also possible to clean them manually using pacman.

To clear the cache of packages that are no longer installed, enter the following command:
{{UserCmd|command=sudo pacman -Sc}}

Otherwise, to clear the cache completely, enter the following command (and use with care):
{{UserCmd|command=sudo pacman -Scc}}

A safer way to remove old package cache files is to remove all packages except for the latest three package versions using {{ic|paccache}}:
{{UserCmd|command=paccache -rvk3}}

=Le fichier de configuration, pacman.conf=

Les paramètres de Pacman sont situées dans le fichier {{ic|/etc/pacman.conf}}. Le propriétaire de ce fichier est root, voir [[Special:MyLanguage/Viewing_and_editing_configuration_files|this guide]] si vous souhaitez plus d'information sur les possibilités d'édition de ce type de fichier. On trouvera une documentation complète de ces options sur le lien Arch Linux référence ci-dessous. Cette documentation met en évidence plusieurs options particulièrement intéressantes pour les utilisateurs de Manjaro.

{{note|les paramètres pacman.conf sont sensibles à la casse}}

==Activation de la sortie couleur==

Par défaut, la sortie de pacman est monochrome, mais l'activation de la sortie couleur peut faciliter la lecture si votre terminal prend en charge les couleurs. Cela peut être activé en décommentant ou en ajoutant la ligne suivante au fichier
Color

==Affichage de Pacman qui mange==

Si vous vous ennuyez de simplement regarder des lignes de hachage lors du téléchargement d'applications dans le terminal, pourquoi ne pas changer la barre de progression en Pacman mangeant des pilules énergétiques à la place? Pour activer ceçi, ajoutez simplement la ligne:
ILoveCandy

=Dépannage=
Une page distincte pour le dépannage de pacman est disponible '''[[Special:MyLanguage/pacman troubleshooting|içi]]'''.

=Voir aussi=
* [[Special:MyLanguage/System Maintenance|maintenance du Système]]
* [[Special:MyLanguage/Pacman-mirrors|Pacman-mirrors]]
* [[Special:MyLanguage/Pacman troubleshooting|Pacman dépannages]]
* [[Special:MyLanguage/Downgrading packages|Downgrading packages]]
* [https://wiki.archlinux.org/index.php/Pacman ArchWiki: pacman]
* [https://wiki.archlinux.org/index.php/Pacman_tips ArchWiki: pacman astuces]
* [https://wiki.archlinux.org/index.php/Improve_pacman_performance ArchWiki: pacman performance]

[[Category:Contents Page{{#translation:}}]]

Translations:Pacman Overview/6/fr

2021-11-14T17:28:27Z

Mioufou:

Pour mettre à jour la base de données de paquets et tout les paquets du système
{{UserCmd|command=sudo pacman -Syu}}

Basic Tips for conky

2021-11-13T13:50:53Z

Mioufou: /* Fixed the LUA link */

<languages/>
__TOC__
<translate>
==Installation== 
Conky can be installed using the package manager
{{UserCmd|command=pamac install conky}}

===Configuration=== 
All file names starting with a dot <code>.</code> are hidden files. If you want to see hidden files in your file manager, you need to make them visible. In most file managers this will be available in the options.
====Configuration file====
The default configuration file is located in {{ic|/usr/share/doc/conky-1.11.5_pre/conky.conf}} where version are subject to change.
Conky do not create a local conky folder so you will have to create beforehand
{{UserCmd|command=mkdir -p ~/.config/conky}}
Then copy the default to home
{{UserCmd|command=cp /usr/share/doc/conky-1.11.5_pre/conky.conf ~/.config/conky/conky.conkyrc}}
The configuration file is a simple text file and the content written using [[https://www.lua.org/ |LUA syntax]] and is split into two parts


* Configuration
* Text

===Conky configuration=== 
The first/upper part contains all the configuration settings for the entire conky. Things like the position of the conky on your screen, transparency settings, border settings, the default font and it's size, and how often your conky gets updated. The whole configuration belong between brackets like this
{{File|file=~/.config/conky/conky.conkyrc|
content=<pre>conky.config = {
};</pre>
Some rules apply

* Every line end with <code>,</code>
* Non-boolean/numerical value should be placed between <code>'</code>
* Comment start with <code>--</code>
}}
===Examples=== 
'''1.''' This will set the default font color of your conky to white. Additionally, a <code>color1</code> gets set using a [http://html-color-codes.info/ Html Color Code]to a light blue:
{{File|file=~/.config/conky/conky.conkyrc|
content=<pre>conky.config = {
...
default_color = 'white', -- White default color
color1 = '0ab1ff', -- Light blue
...
};</pre>
}}
'''2.''' This enables Xft, set the default font (LiberationMono), make it bold and set it's size (8):
{{File|file=~/.config/conky/conky.conkyrc|
content=<pre>conky.config = {
...
use_xft = true,
font = 'LiberationMono:bold:size=8',
...
};</pre>
}}
'''3.''' In order to position your conky on your screen, modify these settings:
{{File|file=~/.config/conky/conky.conkyrc|
content=<pre>conky.config = {
...
alignment = 'top_right', -- Conky gets placed in the top right corner of your desktop
gap_x 18, -- with a horizontal gap of 18 pixels (to your right screen edge)
gap_y 20, -- and a vertical gap of 20 pixels (to your top screen edge).
...
};</pre>
}}
'''4.''' In some case you can have multiple values for one setting, they will be separated by a coma:
{{File|file=~/.config/conky/conky.conkyrc|
content=<pre>conky.config = {
...
own_window_hints = 'undecorated,sticky,skip_taskbar,skip_pager,below',
...
};</pre>
}}
Use the command: <code>man conky</code>, and look into the '''CONFIGURATION SETTINGS''' section to see every settings available.

===Conky text=== 
The second part contains the displayed conky code. Every code line corresponds to one displayed line on your desktop. There are a lot of available for displaying and modifying all kinds of information. Use the command: <code>man conky</code>, and look into the '''OBJECTS/VARIABLES''' section to see every objects/variables available.
{{BoxInfo|Info|The lines in the '''conky.text''' section is printed exactly as is. E.g. if you create an empty line between sections - conky will display an empty line.}}

The whole code belong between these two double bracket:
{{File|file=~/.config/conky/conky.conkyrc|
content=<pre>conky.text = [[
]];</pre>
}}
===Examples=== 
'''1.''' You can choose the color of your font using one of the following variables:
{{File|file=~/.config/conky/conky.conkyrc|
content=<pre>conky.text = [[
...
${color}
${color1}
...
]];</pre>
}}


Every variable is marked with a <code>$</code> sign and by <code>{ }</code> brackets (only needed, if the variable contains more than one word).


'''2.''' You can call the default font (and it's size) with this command:
{{File|file=~/.config/conky/conky.conkyrc|
content=<pre>conky.text = [[
...
$font
...
]];</pre>
}}
If you want a different font (DejaVuSerif) and font size (9) in your conky, use this command in your <code>.conkyrc</code> code:
{{File|file=~/.config/conky/conky.conkyrc|
content=<pre>conky.text = [[
...
${font DejaVuSerif:size=9}
...
]];</pre>
}}
'''3.''' This code line displays the text "Kernel: " and the kernel you are using (using <code>$alignr</code> just yields a nicer formatting, it is not necessary: <code>$alignr</code> aligns all following text on the right of your conky):
{{File|file=~/.config/conky/conky.conkyrc|
content=<pre>conky.text = [[
Kernel: ${alignr}${kernel}
]];</pre>
}}
'''4.''' This variable gives you the latest 3 manjaro blog entry titles (using rss). It checks for updates every 60 minutes.
{{File|file=~/.config/conky/conky.conkyrc|
content=<pre>conky.text = [[
${rss http://manjaro.org/feed/ 60 item_titles 3}
]];</pre>
}}
'''5.''' Information about the root partition <code>/</code> of your manjaro installation is displayed using
{{File|file=~/.config/conky/conky.conkyrc|
content=<pre>conky.text = [[
Root: ${alignr}${fs_used /} of ${fs_size /}
]];</pre>
}}
'''6.''' Instead of example 3, you can use the following code to display the exact same information:
{{File|file=~/.config/conky/conky.conkyrc|
content=<pre>conky.text = [[
Kernel: ${alignr}${execi 3600 uname -r}
]];</pre>
}}

===execi=== 
The variable <code>${execi 3600 XXXX}</code> runs the <code>XXXX</code> bash code in your terminal every 3600 seconds and displays the result in your conky. The result of the <code>uname -r</code> bash command is your currently used kernel name.


Use any bash command instead of <code>XXXX</code> you can think of. The bash commands can be as long and complicated as you want.


Warning: Using complicated bash commands (e.g. which call other programs or use large files) with low intervals (e.g. <code>${execi 2 XXXX}</code> runs the <code>XXXX</code> code once every 2 seconds and displays it's result in your conky) can use a lot of hardware resources and/or make your computer unresponsive.

===Running conky=== 
If you want to display a conky on your desktop a {{ic|~/.config/conky/conky.conkyrc}} file with code in it is required. Next, open a terminal and run conky pointing to the file
{{UserCmd|command=conky -c ~/.config/conky/conky.conkyrc}}
or to run as background daemon
{{UserCmd|command=conky -d -c ~/.config/conky/conky.conkyrc}}


If you want to run conky automatically after each boot of your computer, you need to find out how to autostart a program. This depends on the Desktop Manager you are using. The next is examples of how to run conky from your system autostart folder/file/script/command.
<code>sleep 20</code> and <code>-p 20</code> delay the start of conky by 20 seconds after your Desktop Environment has started. Adjust this value to your liking.


{{UserCmd|command=conky -c ~/.config/conky/conky.conkyrc &}}
{{UserCmd|command=sleep 20 && conky -c ~/.config/conky/conky.conkyrc &}}


When you change the running conky configuration file - conky will reload. But if you changed one of your dependency scripts (e.g. because you changed a variable and want to see the consequences) you will have to reload conky
{{UserCmd|command=killall conky && conky -c ~/.config/config/conky.conkyrc}}

===Troubleshooting & Tips=== 

====Missing rings==== 


To be able to use LUA scripts to execute drawing functions like clock rings - you will a conky package compiled with LUA support. Either build the package the package {{ic|conky-lua}} from [[Arch_User_Repository|AUR]] or install the {{ic|conky-lua-nv}} from the official repo.

====Missing network information==== 
If network information is missing like download speed or network name (SSID), you need to replace the network interfaces in the configuration file with your network interface name. To get the names of your interfaces - open a terminal and execute
{{UserCmd|command=ip a | grep ' state UP' | cut -d' ' -f2 | cut -d':' -f1}}
Use the output from the command. Interface names starting with <code>en</code> is ethernet interface and names starting with <code>wl</code> is wireless interfaces. Replace all network interfaces names with (e.g. <code>wlan0</code>, <code>eth0</code>) in your <code>.conkyrc</code> text section with the interface name(s) you retrieved from the above command.

===Conky Manager=== 
An application named Conky manager exist but has not been updated for years and the configurations found in the package may work or they may not. You may install it - it can be a used as an inspiration but you should not rely on it. If you still think you it is a must have - you can build the package {{ic|conky-manager}} using [[Arch_User_Repository|AUR]]
{{UserCmd|command=pamac build conky-manager}}

==See Also== 
* The [https://github.com/brndnmtthws/conky/wiki Conky website]
* The [https://wiki.archlinux.org/index.php/conky Arch Wiki] page for Conky
</translate>
[[Category:Contents Page{{#translation:}}]]
[[Category:Applications{{#translation:}}]]