guix/documentation-manual — French @ Fedora Weblate: The ``monolithic'' @code{texlive} package: it comes with @emph{every single @TeX{} …

Zen

Translation

Source change

English type: itemize

French

Needs editing

Skip

	English	French	Actions
	The @code{debug} output mechanism in Guix is implemented by the @code{gnu-build-system} (@pxref{Build Systems}). Currently, it is opt-in---debugging information is available only for the packages with definitions explicitly declaring a @code{debug} output. To check whether a package has a @code{debug} output, use @command{guix package --list-available} (@pxref{Invoking guix package}).	Le mécanisme de sortie @code{debug} dans Guix est implémenté par le @code{gnu-build-system} (@pxref{Build Systems}). Actuellement, ce n'est pas obligatoire — les informations de débogage sont disponibles uniquement si les définitions déclarent explicitement une sortie @code{debug}. Cela pourrait être modifié tout en permettant aux paquets de s'en passer dans le futur si nos serveurs de construction peuvent tenir la charge. Pour vérifier si un paquet a une sortie @code{debug}, utilisez @command{guix package --list-available} (@pxref{Invoquer guix package}).
	Read on for how to deal with packages lacking a @code{debug} output.	Continuez à lire pour apprendre comment gérer les paquets qui n'ont pas de sortie @code{debug}.
	As we saw above, some packages, but not all, provide debugging info in a @code{debug} output. What can you do when debugging info is missing? The @option{--with-debug-info} option provides a solution to that: it allows you to rebuild the package(s) for which debugging info is missing---and only those---and to graft those onto the application you're debugging. Thus, while it's not as fast as installing a @code{debug} output, it is relatively inexpensive.	Comme nous l'avons montré, certains paquets, mais pas tous, fournissent des informations de débogage dans une sortie @code{debug}. Que faire lorsque les informations de débogage sont manquantes ? L'option @option{--with-debug-info} fournit une solution à cela : il vous permet de reconstruire les paquets pour lesquels les informations de débogages sont manquantes --- et seulement ceux-là --- et les greffe sur les applications que vous déboguez. Ainsi, bien que ce ne soit pas aussi rapide qu'installer la sortie @code{debug}, ça demande relativement peu de choses.
	Let's illustrate that. Suppose you're experiencing a bug in Inkscape and would like to see what's going on in GLib, a library that's deep down in its dependency graph. As it turns out, GLib does not have a @code{debug} output and the backtrace GDB shows is all sadness:	Illustrons cela. Supposons que vous rencontriez un bogue dans Inkscape et que vous souhaitiez voir ce qui se passe dans GLib, une bibliothèque assez loin dans le graphe de dépendances. Il se trouve que GLib n'a pas de sortie @code{debug} et la trace de débogage de GDB est toute triste :
	(gdb) bt #0 0x00007ffff5f92190 in g_getenv () from /gnu/store/@dots{}-glib-2.62.6/lib/libglib-2.0.so.0 #1 0x00007ffff608a7d6 in gobject_init_ctor () from /gnu/store/@dots{}-glib-2.62.6/lib/libgobject-2.0.so.0 #2 0x00007ffff7fe275a in call_init (l=<optimized out>, argc=argc@@entry=1, argv=argv@@entry=0x7fffffffcfd8, env=env@@entry=0x7fffffffcfe8) at dl-init.c:72 #3 0x00007ffff7fe2866 in call_init (env=0x7fffffffcfe8, argv=0x7fffffffcfd8, argc=1, l=<optimized out>) at dl-init.c:118	(gdb) bt #0 0x00007ffff5f92190 in g_getenv () from /gnu/store/@dots{}-glib-2.62.6/lib/libglib-2.0.so.0 #1 0x00007ffff608a7d6 in gobject_init_ctor () from /gnu/store/@dots{}-glib-2.62.6/lib/libgobject-2.0.so.0 #2 0x00007ffff7fe275a in call_init (l=<optimized out>, argc=argc@@entry=1, argv=argv@@entry=0x7fffffffcfd8, env=env@@entry=0x7fffffffcfe8) at dl-init.c:72 #3 0x00007ffff7fe2866 in call_init (env=0x7fffffffcfe8, argv=0x7fffffffcfd8, argc=1, l=<optimized out>) at dl-init.c:118
	To address that, you install Inkscape linked against a variant GLib that contains debug info:	Pour corriger cela, vous installez Inkscape lié à une variante de GLib qui contient les informations de débogage :
	This time, debugging will be a whole lot nicer:	Cette fois-ci, le débogage a bien plus d'informations :
	$ gdb --args sh -c 'exec inkscape' @dots{} (gdb) b g_getenv Function "g_getenv" not defined. Make breakpoint pending on future shared library load? (y or [n]) y Breakpoint 1 (g_getenv) pending. (gdb) r Starting program: /gnu/store/@dots{}-profile/bin/sh -c exec\ inkscape @dots{} (gdb) bt #0 g_getenv (variable=variable@@entry=0x7ffff60c7a2e "GOBJECT_DEBUG") at ../glib-2.62.6/glib/genviron.c:252 #1 0x00007ffff608a7d6 in gobject_init () at ../glib-2.62.6/gobject/gtype.c:4380 #2 gobject_init_ctor () at ../glib-2.62.6/gobject/gtype.c:4493 #3 0x00007ffff7fe275a in call_init (l=<optimized out>, argc=argc@@entry=3, argv=argv@@entry=0x7fffffffd088, env=env@@entry=0x7fffffffd0a8) at dl-init.c:72 @dots{}	$ gdb --args sh -c 'exec inkscape' @dots{} (gdb) b g_getenv Function "g_getenv" not defined. Make breakpoint pending on future shared library load? (y or [n]) y Breakpoint 1 (g_getenv) pending. (gdb) r Starting program: /gnu/store/@dots{}-profile/bin/sh -c exec\ inkscape @dots{} (gdb) bt #0 g_getenv (variable=variable@@entry=0x7ffff60c7a2e "GOBJECT_DEBUG") at ../glib-2.62.6/glib/genviron.c:252 #1 0x00007ffff608a7d6 in gobject_init () at ../glib-2.62.6/gobject/gtype.c:4380 #2 gobject_init_ctor () at ../glib-2.62.6/gobject/gtype.c:4493 #3 0x00007ffff7fe275a in call_init (l=<optimized out>, argc=argc@@entry=3, argv=argv@@entry=0x7fffffffd088, env=env@@entry=0x7fffffffd0a8) at dl-init.c:72 @dots{}
	Much better!	Bien mieux !
	Note that there can be packages for which @option{--with-debug-info} will not have the desired effect. @xref{Package Transformation Options, @option{--with-debug-info}}, for more information.	Remarquez qu'il y a des paquets pour lesquels @option{--with-debug-info} n'a pas l'effet désiré. @xref{Package Transformation Options, @option{--with-debug-info}}, pour plus d'informations.
	Using @TeX{} and @LaTeX{}	Utiliser @TeX{} et @LaTeX{}
	@TeX{} packages	paquets @TeX{}
	@LaTeX{} packages	paquets @LaTeX{}
	Guix provides packages for the @TeX{}, @LaTeX{}, ConTeXt, LuaTeX, and related typesetting systems, taken from the @uref{https://www.tug.org/texlive/, @TeX{} Live distribution}. Because @TeX{} Live is so huge and because finding one's way in this maze is tricky, this section provides some guidance on how to deploy the relevant packages to compile @TeX{} and @LaTeX{} documents.	Guix fournit des paquets pour les systèmes de composition @TeX{}, @LaTeX{}, ConTeXt, LuaTeX etc, qui font parti de la @uref{https://www.tug.org/texlive/, distribution @TeX{} Live}. Cependant, comme @TeX{} Live est énorme et comme s'y retrouver est difficile, nous pensons que vous, chère utilisatrice, cher utilisateur, apprécierez un peu d'aide sur la manière de déployer les paquets utiles pour que vous puissiez compiler vos documents @TeX{} et @LaTeX{}.
	@TeX{} Live currently comes in two mutually exclusive flavors in Guix:	@TeX{} Live est actuellement proposé dans deux variantes dans Guix :
	The ``monolithic'' @code{texlive} package: it comes with @emph{every single @TeX{} Live package} (roughly 4,200), but it is huge---more than 4@tie{}GiB for a single package!	Le paquet @code{texlive} « monolithique » : il possède @emph{tous les paquets @TeX{} Live} (plus de 7 000), mais il est énorme (plus de 4@tie{}Gio pour un seul paquet !).
	A ``modular'' @TeX{} Live distribution, in which you only install the packages you need, whose name is always prefixed with @samp{texlive-}.
	To insist, these two flavors cannot be combined@footnote{No rule without exception! As the monolithic @TeX{} Live does not contain the @command{biber} executable, it is okay to combine it with @code{texlive-biber}, which does.}. If in the modular setting your document does not compile, the solution is not to add the monolithic @code{texlive} package, but to add the set of missing packages from the modular distribution.
	Building a coherent system that provides all the essential tools and, at the same time, satisfies all of its internal dependencies can be a difficult task. It is therefore recommended to start with sets of packages, called @dfn{collections}, and @dfn{schemes}, the name for collections of collections. The following command lists available schemes and collections (@pxref{guix-search,, Invoking guix package}):
	guix search texlive-$scheme\\|collection$ \| recsel -p name,description
	If needed, you may then complete your system with individual packages, particularly when they belong to a large collection you're not otherwise interested in.
	For instance, the following manifest is a reasonable, yet frugal starting point for a French @LaTeX{} user:
	(specifications->manifest '("rubber"	(specifications->manifest '("rubber"
	"texlive-scheme-basic" "texlive-collection-latexrecommended" "texlive-collection-fontsrecommended" "texlive-babel-french"
	;; From "latexextra" collection. "texlive-tabularray" ;; From "binextra" collection. "texlive-texdoc"))
	If you come across a document that does not compile in such a basic setting, the main difficulty is finding the missing packages. In this case, @command{pdflatex} and similar commands tend to fail with obscure error messages along the lines of:
	doc.tex: File `tikz.sty' not found. doc.tex:7: Emergency stop.	doc.tex: File `tikz.sty' not found. doc.tex:7: Emergency stop.
	or, for a missing font:	ou, pour une police manquante :
	kpathsea: Running mktexmf phvr7t ! I can't find file `phvr7t'.	kpathsea: Running mktexmf phvr7t ! I can't find file `phvr7t'.
	How do you determine what the missing package is? In the first case, you will find the answer by running:	Comment déterminer le paquet manquant ? Dans le premier cas, vous trouverez la réponse avec :
	$ guix search texlive tikz name: texlive-pgf version: 59745 @dots{}	$ guix search texlive tikz name: texlive-pgf version: 59745 @dots{}

anonymous

Suggestion added

Suggested change:

Failing checks:

Mismatched full stop Mismatched exclamation mark a year ago

Loading…

anonymous

Suggestion added

English

French 0 characters edited Current translation

a year ago

None

String updated in the repository

English

French 170 characters edited Current translation Needs editing

a year ago

None

Source string changed

English 22 characters edited

a year ago

Browse all string changes

Things to check

Suggestions

There is 1 suggestion for this string.

View

Mismatched exclamation mark

Source and translation do not both end with an exclamation mark

Reset

Mismatched full stop

Source and translation do not both end with a full stop

Reset

Glossary

English	French
package	paquet	guix Glossary

15214426 String information

Source string description

type: itemize

Source string location

guix-git/doc/guix.texi:49823

String age

a year ago

Last updated

18 hours ago

Source string age

a year ago

Translation file

po/doc/guix-manual.fr.po, string 15649

Shortcut	Action
`?`	Open available keyboard shortcuts.
`Alt` + `Home`	Navigate to the first translation in the current search.
`Alt` + `End`	Navigate to the last translation in the current search.
`Alt` + `PageUp` or `Ctrl` + `↑` or `Alt` + `↑` or `Cmd` + `↑` or	Navigate to the last translation in the current search.
`Alt` + `PageDown` or `Ctrl` + `↓` or `Alt` + `↓` or `Cmd` + `↓` or	Navigate to the next translation in the current search.
`Ctrl` + `Enter` or `Cmd` + `Enter`	Submit current form; this works the same as pressing Save and continue while editing translation.
`Ctrl` + `Shift` + `Enter` or `Cmd` + `Shift` +`Enter`	Unmark translation as Needing edit and submit it.
`Alt` + `Enter` or `Option` + `Enter`	Submit the string as a suggestion; this works the same as pressing Suggest while editing translation.
`Ctrl` + `E` or `Cmd` + `E`	Focus on translation editor.
`Ctrl` + `U` or `Cmd` + `U`	Focus on comment editor.
`Ctrl` + `M` or `Cmd` + `M`	Shows Automatic suggestions tab.
`Ctrl` + `1` to `Ctrl` + `9` or `Cmd` + `1` to `Cmd` + `9`	Copies placeable of a given number from source string.
`Ctrl` + `M` followed by `1` to `9` or `Cmd` + `M` followed by `1` to `9`	Copy the machine translation of a given number to current translation.
`Ctrl` + `I` followed by `1` to `9` or `Cmd` + `I` followed by `1` to `9`	Ignore one item in the list of failing checks.
`Ctrl` + `J` or `Cmd` + `J`	Shows the Nearby strings tab.
`Ctrl` + `S` or `Cmd` + `S`	Focus on search field.
`Ctrl` + `O` or `Cmd` + `O`	Copy the source string.
`Ctrl` + `Y` or `Cmd` + `Y`	Toggle the Needs editing checkbox.
`→`	Browse the next translation string.
`←`	Browse the previous translation string.