Overview

Project website www.linuxfromscratch.org
Translation process
  • Translations can be made directly.
  • Translation suggestions can be made.
  • Any authenticated user can contribute.
  • The translation uses bilingual files.
Source code repository git@git.linuxfromscratch.org:fr-lfs
Repository branch trunk
Last remote commit Automatic BLFS commit based on 0f8d3a0501f2c0daba177f874b995170e779591e 08a7650aa1
Julien Lepiller authored an hour ago
Last commit in Weblate Automatic BLFS commit based on 0f8d3a0501f2c0daba177f874b995170e779591e 08a7650aa1
Julien Lepiller authored an hour ago
Weblate repository https://translate.linuxfromscratch.org/git/faq/faq/
File mask lfs/*/chapter08/pkgmgt.po
Translation file Download lfs/fr/chapter08/pkgmgt.po
Last change March 12, 2025, 4:19 p.m.
Last change made by None
Language French
Language code fr
Text direction Left to right
Case sensitivity Case-sensitive
Number of speakers 295,510,923
Number of plurals 2
Plural type One/other
Plurals Singular 0, 1
Plural 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, …
Plural formula n > 1
2 hours ago

String statistics

Strings percent Hosted strings Words percent Hosted words Characters percent Hosted characters
Total 53 2,314 16,674
Translated 96% 51 90% 2,102 89% 14,973
Needs editing 1% 1 5% 116 5% 876
Read-only 0% 0 0% 0 0% 0
Failing checks 1% 1 5% 116 5% 876
Strings with suggestions 0% 0 0% 0 0% 0
Untranslated strings 1% 1 4% 96 4% 825
Last 12 months Previous

Activity in last 12 months

52 changes 0 changes 0 changes 0 changes 21 changes 0 changes 8 changes 0 changes 0 changes 0 changes 0 changes 0 changes 104 changes 3 changes 11 changes 0 changes 12 changes 0 changes 0 changes 0 changes 3 changes 0 changes 11 changes 0 changes
MarAprMayJunJulAugSepOctNovDecJanFeb

Quick numbers

2,232
Hosted words
52
Hosted strings
100%
Translated
1
Contributors
and previous 30 days

Trends of last 30 days

+1%
Hosted words
+100%
—
Hosted strings
+100%
—
Translated
+100%
+100%
Contributors
—
User avatar None

Resource updated
The “lfs/fr/chapter08/pkgmgt.po” file was changed. 2 hours ago
User avatar None

String added in the repository
If a package containing a shared library is updated, and if the name of the library<placeholder type="footnote" id="0"/> changes, then any packages dynamically linked to the library must be recompiled, to link against the newer library. For example, consider a package foo-1.2.3 that installs a shared library with the name <filename class='libraryfile'>libfoo.so.1</filename>. Suppose you upgrade the package to a newer version foo-1.2.4 that installs a shared library with the name <filename class='libraryfile'>libfoo.so.2</filename>. In this case, any packages that are dynamically linked to <filename class='libraryfile'>libfoo.so.1</filename> need to be recompiled to link against <filename class='libraryfile'>libfoo.so.2</filename> in order to use the new library version. You should not remove the old libraries until all the dependent packages have been recompiled.
Si un paquet contenant une bibliothèque partagée est mis à jour et si le nom de cette dernière est modifié, alors les paquets liés dynamiquement à la bibliothèque devront être recompilés pour être liés à la nouvelle bibliothèque. Notez qu'il n'y a aucune corrélation entre la version du paquet et le nom de la bibliothèque. Par exemple, prenez un paquet foo-1.2.3 qui installe une bibliothèque partagée appelée <filename class='libraryfile'>libfoo.so.1</filename>. Partons du principe que vous mettez à jour le paquet avec une nouvelle version foo-1.2.4 qui installe une bibliothèque partagée appelée <filename class='libraryfile'>libfoo.so.2</filename>. Dans ce cas, tous les paquets liés dynamiquement à <filename class='libraryfile'>libfoo.so.1</filename> doivent être recompilés pour être liés à <filename class='libraryfile'>libfoo.so.2</filename>. Vous ne devez pas supprimer les anciennes bibliothèques avant que les paquets indépendants ne soient tous recompilés.
2 hours ago
User avatar None

Source string changed
If a package containing a shared library is updated, and if the name of the library<placeholder type="footnote" id="0"/> changes, then any packages dynamically linked to the library must be recompiled, to link against the newer library. (Note that there is no correlation between the package version and the name of the library.) For example, consider a package foo-1.2.3 that installs a shared library with the name <filename class='libraryfile'>libfoo.so.1</filename>. Suppose you upgrade the package to a newer version foo-1.2.4 that installs a shared library with the name <filename class='libraryfile'>libfoo.so.2</filename>. In this case, any packages that are dynamically linked to <filename class='libraryfile'>libfoo.so.1</filename> need to be recompiled to link against <filename class='libraryfile'>libfoo.so.2</filename> in order to use the new library version. You should not remove the old libraries until all the dependent packages have been recompiled.
2 hours ago
User avatar None

String added in the repository
The name of a shared library is the string coded in the <constant>DT_SONAME</constant> entry of its ELF dynamic section. You can get it with the <command>readelf -d <replaceable>&lt;library file&gt;</replaceable> | grep SONAME</command> command. In most cases it's suffixed with <literal>.so.<replaceable>&lt;a version number&gt;</replaceable></literal>, but there are some cases where it contains multiple numbers for versioning (like <filename>libbz2.so.1.0</filename>), contains the version number before the <filename class='extension'>.so</filename> suffix (like <filename>libbfd-&binutils-version;</filename>), or does not contain any version number at all (for example <filename>libmemusage.so</filename>). Generally there is no correlation between the package version and the version number(s) in the library name.
 
2 hours ago
User avatar None

Changes committed
Changes committed 2 days ago
User avatar admin

Translation completed
Translation completed 2 days ago
User avatar admin

Translation added
If you want to deploy the LFS system onto a system with a different CPU, when you build <xref linkend='ch-system-gmp'/> and <xref linkend='ch-system-libffi'/> you must follow the notes about overriding the architecture-specific optimization to produce libraries suitable for both the host system and the system(s) where you'll deploy the LFS system. Otherwise you'll get <computeroutput>Illegal Instruction</computeroutput> errors running LFS.
Si vous voulez déployer le système LFS sur un système avec un autre CPU, vous devez suivre les notes sur la modification de l'optimisation dépendant de l'architecture lors de la construction de <xref linkend='ch-system-gmp'/> et <xref linkend='ch-system-libffi'/> pour produire des bibliothèques compatibles à la fois avec le système hôte et les systèmes sur lesquels vous allez déployer le système LFS. Dans le cas contraire, vous obtiendrez des erreurs de type <computeroutput>Illegal Instruction</computeroutput> sur le système LFS.
2 days ago
User avatar None

Resource updated
The “lfs/fr/chapter08/pkgmgt.po” file was changed. 3 days ago
User avatar None

String added in the repository
If you want to deploy the LFS system onto a system with a different CPU, when you build <xref linkend='ch-system-gmp'/> and <xref linkend='ch-system-libffi'/> you must follow the notes about overriding the architecture-specific optimization to produce libraries suitable for both the host system and the system(s) where you'll deploy the LFS system. Otherwise you'll get <computeroutput>Illegal Instruction</computeroutput> errors running LFS.
 
3 days ago
User avatar admin

Resource updated
The “lfs/fr/chapter08/pkgmgt.po” file was changed. 6 months ago
Browse all translation changes