| 1 |
# Roland Mas <[email protected]>, 2015. |
| 2 |
msgid "" |
| 3 |
msgstr "" |
| 4 |
"Project-Id-Version: 0\n" |
| 5 |
"POT-Creation-Date: 2022-07-30 18:23+0200\n" |
| 6 |
"PO-Revision-Date: 2022-07-30 18:44+0200\n" |
| 7 |
"Last-Translator: Galina Anikina <[email protected]>\n" |
| 8 |
"Language-Team: French <https://hosted.weblate.org/projects/debian-handbook/15_debian-packaging/fr/>\n" |
| 9 |
"Language: fr-FR\n" |
| 10 |
"MIME-Version: 1.0\n" |
| 11 |
"Content-Type: application/x-publican; charset=UTF-8\n" |
| 12 |
"Content-Transfer-Encoding: 8bit\n" |
| 13 |
"Plural-Forms: nplurals=2; plural=n > 1;\n" |
| 14 |
"X-Generator: Weblate 2.18-dev\n" |
| 15 |
|
| 16 |
msgid "Backport" |
| 17 |
msgstr "Rétroportage" |
| 18 |
|
| 19 |
msgid "Rebuild" |
| 20 |
msgstr "Recompilation" |
| 21 |
|
| 22 |
msgid "Source package" |
| 23 |
msgstr "Paquet source" |
| 24 |
|
| 25 |
msgid "Archive" |
| 26 |
msgstr "Archive" |
| 27 |
|
| 28 |
msgid "Meta-package" |
| 29 |
msgstr "Métapaquet" |
| 30 |
|
| 31 |
msgid "Debian Developer" |
| 32 |
msgstr "Développeur Debian" |
| 33 |
|
| 34 |
#, fuzzy |
| 35 |
#| msgid "Creating a Debian Package" |
| 36 |
msgid "Debian Package" |
| 37 |
msgstr "Conception d'un paquet Debian" |
| 38 |
|
| 39 |
msgid "Maintainer" |
| 40 |
msgstr "Mainteneur" |
| 41 |
|
| 42 |
msgid "Creating a Debian Package" |
| 43 |
msgstr "Conception d'un paquet Debian" |
| 44 |
|
| 45 |
msgid "It is quite common, for an administrator who has been handling Debian packages in a regular fashion, to eventually feel the need to create their own packages, or to modify an existing package. This chapter aims to answer the most common questions in this field, and provide the required elements to take advantage of the Debian infrastructure in the best way. With any luck, after trying your hand for local packages, you may even feel the need to go further than that and join the Debian project itself!" |
| 46 |
msgstr "Manipuler régulièrement des paquets Debian provoque tôt ou tard le besoin de créer le sien ou d'en modifier un. Ce chapitre essaie de répondre à vos interrogations en la matière et fournit des éléments pour tirer le meilleur parti de l'infrastructure offerte par Debian. Qui sait, en ayant ainsi mis la main à la pâte, peut-être irez-vous plus loin et deviendrez-vous développeur Debian !" |
| 47 |
|
| 48 |
msgid "Rebuilding a Package from its Sources" |
| 49 |
msgstr "Recompiler un paquet depuis ses sources" |
| 50 |
|
| 51 |
#, fuzzy |
| 52 |
#| msgid "<primary>package</primary><secondary>types</secondary>" |
| 53 |
msgid "<primary>package</primary><secondary>backport</secondary>" |
| 54 |
msgstr "<primary>paquet</primary><secondary>types</secondary>" |
| 55 |
|
| 56 |
#, fuzzy |
| 57 |
#| msgid "<primary>package</primary><secondary>types</secondary>" |
| 58 |
msgid "<primary>package</primary><secondary>rebuild</secondary>" |
| 59 |
msgstr "<primary>paquet</primary><secondary>types</secondary>" |
| 60 |
|
| 61 |
msgid "Rebuilding a binary package is required under several sets of circumstances. In some cases, the administrator needs a software feature that requires the software to be compiled from sources, with a particular compilation option; in others, the software as packaged in the installed version of Debian is not recent enough. In the latter case, the administrator will usually build a more recent package taken from a newer version of Debian — such as <emphasis role=\"distribution\">Testing</emphasis> or even <emphasis role=\"distribution\">Unstable</emphasis> — so that this new package works in their <emphasis role=\"distribution\">Stable</emphasis> distribution; this operation is called “backporting”. As usual, care should be taken, before undertaking such a task, to check whether it has been done already — a quick look on the Debian Package Tracker for that package will reveal that information. <ulink type=\"block\" url=\"https://tracker.debian.org/\" /> <indexterm><primary>backport</primary></indexterm>" |
| 62 |
msgstr "Plusieurs éléments justifient la recompilation d'un paquet depuis ses sources. L'administrateur peut avoir besoin d'une fonctionnalité du logiciel qui implique de recompiler le programme en activant une option particulière ou souhaiter en installer une version plus récente que celle fournie dans sa version de Debian (dans ce cas, il recompilera un paquet plus récent récupéré dans la version <emphasis role=\"distribution\">Testing</emphasis> ou <emphasis role=\"distribution\">Unstable</emphasis> pour qu'il fonctionne parfaitement dans sa distribution <emphasis role=\"distribution\">Stable</emphasis>, opération appelée le rétroportage). On prendra soin de vérifier, avant de se lancer dans une recompilation, que personne d'autre ne s'en est déjà chargé ; on pourra vérifier en particulier sur la page dédiée du système de suivi de paquets. <ulink type=\"block\" url=\"https://tracker.debian.org/\" /> <indexterm><primary>rétroportage</primary></indexterm>" |
| 63 |
|
| 64 |
msgid "Getting the Sources" |
| 65 |
msgstr "Récupérer les sources" |
| 66 |
|
| 67 |
#, fuzzy |
| 68 |
#| msgid "<primary>package</primary><secondary>types</secondary>" |
| 69 |
msgid "<primary>package</primary><secondary>source</secondary>" |
| 70 |
msgstr "<primary>paquet</primary><secondary>types</secondary>" |
| 71 |
|
| 72 |
#, fuzzy |
| 73 |
#| msgid "<primary>package</primary><secondary>types</secondary>" |
| 74 |
msgid "<primary><command>apt</command></primary><secondary><literal>source</literal></secondary>" |
| 75 |
msgstr "<primary>paquet</primary><secondary>types</secondary>" |
| 76 |
|
| 77 |
#, fuzzy |
| 78 |
#| msgid "<primary>package</primary><secondary>types</secondary>" |
| 79 |
msgid "<primary><command>apt-get</command></primary><secondary><literal>source</literal></secondary>" |
| 80 |
msgstr "<primary>paquet</primary><secondary>types</secondary>" |
| 81 |
|
| 82 |
#, fuzzy |
| 83 |
#| msgid "<primary>package</primary><secondary>types</secondary>" |
| 84 |
msgid "<primary><command>apt</command></primary><secondary><literal>update</literal></secondary>" |
| 85 |
msgstr "<primary>paquet</primary><secondary>types</secondary>" |
| 86 |
|
| 87 |
#, fuzzy |
| 88 |
#| msgid "<primary>package</primary><secondary>types</secondary>" |
| 89 |
msgid "<primary><command>apt-get</command></primary><secondary><literal>update</literal></secondary>" |
| 90 |
msgstr "<primary>paquet</primary><secondary>types</secondary>" |
| 91 |
|
| 92 |
msgid "<primary><filename>/etc</filename></primary><secondary><filename>/etc/apt/</filename></secondary><see>APT</see>" |
| 93 |
msgstr "" |
| 94 |
|
| 95 |
#, fuzzy |
| 96 |
#| msgid "<primary><literal>Build-Depends</literal>, control field</primary>" |
| 97 |
msgid "<primary><literal>deb-src</literal></primary>" |
| 98 |
msgstr "<primary><literal>Build-Depends</literal>, champ d'en-tête du paquet source</primary>" |
| 99 |
|
| 100 |
msgid "Rebuilding a Debian package starts with getting its source code. The easiest way is to use the <command>apt-get source <replaceable>package-name</replaceable></command> command. This command requires a <literal>deb-src</literal> line in the <filename>/etc/apt/sources.list</filename> file, and up-to-date index files (i.e. <command>apt-get update</command>). These conditions should already be met if you followed the instructions from the chapter dealing with APT configuration (see <xref linkend=\"sect.apt-sources.list\" />). Note, however, that you will be downloading the source packages from the Debian version mentioned in the <literal>deb-src</literal> line." |
| 101 |
msgstr "" |
| 102 |
|
| 103 |
#, fuzzy |
| 104 |
#| msgid "Rebuilding a Debian package starts with getting its source code. The easiest way is to use the <command>apt-get source <replaceable>source-package-name</replaceable></command> command. This command requires a <literal>deb-src</literal> line in the <filename>/etc/apt/sources.list</filename> file, and up-to-date index files (i.e. <command>apt-get update</command>). These conditions should already be met if you followed the instructions from the chapter dealing with APT configuration (see <xref linkend=\"sect.apt-sources.list\" />). Note however, that you will be downloading the source packages from the Debian version mentioned in the <literal>deb-src</literal> line. If you need another version, you may need to download it manually from a Debian mirror or from the web site. This involves fetching two or three files (with extensions <filename>*.dsc</filename> — for <emphasis>Debian Source Control</emphasis> — <filename>*.tar.<replaceable>comp</replaceable></filename>, and sometimes <filename>*.diff.gz</filename> or <filename>*.debian.tar.<replaceable>comp</replaceable></filename> — <replaceable>comp</replaceable> taking one value among <literal>gz</literal>, <literal>bz2</literal> or <literal>xz</literal> depending on the compression tool in use), then run the <command>dpkg-source -x <replaceable>file.dsc</replaceable></command> command. If the <filename>*.dsc</filename> file is directly accessible at a given URL, there is an even simpler way to fetch it all, with the <command>dget <replaceable>URL</replaceable></command> command. This command (which can be found in the <emphasis role=\"pkg\">devscripts</emphasis> package) fetches the <filename>*.dsc</filename> file at the given address, then analyzes its contents, and automatically fetches the file or files referenced within. Once everything has been downloaded, it extracts the source package (unless the <literal>-d</literal> or <literal>--download-only</literal> option is used)." |
| 105 |
msgid "If you need another version, you may need to download it manually from a Debian mirror or from the web site. This involves fetching two or three files (with extensions <filename>*.dsc</filename> — for <emphasis>Debian Source Control</emphasis> — <filename>*.tar.<replaceable>comp</replaceable></filename>, and sometimes <filename>*.diff.gz</filename> or <filename>*.debian.tar.<replaceable>comp</replaceable></filename> — <replaceable>comp</replaceable> taking one value among <literal>gz</literal>, <literal>bz2</literal> or <literal>xz</literal> depending on the compression tool in use), then run the <command>dpkg-source -x <replaceable>file.dsc</replaceable></command> command. If the <filename>*.dsc</filename> file is directly accessible at a given URL, there is an even simpler way to fetch it all, with the <command>dget <replaceable>URL</replaceable></command> command. This command (which can be found in the <emphasis role=\"pkg\">devscripts</emphasis> package) fetches the <filename>*.dsc</filename> file at the given address, then analyzes its contents, and automatically fetches the file or files referenced within. Once everything has been downloaded, it verifies the integrity of the downloaded source packages using <command>dscverify</command>, and it extracts the source package (unless the <literal>-d</literal> or <literal>--download-only</literal> option is used). The Debian keyring is needed, unless the option <literal>-u</literal> is supplied." |
| 106 |
msgstr "Pour recompiler un paquet Debian, il faut commencer par rapatrier son code source. Le moyen le plus simple est d'employer la commande <command>apt-get source <replaceable>nom-paquet-source</replaceable></command>, qui nécessite la présence d'une ligne de type <literal>deb-src</literal> dans le fichier <filename>/etc/apt/sources.list</filename> et l'exécution préalable de la commande <command>apt-get update</command>. C'est déjà le cas si vous avez suivi les instructions du chapitre portant sur la configuration d'APT (voir <xref linkend=\"sect.apt-sources.list\" />). Notez cependant que vous téléchargerez les paquetages sources du paquet disponible dans la version de Debian désignée par la ligne <literal>deb-src</literal> de ce fichier de configuration. Si vous souhaitez en rapatrier une version particulière, il vous faudra peut-être la télécharger manuellement depuis un miroir Debian ou depuis le site web : récupérer deux ou trois fichiers (d'extensions <filename>*.dsc</filename> — pour <foreignphrase>Debian Source Control</foreignphrase> — <filename>*.tar.<replaceable>comp</replaceable></filename> et parfois <filename>*.diff.gz</filename> ou <filename>*.debian.tar.<replaceable>comp</replaceable></filename> — <replaceable>comp</replaceable> pouvant prendre les valeurs <literal>gz</literal>, <literal>bz2</literal> ou <literal>xz</literal> selon l'outil de compression employé), puis exécuter la commande <command>dpkg-source -x <replaceable>fichier.dsc</replaceable></command>. Si le fichier <filename>*.dsc</filename> est disponible à une URL donnée, on pourra même se simplifier la vie en utilisant <command>dget <replaceable>URL</replaceable></command> : cette commande (qui fait partie du paquet <emphasis role=\"pkg\">devscripts</emphasis>) récupère le <filename>*.dsc</filename> à l'adresse indiquée, en analyse le contenu et récupère automatiquement le ou les fichiers qu'il référence. Le paquet source est même extrait localement (à moins que l'option <literal>-d</literal> ou <literal>--download-only</literal> soit spécifiée)." |
| 107 |
|
| 108 |
msgid "<primary><emphasis role=\"pkg\">devscripts</emphasis></primary>" |
| 109 |
msgstr "<primary><emphasis role=\"pkg\">devscripts</emphasis></primary>" |
| 110 |
|
| 111 |
#, fuzzy |
| 112 |
#| msgid "<primary><command>debi</command></primary>" |
| 113 |
msgid "<primary><command>dscverify</command></primary>" |
| 114 |
msgstr "<primary><command>debi</command></primary>" |
| 115 |
|
| 116 |
#, fuzzy |
| 117 |
#| msgid "<primary><command>dput</command></primary>" |
| 118 |
msgid "<primary><command>dget</command></primary>" |
| 119 |
msgstr "<primary><command>dput</command></primary>" |
| 120 |
|
| 121 |
#, fuzzy |
| 122 |
#| msgid "<primary><command>dput</command></primary>" |
| 123 |
msgid "<primary><command>dpkg-source</command></primary>" |
| 124 |
msgstr "<primary><command>dput</command></primary>" |
| 125 |
|
| 126 |
#, fuzzy |
| 127 |
#| msgid "<primary><filename>Makefile</filename></primary>" |
| 128 |
msgid "<primary><filename>.dsc</filename></primary>" |
| 129 |
msgstr "<primary><filename>Makefile</filename></primary>" |
| 130 |
|
| 131 |
#, fuzzy |
| 132 |
#| msgid "<primary><filename>Makefile</filename></primary>" |
| 133 |
msgid "<primary><filename>.diff.gz</filename></primary>" |
| 134 |
msgstr "<primary><filename>Makefile</filename></primary>" |
| 135 |
|
| 136 |
#, fuzzy |
| 137 |
#| msgid "<primary>package</primary><secondary>types</secondary>" |
| 138 |
msgid "<primary><filename>.debian.tar</filename></primary><secondary><filename>.tar.gz</filename></secondary>" |
| 139 |
msgstr "<primary>paquet</primary><secondary>types</secondary>" |
| 140 |
|
| 141 |
msgid "<primary><filename>.debian.tar</filename></primary><secondary><filename>.tar.bz2</filename></secondary>" |
| 142 |
msgstr "" |
| 143 |
|
| 144 |
#, fuzzy |
| 145 |
#| msgid "<primary>package</primary><secondary>types</secondary>" |
| 146 |
msgid "<primary><filename>.debian.tar</filename></primary><secondary><filename>.tar.xz</filename></secondary>" |
| 147 |
msgstr "<primary>paquet</primary><secondary>types</secondary>" |
| 148 |
|
| 149 |
#, fuzzy |
| 150 |
#| msgid "<primary>package</primary><secondary>types</secondary>" |
| 151 |
msgid "<primary><filename>.tar</filename></primary><secondary><filename>.tar.gz</filename></secondary>" |
| 152 |
msgstr "<primary>paquet</primary><secondary>types</secondary>" |
| 153 |
|
| 154 |
#, fuzzy |
| 155 |
#| msgid "<primary>package</primary><secondary>types</secondary>" |
| 156 |
msgid "<primary><filename>.tar</filename></primary><secondary><filename>.tar.bz2</filename></secondary>" |
| 157 |
msgstr "<primary>paquet</primary><secondary>types</secondary>" |
| 158 |
|
| 159 |
#, fuzzy |
| 160 |
#| msgid "<primary>package</primary><secondary>types</secondary>" |
| 161 |
msgid "<primary><filename>.tar</filename></primary><secondary><filename>.tar.xz</filename></secondary>" |
| 162 |
msgstr "<primary>paquet</primary><secondary>types</secondary>" |
| 163 |
|
| 164 |
#, fuzzy |
| 165 |
#| msgid "<primary>package</primary><secondary>types</secondary>" |
| 166 |
msgid "<primary><command>apt</command></primary><secondary><literal>--download-only</literal></secondary>" |
| 167 |
msgstr "<primary>paquet</primary><secondary>types</secondary>" |
| 168 |
|
| 169 |
#, fuzzy |
| 170 |
#| msgid "<primary>package</primary><secondary>types</secondary>" |
| 171 |
msgid "<primary><command>apt-get</command></primary><secondary><literal>--download-only</literal></secondary>" |
| 172 |
msgstr "<primary>paquet</primary><secondary>types</secondary>" |
| 173 |
|
| 174 |
#, fuzzy |
| 175 |
#| msgid "<primary><emphasis role=\"pkg\">devscripts</emphasis></primary>" |
| 176 |
msgid "<primary><emphasis role=\"pkg\">debian-archive-keyring</emphasis></primary>" |
| 177 |
msgstr "<primary><emphasis role=\"pkg\">devscripts</emphasis></primary>" |
| 178 |
|
| 179 |
msgid "Making Changes" |
| 180 |
msgstr "Effectuer les modifications" |
| 181 |
|
| 182 |
msgid "Let us use the <emphasis role=\"pkg\">samba</emphasis> package as an example." |
| 183 |
msgstr "" |
| 184 |
|
| 185 |
msgid "" |
| 186 |
"<computeroutput>$ </computeroutput><userinput>apt source samba\n" |
| 187 |
"</userinput><computeroutput>Reading package lists... Done\n" |
| 188 |
"NOTICE: 'samba' packaging is maintained in the 'Git' version control system at:\n" |
| 189 |
"https://salsa.debian.org/samba-team/samba.git\n" |
| 190 |
"Please use:\n" |
| 191 |
"git clone https://salsa.debian.org/samba-team/samba.git\n" |
| 192 |
"to retrieve the latest (possibly unreleased) updates to the package.\n" |
| 193 |
"Need to get 12.3 MB of source archives.\n" |
| 194 |
"Get:1 http://security.debian.org/debian-security bullseye-security/main samba 2:4.13.13+dfsg-1~deb11u3 (dsc) [4,514 B]\n" |
| 195 |
"Get:2 http://security.debian.org/debian-security bullseye-security/main samba 2:4.13.13+dfsg-1~deb11u3 (tar) [11.8 MB]\n" |
| 196 |
"Get:3 http://security.debian.org/debian-security bullseye-security/main samba 2:4.13.13+dfsg-1~deb11u3 (diff) [468 kB]\n" |
| 197 |
"Fetched 12.3 MB in 3s (4,582 kB/s)\n" |
| 198 |
"dpkg-source: info: extracting samba in samba-4.13.13+dfsg\n" |
| 199 |
"dpkg-source: info: unpacking samba_4.13.13+dfsg.orig.tar.xz\n" |
| 200 |
"dpkg-source: info: unpacking samba_4.13.13+dfsg-1~deb11u3.debian.tar.xz\n" |
| 201 |
"dpkg-source: info: using patch list from debian/patches/series\n" |
| 202 |
"dpkg-source: info: applying 07_private_lib\n" |
| 203 |
"dpkg-source: info: applying bug_221618_precise-64bit-prototype.patch\n" |
| 204 |
"dpkg-source: info: applying [...]\n" |
| 205 |
"</computeroutput>" |
| 206 |
msgstr "" |
| 207 |
|
| 208 |
#, fuzzy |
| 209 |
#| msgid "The source of the package is now available in a directory named after the source package and its version (for instance, <emphasis>samba-4.1.17+dfsg</emphasis>); this is where we'll work on our local changes." |
| 210 |
msgid "The source of the package is now available in a directory named after the source package and its version (<filename>samba-4.13.13+dfsg</filename>); this is where we'll work on our local changes." |
| 211 |
msgstr "Les sources maintenant disponibles dans un répertoire portant le nom du paquet source et sa version (par exemple <emphasis>samba-4.1.17+dfsg</emphasis>), nous pouvons nous y rendre pour y effectuer nos modifications." |
| 212 |
|
| 213 |
#, fuzzy |
| 214 |
#| msgid "The first thing to do is to change the package version number, so that the rebuilt packages can be distinguished from the original packages provided by Debian. Assuming the current version is <literal>2:4.1.17+dfsg-2</literal>, we can create version <literal>2:4.1.17+dfsg-2falcot1</literal>, which clearly indicates the origin of the package. This makes the package version number higher than the one provided by Debian, so that the package will easily install as an update to the original package. Such a change is best effected with the <command>dch</command> command (<emphasis>Debian CHangelog</emphasis>) from the <emphasis role=\"pkg\">devscripts</emphasis> package, with an command such as <command>dch --local falcot</command>. This invokes a text editor (<command>sensible-editor</command> — this should be your favorite editor if it is mentioned in the <varname>VISUAL</varname> or <varname>EDITOR</varname> environment variables, and the default editor otherwise) to allow documenting the differences brought by this rebuild. This editor shows us that <command>dch</command> really did change the <filename>debian/changelog</filename> file." |
| 215 |
msgid "The first thing to do is to change the package version number, so that the rebuilt packages can be distinguished from the original packages provided by Debian. Assuming the current version is <literal>2:4.13.13+dfsg-1~deb11u3</literal>, we can create version <literal>2:4.13.13+dfsg-1~deb11u3+falcot1</literal>, which clearly indicates the origin of the package. This makes the package version number higher than the one provided by Debian, so that the package will easily install as an update to the original package. Such a change is best effected with the <command>dch</command> command (<emphasis>Debian CHangelog</emphasis>) from the <emphasis role=\"pkg\">devscripts</emphasis> package. <indexterm><primary><command>dch</command></primary></indexterm> <indexterm><primary><emphasis role=\"pkg\">devscripts</emphasis></primary></indexterm> <indexterm><primary>package</primary><secondary>version</secondary></indexterm>" |
| 216 |
msgstr "La première modification à apporter est de changer le numéro de version du paquet pour distinguer les paquets recompilés des originaux fournis par Debian. Supposons que la version actuelle soit <literal>2:4.1.17+dfsg-2</literal> ; nous pouvons créer une version <literal>2:4.1.17+dfsg-2falcot1</literal>, ce qui désigne clairement l'origine du paquet. De cette manière, la version est supérieure à celle fournie par Debian et le paquet s'installera facilement en tant que mise à jour de l'original. Pour effectuer ce changement, il est préférable d'utiliser le programme <command>dch</command> <foreignphrase>(Debian CHangelog)</foreignphrase> du paquet <emphasis role=\"pkg\">devscripts</emphasis> en saisissant <command>dch --local falcot</command>. Cette commande démarre un éditeur de texte (<command>sensible-editor</command> — votre éditeur favori si vous l'avez précisé dans la variable d'environnement <varname>VISUAL</varname> ou <varname>EDITOR</varname>, un éditeur par défaut dans les autres cas) où l'on pourra documenter les différences apportées par cette recompilation. On peut constater que <command>dch</command> a bien modifié le fichier <filename>debian/changelog</filename>." |
| 217 |
|
| 218 |
#, fuzzy |
| 219 |
#| msgid "" |
| 220 |
#| "<computeroutput>$ </computeroutput><userinput>dpkg-buildpackage -us -uc\n" |
| 221 |
#| "</userinput><computeroutput>[...]\n" |
| 222 |
#| "</computeroutput>" |
| 223 |
msgid "" |
| 224 |
"<computeroutput>$ </computeroutput><userinput>cd 4.13.13+dfsg-1~deb11u3\n" |
| 225 |
"</userinput><computeroutput>$ </computeroutput><userinput>dch --local +falcot\n" |
| 226 |
"</userinput>" |
| 227 |
msgstr "" |
| 228 |
"<computeroutput>$ </computeroutput><userinput>dpkg-buildpackage -us -uc\n" |
| 229 |
"</userinput><computeroutput>[...]\n" |
| 230 |
"</computeroutput>" |
| 231 |
|
| 232 |
msgid "The last command invokes a text editor (<command>sensible-editor</command> — this should be your favorite editor if it is mentioned in the <varname>VISUAL</varname> or <varname>EDITOR</varname> environment variables, and the default editor otherwise) to allow documenting the differences brought by this rebuild. This editor shows us that <command>dch</command> really did change the <filename>debian/changelog</filename> file." |
| 233 |
msgstr "" |
| 234 |
|
| 235 |
#, fuzzy |
| 236 |
#| msgid "<primary><command>debi</command></primary>" |
| 237 |
msgid "<primary><command>sensible-editor</command></primary>" |
| 238 |
msgstr "<primary><command>debi</command></primary>" |
| 239 |
|
| 240 |
#, fuzzy |
| 241 |
#| msgid "<primary><filename>Makefile</filename></primary>" |
| 242 |
msgid "<primary><varname>VISUAL</varname></primary>" |
| 243 |
msgstr "<primary><filename>Makefile</filename></primary>" |
| 244 |
|
| 245 |
#, fuzzy |
| 246 |
#| msgid "<primary>package</primary><secondary>types</secondary>" |
| 247 |
msgid "<primary>environment variable</primary><secondary><varname>VISUAL</varname></secondary>" |
| 248 |
msgstr "<primary>paquet</primary><secondary>types</secondary>" |
| 249 |
|
| 250 |
#, fuzzy |
| 251 |
#| msgid "<primary><filename>Makefile</filename></primary>" |
| 252 |
msgid "<primary><varname>EDITOR</varname></primary>" |
| 253 |
msgstr "<primary><filename>Makefile</filename></primary>" |
| 254 |
|
| 255 |
#, fuzzy |
| 256 |
#| msgid "<primary>package</primary><secondary>types</secondary>" |
| 257 |
msgid "<primary>environment variable</primary><secondary><varname>EDITOR</varname></secondary>" |
| 258 |
msgstr "<primary>paquet</primary><secondary>types</secondary>" |
| 259 |
|
| 260 |
#, fuzzy |
| 261 |
#| msgid "<primary>package</primary><secondary>types</secondary>" |
| 262 |
msgid "<primary>package</primary><secondary><filename>changelog</filename></secondary>" |
| 263 |
msgstr "<primary>paquet</primary><secondary>types</secondary>" |
| 264 |
|
| 265 |
#, fuzzy |
| 266 |
#| msgid "When a change in build options is required, the changes need to be made in <filename>debian/rules</filename>, which drives the steps in the package build process. In the simplest cases, the lines concerning the initial configuration (<literal>./configure …</literal>) or the actual build (<literal>$(MAKE) …</literal> or <literal>make …</literal>) are easy to spot. If these commands are not explicitly called, they are probably a side effect of another explicit command, in which case please refer to their documentation to learn more about how to change the default behavior. With packages using <command>dh</command>, you might need to add an override for the <command>dh_auto_configure</command> or <command>dh_auto_build</command> commands (see their respective manual pages for explanations on how to achieve this)." |
| 267 |
msgid "When a change in build options is required, the changes need to be made in <filename>debian/rules</filename>, which drives the steps in the package build process. In the simplest cases, the lines concerning the initial configuration (<literal>./configure …</literal>) or the actual build (<literal>$(MAKE) …</literal> or <literal>make …</literal> or <literal>cmake …</literal> or …) are easy to spot. If these commands are not explicitly called, they are probably a side effect of another explicit command, in which case please refer to their documentation to learn more about how to change the default behavior. With packages using <command>dh</command>, you might need to add an override for the <command>dh_auto_configure</command> or <command>dh_auto_build</command> commands (see their respective manual pages and <citerefentry><refentrytitle>debhelper</refentrytitle> <manvolnum>7</manvolnum></citerefentry> for explanations on how to achieve this)." |
| 268 |
msgstr "Si une modification des options de compilation s'avère nécessaire, il faudra modifier le fichier <filename>debian/rules</filename>, qui pilote les différentes étapes de la compilation du paquet. Dans les cas les plus simples, vous repérerez facilement les lignes concernant la configuration initiale (<literal>./configure …</literal>) ou déclenchant la compilation (<literal>$(MAKE) …</literal> ou <literal>make …</literal>). En les adaptant convenablement, il est possible d'obtenir l'effet souhaité. Si ces commandes n'apparaissent pas directement, elles sont vraisemblablement appelées par une des commandes présentes. Il faudra se référer à leur documentation pour en apprendre plus sur la manière de changer le comportement par défaut. Pour les paquets qui utilisent <command>dh</command>, il sera peut-être nécessaire de surcharger les commandes <command>dh_auto_configure</command> ou <command>dh_auto_build</command> (voir leurs pages de manuel respectives pour des explications à ce sujet)." |
| 269 |
|
| 270 |
#, fuzzy |
| 271 |
#| msgid "<primary>package</primary><secondary>types</secondary>" |
| 272 |
msgid "<primary><command>dh</command></primary><secondary><command>dh_auto_build</command></secondary>" |
| 273 |
msgstr "<primary>paquet</primary><secondary>types</secondary>" |
| 274 |
|
| 275 |
#, fuzzy |
| 276 |
#| msgid "<primary>package</primary><secondary>types</secondary>" |
| 277 |
msgid "<primary><command>dh</command></primary><secondary><command>dh_auto_configure</command></secondary>" |
| 278 |
msgstr "<primary>paquet</primary><secondary>types</secondary>" |
| 279 |
|
| 280 |
#, fuzzy |
| 281 |
#| msgid "<primary>package</primary><secondary>types</secondary>" |
| 282 |
msgid "<primary><command>dh</command></primary><secondary>override target</secondary>" |
| 283 |
msgstr "<primary>paquet</primary><secondary>types</secondary>" |
| 284 |
|
| 285 |
#, fuzzy |
| 286 |
#| msgid "<primary><command>dch</command></primary>" |
| 287 |
msgid "<primary><command>dh</command></primary><seealso><command>debhelper</command></seealso>" |
| 288 |
msgstr "<primary><command>dch</command></primary>" |
| 289 |
|
| 290 |
#, fuzzy |
| 291 |
#| msgid "<primary>package</primary><secondary>Debian</secondary><tertiary>archive of</tertiary>" |
| 292 |
msgid "<primary>package</primary><secondary><filename>rules</filename></secondary><seealso><filename>rules</filename></seealso>" |
| 293 |
msgstr "<primary>paquet</primary><secondary>Debian</secondary><tertiary>archive de</tertiary>" |
| 294 |
|
| 295 |
#, fuzzy |
| 296 |
#| msgid "<primary><emphasis>debhelper</emphasis></primary>" |
| 297 |
msgid "<primary><emphasis role=\"pkg\">debhelper</emphasis></primary>" |
| 298 |
msgstr "<primary><emphasis>debhelper</emphasis></primary>" |
| 299 |
|
| 300 |
msgid "Depending on the local changes to the packages, an update may also be required in the <filename>debian/control</filename> file, which contains a description of the generated packages. In particular, this file contains <literal>Build-Depends</literal> lines controlling the list of dependencies that must be fulfilled at package build time. These often refer to versions of packages contained in the distribution the source package comes from, but which may not be available in the distribution used for the rebuild. There is no automated way to determine if a dependency is real or only specified to guarantee that the build should only be attempted with the latest version of a library — this is the only available way to force an <emphasis>autobuilder</emphasis> to use a given package version during build, which is why Debian maintainers frequently use strictly versioned build-dependencies." |
| 301 |
msgstr "Il convient parfois de s'occuper du fichier <filename>debian/control</filename>, qui renferme la description des paquets générés. Il peut être intéressant de la modifier pour qu'elle reflète les changements apportés. Par ailleurs, ce fichier contient aussi des champs <literal>Build-Depends</literal> qui donnent la liste des dépendances de génération du paquet. Celles-ci se rapportent souvent à des versions de paquets contenus dans la distribution d'origine du paquet source, qui ne sont peut-être pas disponibles dans la version utilisée pour la recompilation. Il n'existe pas de moyen automatique pour savoir si une dépendance est réelle ou si elle a été créée pour garantir que la compilation s'effectue bien avec les dernières versions d'une bibliothèque (c'est le seul moyen disponible pour forcer un <foreignphrase>autobuilder</foreignphrase> à recompiler le paquet avec une version prédéfinie d'un paquet — c'est pourquoi les mainteneurs Debian utilisent fréquemment ce procédé)." |
| 302 |
|
| 303 |
#, fuzzy |
| 304 |
#| msgid "<primary>package</primary><secondary>Debian</secondary><tertiary>archive of</tertiary>" |
| 305 |
msgid "<primary>package</primary><secondary><filename>control</filename></secondary><see><filename>control</filename></see>" |
| 306 |
msgstr "<primary>paquet</primary><secondary>Debian</secondary><tertiary>archive de</tertiary>" |
| 307 |
|
| 308 |
#, fuzzy |
| 309 |
#| msgid "<primary><literal>Build-Depends</literal>, control field</primary>" |
| 310 |
msgid "<primary><filename>control</filename></primary><secondary><literal>Build-Depends</literal>, header field</secondary>" |
| 311 |
msgstr "<primary><literal>Build-Depends</literal>, champ d'en-tête du paquet source</primary>" |
| 312 |
|
| 313 |
msgid "If you know for sure that these build-dependencies are too strict, you should feel free to relax them locally. Reading the files which document the standard way of building the software — these files are often called <filename>INSTALL</filename> — will help you figure out the appropriate dependencies. Ideally, all dependencies should be satisfiable from the distribution used for the rebuild; if they are not, a recursive process starts, whereby the packages mentioned in the <literal>Build-Depends</literal> field must be backported before the target package can be. Some packages may not need backporting, and can be installed as-is during the build process (a notable example is <emphasis role=\"pkg\">debhelper</emphasis>). Note that the backporting process can quickly become complex if you are not careful. Therefore, backports should be kept to a strict minimum when possible." |
| 314 |
msgstr "N'hésitez donc pas à modifier ces dépendances pour les assouplir si vous savez qu'elles sont trop strictes. La lecture d'éventuels fichiers documentant le mode de compilation du logiciel (souvent nommés <filename>INSTALL</filename>) vous sera sans doute utile pour retrouver les bonnes dépendances. Idéalement, il faudrait satisfaire toutes les dépendances avec les paquets disponibles dans la version utilisée pour la recompilation. Sans cela, on entre dans un processus récursif où il faut préalablement rétroporter les paquets donnés dans les champs <literal>Build-Depends</literal> avant de pouvoir compléter le rétroportage souhaité. Certains paquets, qui n'ont pas besoin d'être rétroportés, seront installés tels quels pour les besoins de la recompilation (c'est souvent le cas de <emphasis role=\"pkg\">debhelper</emphasis>). Cependant, le processus peut se compliquer rapidement si l'on n'y prend garde, aussi faut-il éviter autant que possible tout rétroportage non strictement nécessaire." |
| 315 |
|
| 316 |
#, fuzzy |
| 317 |
#| msgid "<primary><filename>Makefile</filename></primary>" |
| 318 |
msgid "<primary><filename>INSTALL</filename></primary>" |
| 319 |
msgstr "<primary><filename>Makefile</filename></primary>" |
| 320 |
|
| 321 |
msgid "<emphasis>TIP</emphasis> Installing <literal>Build-Depends</literal>" |
| 322 |
msgstr "<emphasis>ASTUCE</emphasis> Installer les <literal>Build-Depends</literal>" |
| 323 |
|
| 324 |
#, fuzzy |
| 325 |
#| msgid "<command>apt-get</command> allows installing all packages mentioned in the <literal>Build-Depends</literal> fields of a source package available in a distribution mentioned in a <literal>deb-src</literal> line of the <filename>/etc/apt/sources.list</filename> file. This is a simple matter of running the <command>apt-get build-dep <replaceable>source-package</replaceable></command> command." |
| 326 |
msgid "<command>apt-get</command> allows installing all packages mentioned in the <literal>Build-Depends</literal> fields of a source package available in a distribution mentioned in a <literal>deb-src</literal> line of the <filename>/etc/apt/sources.list</filename> file. This is a simple matter of running the <command>apt-get build-dep <replaceable>package</replaceable></command> command." |
| 327 |
msgstr "<command>apt-get</command> aide à installer rapidement tous les paquets cités dans le ou les champs <literal>Build-Depends</literal> d'un paquet source disponible dans une distribution donnée sur une ligne <literal>deb-src</literal> du fichier <filename>/etc/apt/sources.list</filename>. Il suffit pour cela d'exécuter la commande <command>apt-get build-dep <replaceable>paquet-source</replaceable></command>." |
| 328 |
|
| 329 |
#, fuzzy |
| 330 |
#| msgid "<primary>package</primary><secondary>types</secondary>" |
| 331 |
msgid "<primary>APT</primary><secondary><filename>/etc/apt/sources.list</filename></secondary>" |
| 332 |
msgstr "<primary>paquet</primary><secondary>types</secondary>" |
| 333 |
|
| 334 |
#, fuzzy |
| 335 |
#| msgid "<primary><command>dput</command></primary>" |
| 336 |
msgid "<primary><command>apt-get</command></primary>" |
| 337 |
msgstr "<primary><command>dput</command></primary>" |
| 338 |
|
| 339 |
msgid "Starting the Rebuild" |
| 340 |
msgstr "Démarrer la recompilation" |
| 341 |
|
| 342 |
msgid "When all the needed changes have been applied to the sources, we can start generating the actual binary package (<filename>.deb</filename> file). The whole process is managed by the <command>dpkg-buildpackage</command> command." |
| 343 |
msgstr "Toutes les modifications souhaitables étant apportées sur les sources, il faut maintenant régénérer le paquet binaire correspondant (fichier <filename>.deb</filename>). Tout ce processus de création est contrôlé par le programme <command>dpkg-buildpackage</command>." |
| 344 |
|
| 345 |
#, fuzzy |
| 346 |
#| msgid "<primary><filename>Makefile</filename></primary>" |
| 347 |
msgid "<primary><filename>.deb</filename></primary>" |
| 348 |
msgstr "<primary><filename>Makefile</filename></primary>" |
| 349 |
|
| 350 |
#, fuzzy |
| 351 |
#| msgid "<primary><command>pbuilder</command></primary>" |
| 352 |
msgid "<primary><command>dpkg-buildpackage</command></primary>" |
| 353 |
msgstr "<primary><command>pbuilder</command></primary>" |
| 354 |
|
| 355 |
msgid "Rebuilding a package" |
| 356 |
msgstr "Recompilation d'un paquet" |
| 357 |
|
| 358 |
msgid "" |
| 359 |
"<computeroutput>$ </computeroutput><userinput>dpkg-buildpackage -us -uc\n" |
| 360 |
"</userinput><computeroutput>[...]\n" |
| 361 |
"</computeroutput>" |
| 362 |
msgstr "" |
| 363 |
"<computeroutput>$ </computeroutput><userinput>dpkg-buildpackage -us -uc\n" |
| 364 |
"</userinput><computeroutput>[...]\n" |
| 365 |
"</computeroutput>" |
| 366 |
|
| 367 |
#, fuzzy |
| 368 |
#| msgid "The previous command can fail if the <literal>Build-Depends</literal> fields have not been updated, or if the related packages are not installed. In such a case, it is possible to overrule this check by passing the <literal>-d</literal> option to <command>dpkg-buildpackage</command>. However, explicitly ignoring these dependencies runs the risk of the build process failing at a later stage. Worse, the package may seem to build correctly but fail to run properly: some programs automatically disable some of their features when a required library is not available at build time." |
| 369 |
msgid "The previous command can fail if the <literal>Build-Depends</literal> field has not been updated, or if the related packages are not installed. In such a case, it is possible to overrule this check by passing the <literal>-d</literal> option to <command>dpkg-buildpackage</command>. However, explicitly ignoring these dependencies runs the risk of the build process failing at a later stage. Worse, the package may seem to build correctly but fail to run properly: some programs automatically disable some of their features when a required library is not available at build time. The switch can still be very useful if you only want to create a source package, which is supposed to be passed to clean build environments as described in <xref linkend=\"sidebar.schroot\" />." |
| 370 |
msgstr "La commande précédente échoue si les champs <literal>Build-Depends</literal> n'ont pas été corrigés ou si les dépendances correspondantes n'ont pas été installées. Dans ce cas, on outrepasse cette vérification en ajoutant le paramètre <literal>-d</literal> à l'invocation de <command>dpkg-buildpackage</command>. En ignorant volontairement ces dépendances, on s'expose cependant à ce que la compilation échoue plus tard. Pire, il se peut que le paquet compile correctement mais que son fonctionnement soit altéré car certains programmes désactivent automatiquement des fonctionnalités s'ils détectent l'absence d'une bibliothèque lors de la compilation." |
| 371 |
|
| 372 |
msgid "The other options used in the above example make sure that neither the source package's <filename>.dsc</filename> (<literal>-us</literal>) nor the produced <filename>.changes</filename> file (<literal>-uc</literal>) get signed with the package builder's cryptographic key after the asuccessful build." |
| 373 |
msgstr "" |
| 374 |
|
| 375 |
msgid "<emphasis>TOOL</emphasis> <command>fakeroot</command>" |
| 376 |
msgstr "<emphasis>OUTIL</emphasis> <command>fakeroot</command>" |
| 377 |
|
| 378 |
#, fuzzy |
| 379 |
#| msgid "<primary><command>dch</command></primary>" |
| 380 |
msgid "<primary><command>fakeroot</command></primary>" |
| 381 |
msgstr "<primary><command>dch</command></primary>" |
| 382 |
|
| 383 |
# TODO: INTEGRATE ALTERNATE STRING: <primary><foreignphrase>sponsoring</foreignphrase></primary> |
| 384 |
#, fuzzy |
| 385 |
#| msgid "<primary>sponsoring</primary>" |
| 386 |
msgid "<primary>root</primary>" |
| 387 |
msgstr "<primary>parrainage</primary>" |
| 388 |
|
| 389 |
#, fuzzy |
| 390 |
#| msgid "<primary>package</primary><secondary>types</secondary>" |
| 391 |
msgid "<primary>account</primary><secondary>root account</secondary>" |
| 392 |
msgstr "<primary>paquet</primary><secondary>types</secondary>" |
| 393 |
|
| 394 |
msgid "In essence, the package creation process is a simple matter of gathering in an archive a set of existing (or built) files; most of the files will end up being owned by <emphasis>root</emphasis> in the archive. However, building the whole package under this user would imply increased risks; fortunately, this can be avoided with the <command>fakeroot</command> command. This tool can be used to run a program and give it the impression that it runs as <emphasis>root</emphasis> and creates files with arbitrary ownership and permissions. When the program creates the archive that will become the Debian package, it is tricked into creating an archive containing files marked as belonging to arbitrary owners, including <emphasis>root</emphasis>. This setup is so convenient that <command>dpkg-buildpackage</command> uses <command>fakeroot</command> by default when building packages." |
| 395 |
msgstr "Le processus de création de paquet, qui finalement se contente de rassembler dans une archive des fichiers existant localement (ou compilés), a besoin de créer des fichiers dont le propriétaire sera le plus souvent <literal>root</literal>. Pour éviter de compiler les paquets sous l'identité de l'administrateur, ce qui induirait des risques inutiles, on peut utiliser l'utilitaire nommé <command>fakeroot</command>. Lorsqu'il est utilisé pour lancer un programme, <command>fakeroot</command> laisse croire à ce programme qu'il tourne sous l'identité de <literal>root</literal>, et que les fichiers qu'il crée appartiennent également à l'administrateur. Lorsque le programme va créer l'archive qui deviendra le paquet Debian, il pourra ainsi y placer des fichiers appartenant à divers propriétaires. C'est pourquoi <command>dpkg-buildpackage</command> utilise par défaut <command>fakeroot</command> pour la préparation des paquets." |
| 396 |
|
| 397 |
msgid "Note that the program is only tricked into “believing” that it operates as a privileged account, and the process actually runs as the user running <command>fakeroot <replaceable>program</replaceable></command> (and the files are actually created with that user's permissions). At no time does it actually get root privileges that it could abuse." |
| 398 |
msgstr "Notez qu'il ne s'agit que d'une impression donnée au programme lancé et qu'on ne peut donc pas utiliser cet outil pour obtenir des privilèges quelconques. Le programme tourne réellement sous l'identité de l'utilisateur qui lance <command>fakeroot <replaceable>programme</replaceable></command> et les fichiers qu'il crée réellement continuent de lui appartenir." |
| 399 |
|
| 400 |
#, fuzzy |
| 401 |
#| msgid "More often than not, Debian developers use a higher-level program such as <command>debuild</command>; this runs <command>dpkg-buildpackage</command> as usual, but it also adds an invocation of a program that runs many checks to validate the generated package against the Debian policy. This script also cleans up the environment so that local environment variables do not “pollute” the package build. The <command>debuild</command> command is one of the tools in the <emphasis>devscripts</emphasis> suite, which share some consistency and configuration to make the maintainers' task easier." |
| 402 |
msgid "More often than not, Debian developers use a higher-level program such as <command>debuild</command>; this runs <command>dpkg-buildpackage</command> as usual, but it also adds an invocation of a program that runs many checks to validate the generated package against the Debian policy. This script also cleans up the environment so that local environment variables do not “pollute” the package build. The <command>debuild</command> command is one of the tools in the <emphasis role=\"pkg\">devscripts</emphasis> suite, which share some consistency and configuration to make the maintainers' task easier." |
| 403 |
msgstr "Les développeurs Debian utilisent plus volontiers un programme comme <command>debuild</command>, qui fera suivre l'appel de <command>dpkg-buildpackage</command> par l'exécution d'un programme chargé de vérifier que le paquet généré est conforme à la charte Debian. Par ailleurs, ce script nettoie l'environnement pour que les variables d'environnement locales n'affectent pas la compilation du paquet. <command>debuild</command> fait partie de la série d'outils du paquet <emphasis>devscripts</emphasis>, qui partagent une certaine cohérence et une configuration commune simplifiant le travail des mainteneurs." |
| 404 |
|
| 405 |
msgid "<primary><command>debuild</command></primary>" |
| 406 |
msgstr "<primary><command>debuild</command></primary>" |
| 407 |
|
| 408 |
msgid "<emphasis>QUICK LOOK</emphasis> Building packages in <emphasis>chrooted</emphasis> and <emphasis>virtual</emphasis> environments" |
| 409 |
msgstr "" |
| 410 |
|
| 411 |
msgid "<primary><command>pbuilder</command></primary>" |
| 412 |
msgstr "<primary><command>pbuilder</command></primary>" |
| 413 |
|
| 414 |
#, fuzzy |
| 415 |
#| msgid "<primary><command>pbuilder</command></primary>" |
| 416 |
msgid "<primary><command>cowbuilder</command></primary>" |
| 417 |
msgstr "<primary><command>pbuilder</command></primary>" |
| 418 |
|
| 419 |
msgid "<primary><command>schroot</command></primary>" |
| 420 |
msgstr "<primary><command>schroot</command></primary>" |
| 421 |
|
| 422 |
#, fuzzy |
| 423 |
#| msgid "<primary><command>debuild</command></primary>" |
| 424 |
msgid "<primary><command>sbuild</command></primary>" |
| 425 |
msgstr "<primary><command>debuild</command></primary>" |
| 426 |
|
| 427 |
msgid "Building a package on an existing system, like a workstation or server, can pose several problems. Maybe the system has packages installed, that conflict with the build requirements. Or maybe it has packages (libraries, headers, etc.) installed, that the project to build is not supposed to use - e.g. from <emphasis role=\"distribution\">Testing</emphasis>, <emphasis role=\"distribution\">Unstable</emphasis>, or even from third parties. Also it might have packages installed, which are actually required for the build, but are not listed in <filename>debian/control</filename>. It is therefore a good practice to build a packages in “clean“ environments." |
| 428 |
msgstr "" |
| 429 |
|
| 430 |
#, fuzzy |
| 431 |
#| msgid "The <command>pbuilder</command> program (in the similarly named package) allows building a Debian package in a <emphasis>chrooted</emphasis> environment. It first creates a temporary directory containing the minimal system required for building the package (including the packages mentioned in the <emphasis>Build-Depends</emphasis> field). This directory is then used as the root directory (<filename>/</filename>), using the <command>chroot</command> command, during the build process." |
| 432 |
msgid "The <command>sbuild</command>, <command>pbuilder</command>, or <command>cowbuilder</command> programs (in the similarly named packages) allow building a Debian package in a <emphasis>chrooted</emphasis> environment. Each of them first creates a temporary directory containing the minimal system required for building the package (including the packages mentioned in the <emphasis>Build-Depends</emphasis> field). This directory is then used as the root directory (<filename>/</filename>), using the <command>chroot</command> command, during the build process." |
| 433 |
msgstr "Le programme <command>pbuilder</command> (du paquet éponyme) sert à recompiler un paquet Debian dans un environnement <foreignphrase>chrooté</foreignphrase> : il crée un répertoire temporaire contenant un système minimal nécessaire à la reconstruction du paquet (en se basant sur les informations contenues dans le champ <emphasis>Build-Depends</emphasis>). Grâce à la commande <command>chroot</command>, ce répertoire sert ensuite de racine (<filename>/</filename>) lors du processus de recompilation." |
| 434 |
|
| 435 |
#, fuzzy |
| 436 |
#| msgid "<primary><command>dch</command></primary>" |
| 437 |
msgid "<primary><command>chroot</command></primary>" |
| 438 |
msgstr "<primary><command>dch</command></primary>" |
| 439 |
|
| 440 |
#, fuzzy |
| 441 |
#| msgid "This tool allows the build process to happen in an environment that is not altered by users' manipulations. This also allows for quick detection of the missing build-dependencies (since the build will fail unless the appropriate dependencies are documented). Finally, it allows building a package for a Debian version that is not the one used by the system as a whole: the machine can be using <emphasis role=\"distribution\">Stable</emphasis> for its normal workload, and a <command>pbuilder</command> running on the same machine can be using <emphasis role=\"distribution\">Unstable</emphasis> for package builds." |
| 442 |
msgid "These tools allow the build process to happen in an environment that is not altered by users' manipulations. This also allows for quick detection of the missing build-dependencies (since the build will fail unless the appropriate dependencies are documented). Finally, it allows building a package for a Debian version that is not the one used by the system as a whole: the machine can be using <emphasis role=\"distribution\">Stable</emphasis> for its normal workload, and the chrooted environments can be running on the same machine using <emphasis role=\"distribution\">Unstable</emphasis> for package builds. Using these tools, it is also possible to build for a different distribution, like <emphasis role=\"distribution\">Ubuntu</emphasis>." |
| 443 |
msgstr "Cette technique permet de compiler le paquet dans un environnement non dégradé (notamment par les manipulations des utilisateurs), de détecter rapidement les manques éventuels dans les dépendances de compilation (qui échouera si un élément essentiel n'est pas documenté) et de compiler un paquet pour une version de Debian différente de celle employée par le système (la machine peut utiliser <emphasis role=\"distribution\">Stable</emphasis> pour le fonctionnement quotidien et <command>pbuilder</command> peut employer <emphasis role=\"distribution\">Unstable</emphasis> pour la recompilation)." |
| 444 |
|
| 445 |
msgid "<command>schroot</command>, <command>sbuild-shell</command>, or <command>pbuilder</command> allow running a command or a login shell in a <emphasis>chrooted</emphasis> environment." |
| 446 |
msgstr "" |
| 447 |
|
| 448 |
msgid "Sometimes it is not enough to build a package in a chrooted environment. This can be due to building for a different architecture where cross-compilation does not work, or due to the tools not being able to create a chrooted environment for the desired target system. Then one can create virtual machines to build the package there. These setups are usually more complex then the tools mentioned above, and rarely needed, so we will only mention this possibility without going into much detail. Check out <xref linkend=\"sect.virtualization\" /> for an introduction into this topic." |
| 449 |
msgstr "" |
| 450 |
|
| 451 |
# TODO: INTEGRATE ALTERNATE STRING: <primary>Mainteneur Debian</primary> |
| 452 |
#, fuzzy |
| 453 |
#| msgid "<primary>Debian Maintainer</primary>" |
| 454 |
msgid "<primary>virtualization</primary>" |
| 455 |
msgstr "<primary><foreignphrase>Debian Maintainer</foreignphrase></primary>" |
| 456 |
|
| 457 |
msgid "Building your First Package" |
| 458 |
msgstr "Construire son premier paquet" |
| 459 |
|
| 460 |
msgid "Meta-Packages or Fake Packages" |
| 461 |
msgstr "Métapaquet ou faux paquet" |
| 462 |
|
| 463 |
#, fuzzy |
| 464 |
#| msgid "<primary>package</primary><secondary>types</secondary>" |
| 465 |
msgid "<primary>package</primary><secondary>meta-package</secondary>" |
| 466 |
msgstr "<primary>paquet</primary><secondary>types</secondary>" |
| 467 |
|
| 468 |
#, fuzzy |
| 469 |
#| msgid "<primary>package types</primary>" |
| 470 |
msgid "<primary>meta-package</primary>" |
| 471 |
msgstr "<primary>types de paquets</primary>" |
| 472 |
|
| 473 |
#, fuzzy |
| 474 |
#| msgid "<primary>package</primary><secondary>types</secondary>" |
| 475 |
msgid "<primary>package</primary><secondary>fake package</secondary>" |
| 476 |
msgstr "<primary>paquet</primary><secondary>types</secondary>" |
| 477 |
|
| 478 |
#, fuzzy |
| 479 |
#| msgid "<primary>key pair</primary>" |
| 480 |
msgid "<primary>fake package</primary>" |
| 481 |
msgstr "<primary>biclé</primary>" |
| 482 |
|
| 483 |
msgid "Fake packages and meta-packages are similar, in that they are empty shells that only exist for the effects their meta-data have on the package handling stack." |
| 484 |
msgstr "Faux paquet et métapaquet se concrétisent tous deux par un paquet vide qui n'existe que pour les effets de ses informations d'en-têtes sur la chaîne logicielle de gestion des paquets." |
| 485 |
|
| 486 |
#, fuzzy |
| 487 |
#| msgid "The purpose of a fake package is to trick <command>dpkg</command> and <command>apt</command> into believing that some package is installed even though it's only an empty shell. This allows satisfying dependencies on a package when the corresponding software was installed outside the scope of the packaging system. Such a method works, but it should still be avoided whenever possible, since there is no guarantee that the manually installed software behaves exactly like the corresponding package would and other packages depending on it would not work properly." |
| 488 |
msgid "The purpose of a fake package is to trick <command>dpkg</command> and <command>apt</command> into believing that some package is installed even though it is only an empty shell. This allows satisfying dependencies on a package when the corresponding software was installed outside the scope of the packaging system. Such a method works, but it should still be avoided whenever possible, since there is no guarantee that the manually installed software behaves exactly like the corresponding package would and other packages depending on it would not work properly." |
| 489 |
msgstr "Le faux paquet existe pour tromper <command>dpkg</command> et <command>apt</command> en leur faisant croire que le paquet correspondant est installé alors qu'il ne s'agit que d'une coquille vide. Cela aide à satisfaire les dépendances lorsque le logiciel en question a été installé manuellement. Cette méthode fonctionne, mais il faut l'éviter autant que possible ; rien ne garantit en effet que le logiciel installé manuellement constitue un remplaçant parfait du paquet concerné et certains autres paquets, qui en dépendent, pourraient donc ne pas fonctionner." |
| 490 |
|
| 491 |
msgid "On the other hand, a meta-package exists mostly as a collection of dependencies, so that installing the meta-package will actually bring in a set of other packages in a single step." |
| 492 |
msgstr "Le métapaquet existe en tant que collection de paquets par le biais de ses dépendances, que son installation installera donc toutes." |
| 493 |
|
| 494 |
msgid "Both these kinds of packages can be created by the <command>equivs-control</command> and <command>equivs-build</command> commands (in the <emphasis role=\"pkg\">equivs</emphasis> package). The <command>equivs-control <replaceable>file</replaceable></command> command creates a Debian package header file that should be edited to contain the name of the expected package, its version number, the name of the maintainer, its dependencies, and its description. Other fields without a default value are optional and can be deleted. The <literal>Copyright</literal>, <literal>Changelog</literal>, <literal>Readme</literal> and <literal>Extra-Files</literal> fields are not standard fields in Debian packages; they only make sense within the scope of <command>equivs-build</command>, and they will not be kept in the headers of the generated package." |
| 495 |
msgstr "Pour créer ces deux types de paquets, on peut recourir aux programmes <command>equivs-control</command> et <command>equivs-build</command> (du paquet Debian <emphasis>equivs</emphasis>). La commande <command>equivs-control <replaceable>fichier</replaceable></command> crée un fichier contenant des en-têtes de paquet Debian qu'on modifiera pour indiquer le nom du paquet souhaité, son numéro de version, le nom du mainteneur, ses dépendances, sa description. Tous les autres champs dépourvus de valeur par défaut sont optionnels et peuvent être supprimés. Les champs <literal>Copyright</literal>, <literal>Changelog</literal>, <literal>Readme</literal> et <literal>Extra-Files</literal> ne sont pas standards pour un paquet Debian. Propres à <command>equivs-build</command>, ils disparaîtront des en-têtes réels du paquet généré." |
| 496 |
|
| 497 |
#, fuzzy |
| 498 |
#| msgid "<primary><emphasis role=\"pkg\">devscripts</emphasis></primary>" |
| 499 |
msgid "<primary><emphasis role=\"pkg\">equivs</emphasis></primary>" |
| 500 |
msgstr "<primary><emphasis role=\"pkg\">devscripts</emphasis></primary>" |
| 501 |
|
| 502 |
#, fuzzy |
| 503 |
#| msgid "<primary><emphasis role=\"pkg\">devscripts</emphasis></primary>" |
| 504 |
msgid "<primary><emphasis role=\"pkg\">equivs</emphasis></primary><secondary><command>equivs-control</command></secondary>" |
| 505 |
msgstr "<primary><emphasis role=\"pkg\">devscripts</emphasis></primary>" |
| 506 |
|
| 507 |
#, fuzzy |
| 508 |
#| msgid "<primary><emphasis role=\"pkg\">devscripts</emphasis></primary>" |
| 509 |
msgid "<primary><emphasis role=\"pkg\">equivs</emphasis></primary><secondary><command>equivs-build</command></secondary>" |
| 510 |
msgstr "<primary><emphasis role=\"pkg\">devscripts</emphasis></primary>" |
| 511 |
|
| 512 |
msgid "Header file of the <emphasis>libxml-libxml-perl</emphasis> fake package" |
| 513 |
msgstr "Fichier d'en-têtes d'un faux paquet <emphasis>libxml-libxml-perl</emphasis>" |
| 514 |
|
| 515 |
#, fuzzy |
| 516 |
#| msgid "" |
| 517 |
#| "\n" |
| 518 |
#| "Section: perl\n" |
| 519 |
#| "Priority: optional\n" |
| 520 |
#| "Standards-Version: 3.9.6\n" |
| 521 |
#| "\n" |
| 522 |
#| "Package: libxml-libxml-perl\n" |
| 523 |
#| "Version: 2.0116-1\n" |
| 524 |
#| "Maintainer: Raphael Hertzog <[email protected]>\n" |
| 525 |
#| "Depends: libxml2 (>= 2.7.4)\n" |
| 526 |
#| "Architecture: all\n" |
| 527 |
#| "Description: Fake package - module manually installed in site_perl\n" |
| 528 |
#| " This is a fake package to let the packaging system\n" |
| 529 |
#| " believe that this Debian package is installed. \n" |
| 530 |
#| " .\n" |
| 531 |
#| " In fact, the package is not installed since a newer version\n" |
| 532 |
#| " of the module has been manually compiled & installed in the\n" |
| 533 |
#| " site_perl directory." |
| 534 |
msgid "" |
| 535 |
"<![CDATA[\n" |
| 536 |
"Section: perl\n" |
| 537 |
"Priority: optional\n" |
| 538 |
"Standards-Version: 4.5.1\n" |
| 539 |
"\n" |
| 540 |
"Package: libxml-libxml-perl\n" |
| 541 |
"Version: 2.0207-1\n" |
| 542 |
"Maintainer: Raphael Hertzog <[email protected]>\n" |
| 543 |
"Depends: libxml2 (>= 2.9.10)\n" |
| 544 |
"Architecture: all\n" |
| 545 |
"Description: Fake package - module manually installed in site_perl\n" |
| 546 |
" This is a fake package to let the packaging system\n" |
| 547 |
" believe that this Debian package is installed.\n" |
| 548 |
" .\n" |
| 549 |
" In fact, the package is not installed since a newer version\n" |
| 550 |
" of the module has been manually compiled & installed in the\n" |
| 551 |
" site_perl directory.\n" |
| 552 |
"]]>" |
| 553 |
msgstr "" |
| 554 |
"\n" |
| 555 |
"Section: perl\n" |
| 556 |
"Priority: optional\n" |
| 557 |
"Standards-Version: 3.9.6\n" |
| 558 |
"\n" |
| 559 |
"Package: libxml-libxml-perl\n" |
| 560 |
"Version: 2.0116-1\n" |
| 561 |
"Maintainer: Raphael Hertzog <[email protected]>\n" |
| 562 |
"Depends: libxml2 (>= 2.7.4)\n" |
| 563 |
"Architecture: all\n" |
| 564 |
"Description: Fake package - module manually installed in site_perl\n" |
| 565 |
" This is a fake package to let the packaging system\n" |
| 566 |
" believe that this Debian package is installed. \n" |
| 567 |
" .\n" |
| 568 |
" In fact, the package is not installed since a newer version\n" |
| 569 |
" of the module has been manually compiled & installed in the\n" |
| 570 |
" site_perl directory." |
| 571 |
|
| 572 |
msgid "The next step is to generate the Debian package with the <command>equivs-build <replaceable>file</replaceable></command> command. Voilà: the package is created in the current directory and it can be handled like any other Debian package would." |
| 573 |
msgstr "L'étape suivante consiste à générer le paquet Debian en invoquant la commande <command>equivs-build <replaceable>fichier</replaceable></command>. Le tour est joué : le paquet est disponible dans le répertoire courant et vous pouvez désormais le manipuler comme tous les autres paquets Debian." |
| 574 |
|
| 575 |
msgid "" |
| 576 |
"<computeroutput>$ </computeroutput><userinput>equivs-build <replaceable>file</replaceable>\n" |
| 577 |
"</userinput><computeroutput><![CDATA[equivs-build control \n" |
| 578 |
"dpkg-buildpackage: info: source package libxml-libxml-perl\n" |
| 579 |
"dpkg-buildpackage: info: source version 2.0207-1\n" |
| 580 |
"dpkg-buildpackage: info: source distribution unstable\n" |
| 581 |
"dpkg-buildpackage: info: source changed by Raphael Hertzog <[email protected]>\n" |
| 582 |
"dpkg-buildpackage: info: host architecture amd64\n" |
| 583 |
" dpkg-source --before-build .\n" |
| 584 |
" debian/rules clean\n" |
| 585 |
"dh clean\n" |
| 586 |
" dh_clean\n" |
| 587 |
" debian/rules binary\n" |
| 588 |
"dh binary\n" |
| 589 |
" dh_update_autotools_config\n" |
| 590 |
" dh_autoreconf\n" |
| 591 |
" create-stamp debian/debhelper-build-stamp\n" |
| 592 |
" dh_prep\n" |
| 593 |
" dh_install\n" |
| 594 |
" dh_installdocs\n" |
| 595 |
" dh_installchangelogs\n" |
| 596 |
" dh_perl\n" |
| 597 |
" dh_link\n" |
| 598 |
" dh_strip_nondeterminism\n" |
| 599 |
" dh_compress\n" |
| 600 |
" dh_fixperms\n" |
| 601 |
" dh_missing\n" |
| 602 |
" dh_installdeb\n" |
| 603 |
" dh_gencontrol\n" |
| 604 |
" dh_md5sums\n" |
| 605 |
" dh_builddeb\n" |
| 606 |
"dpkg-deb: building package 'libxml-libxml-perl' in '../libxml-libxml-perl_2.0207-1_all.deb'.\n" |
| 607 |
" dpkg-genbuildinfo --build=binary\n" |
| 608 |
" dpkg-genchanges --build=binary >../libxml-libxml-perl_2.0207-1_amd64.changes\n" |
| 609 |
"dpkg-genchanges: info: binary-only upload (no source code included)\n" |
| 610 |
" dpkg-source --after-build .\n" |
| 611 |
"dpkg-buildpackage: info: binary-only upload (no source included)\n" |
| 612 |
"\n" |
| 613 |
"The package has been created.\n" |
| 614 |
"Attention, the package has been created in the current directory,\n" |
| 615 |
"not in \"..\" as indicated by the messaige above!\n" |
| 616 |
"]]></computeroutput>" |
| 617 |
msgstr "" |
| 618 |
|
| 619 |
msgid "Simple File Archive" |
| 620 |
msgstr "Simple archive de fichiers" |
| 621 |
|
| 622 |
#, fuzzy |
| 623 |
#| msgid "<primary><command>dch</command></primary>" |
| 624 |
msgid "<primary><command>dh_make</command></primary>" |
| 625 |
msgstr "<primary><command>dch</command></primary>" |
| 626 |
|
| 627 |
#, fuzzy |
| 628 |
#| msgid "<primary><emphasis>dh-make</emphasis></primary>" |
| 629 |
msgid "<primary><emphasis role=\"pkg\">dh-make</emphasis></primary>" |
| 630 |
msgstr "<primary><emphasis>dh-make</emphasis></primary>" |
| 631 |
|
| 632 |
msgid "The Falcot Corp administrators need to create a Debian package in order to ease deployment of a set of documents on a large number of machines. The administrator in charge of this task first reads the “New Maintainer's Guide”, then starts working on their first package. <ulink type=\"block\" url=\"https://www.debian.org/doc/manuals/maint-guide/\" />" |
| 633 |
msgstr "Les administrateurs de Falcot SA souhaitent créer un paquet Debian pour déployer facilement un ensemble de documents sur un grand nombre de machines. Après avoir étudié le guide du nouveau mainteneur, l'administrateur en charge de cette tâche se lance dans la création de son premier paquet. <ulink type=\"block\" url=\"https://www.debian.org/doc/manuals/maint-guide/index.fr.html\" />" |
| 634 |
|
| 635 |
msgid "The first step is creating a <filename>falcot-data-1.0</filename> directory to contain the target source package. The package will logically, be named <literal>falcot-data</literal> and bear the <literal>1.0</literal> version number. The administrator then places the document files in a <filename>data</filename> subdirectory. Then they invoke the <command>dh_make</command> command (from the <emphasis role=\"pkg\">dh-make</emphasis> package) to add files required by the package generation process, which will all be stored in a <filename>debian</filename> subdirectory:" |
| 636 |
msgstr "Il commence par créer un répertoire <filename>falcot-data-1.0</filename>, qui abritera le paquet source qu'il a choisi de réaliser. Ce paquet se nommera donc <literal>falcot-data</literal> et portera le numéro de version <literal>1.0</literal>. L'administrateur place ensuite les fichiers des documents qu'il souhaite distribuer dans un sous-répertoire <filename>data</filename>. Il invoque la commande <command>dh_make</command> (du paquet <emphasis role=\"pkg\">dh-make</emphasis>) pour ajouter les fichiers requis par le processus de génération d'un paquet (tous contenus dans un sous-répertoire <filename>debian</filename>) :" |
| 637 |
|
| 638 |
#, fuzzy |
| 639 |
#| msgid "" |
| 640 |
#| "\n" |
| 641 |
#| "<computeroutput>$ </computeroutput><userinput>cd falcot-data-1.0</userinput>\n" |
| 642 |
#| "<computeroutput>$ </computeroutput><userinput>dh_make --native</userinput>\n" |
| 643 |
#| "<computeroutput>\n" |
| 644 |
#| "Type of package: single binary, indep binary, multiple binary, library, kernel module, kernel patch?\n" |
| 645 |
#| " [s/i/m/l/k/n] </computeroutput><userinput>i</userinput>\n" |
| 646 |
#| "<computeroutput>\n" |
| 647 |
#| "Maintainer name : Raphael Hertzog\n" |
| 648 |
#| "Email-Address : [email protected]\n" |
| 649 |
#| "Date : Fri, 04 Sep 2015 12:09:39 -0400\n" |
| 650 |
#| "Package Name : falcot-data\n" |
| 651 |
#| "Version : 1.0\n" |
| 652 |
#| "License : gpl3\n" |
| 653 |
#| "Type of Package : Independent\n" |
| 654 |
#| "Hit <enter> to confirm:\n" |
| 655 |
#| "Currently there is no top level Makefile. This may require additional tuning.\n" |
| 656 |
#| "Done. Please edit the files in the debian/ subdirectory now. You should also\n" |
| 657 |
#| "check that the falcot-data Makefiles install into $DESTDIR and not in / .\n" |
| 658 |
#| "$</computeroutput>" |
| 659 |
msgid "" |
| 660 |
"\n" |
| 661 |
"<computeroutput>$ </computeroutput><userinput>cd falcot-data-1.0</userinput>\n" |
| 662 |
"<computeroutput>$ </computeroutput><userinput>dh_make --native</userinput>\n" |
| 663 |
"<computeroutput>\n" |
| 664 |
"Type of package: (single, indep, library, python)\n" |
| 665 |
"[s/i/l/p]? </computeroutput><userinput>i</userinput>\n" |
| 666 |
"<computeroutput>\n" |
| 667 |
"Maintainer Name : Raphael Hertzog\n" |
| 668 |
"Email-Address : [email protected]\n" |
| 669 |
"Date : Sat, 26 Feb 2021 13:02:06 +0100\n" |
| 670 |
"Package Name : falcot-data\n" |
| 671 |
"Version : 1.0\n" |
| 672 |
"License : gpl3\n" |
| 673 |
"Package Type : indep\n" |
| 674 |
"Are the details correct? [Y/n/q]\n" |
| 675 |
"Currently there is not top level Makefile. This may require additional tuning\n" |
| 676 |
"Done. Please edit the files in the debian/ subdirectory now.\n" |
| 677 |
"\n" |
| 678 |
"$</computeroutput>" |
| 679 |
msgstr "" |
| 680 |
"\n" |
| 681 |
"<computeroutput>$ </computeroutput><userinput>cd falcot-data-1.0</userinput>\n" |
| 682 |
"<computeroutput>$ </computeroutput><userinput>dh_make --native</userinput>\n" |
| 683 |
"<computeroutput>\n" |
| 684 |
"Type of package: single binary, indep binary, multiple binary, library, kernel module, kernel patch?\n" |
| 685 |
" [s/i/m/l/k/n] </computeroutput><userinput>i</userinput>\n" |
| 686 |
"<computeroutput>\n" |
| 687 |
"Maintainer name : Raphael Hertzog\n" |
| 688 |
"Email-Address : [email protected]\n" |
| 689 |
"Date : Fri, 04 Sep 2015 12:09:39 -0400\n" |
| 690 |
"Package Name : falcot-data\n" |
| 691 |
"Version : 1.0\n" |
| 692 |
"License : gpl3\n" |
| 693 |
"Type of Package : Independent\n" |
| 694 |
"Hit <enter> to confirm:\n" |
| 695 |
"Currently there is no top level Makefile. This may require additional tuning.\n" |
| 696 |
"Done. Please edit the files in the debian/ subdirectory now. You should also\n" |
| 697 |
"check that the falcot-data Makefiles install into $DESTDIR and not in / .\n" |
| 698 |
"$</computeroutput>" |
| 699 |
|
| 700 |
#, fuzzy |
| 701 |
#| msgid "The selected type of package (<emphasis>indep binary</emphasis>) indicates that this source package will generate a single binary package that can be shared across all architectures (<literal>Architecture: all</literal>). <emphasis>single binary</emphasis> acts as a counterpart, and leads to a single binary package that is dependent on the target architecture (<literal>Architecture: any</literal>). In this case, the former choice is more relevant since the package only contains documents and no binary programs, so it can be used similarly on computers of all architectures." |
| 702 |
msgid "The selected type of package (<emphasis>indep</emphasis>) indicates that this source package will generate a single binary package that can be shared across all architectures (<literal>Architecture: all</literal> in <filename>debian/control</filename>). <emphasis>single</emphasis> acts as a counterpart, and leads to a single binary package that is dependent on the target architecture (<literal>Architecture: any</literal>). In this case, the former choice is more relevant since the package only contains documents and no binary programs, so it can be used similarly on computers of all architectures." |
| 703 |
msgstr "Le type de paquet <foreignphrase>indep binary</foreignphrase> indique que ce paquet source ne générera qu'un seul paquet binaire indépendant de l'architecture (<literal>Architecture: all</literal>). <foreignphrase>single binary</foreignphrase> est le pendant de <foreignphrase>indep binary</foreignphrase> pour un seul paquet binaire dépendant de l'architecture (<literal>Architecture: any</literal>). Nous optons pour le premier choix puisque le paquet abrite des documents et non des programmes binaires : il est donc exploitable sur toutes les architectures." |
| 704 |
|
| 705 |
msgid "<primary>package</primary><secondary>types</secondary>" |
| 706 |
msgstr "<primary>paquet</primary><secondary>types</secondary>" |
| 707 |
|
| 708 |
#, fuzzy |
| 709 |
#| msgid "<primary>package</primary><secondary>types</secondary>" |
| 710 |
msgid "<primary>package</primary><secondary>architecture</secondary>" |
| 711 |
msgstr "<primary>paquet</primary><secondary>types</secondary>" |
| 712 |
|
| 713 |
msgid "<primary><filename>control</filename></primary><secondary><literal>Architecture</literal>, header field</secondary>" |
| 714 |
msgstr "" |
| 715 |
|
| 716 |
#, fuzzy |
| 717 |
#| msgid "The <emphasis>multiple binary</emphasis> type corresponds to a source package leading to several binary packages. A particular case, <emphasis>library</emphasis>, is useful for shared libraries, since they need to follow strict packaging rules. In a similar fashion, <emphasis>kernel module</emphasis> or <emphasis>kernel patch</emphasis> should be restricted to packages containing kernel modules." |
| 718 |
msgid "The <emphasis>library</emphasis> type corresponds to a source package leading to several binary packages. It is useful for shared libraries, since they need to follow strict packaging rules." |
| 719 |
msgstr "<foreignphrase>multiple binary</foreignphrase> est à employer pour un paquet source générant plusieurs paquets binaires. Le type <foreignphrase>library</foreignphrase> est un cas particulier pour les bibliothèques partagées qui doivent suivre des règles de mise en paquet très strictes. Il en est de même pour <foreignphrase>kernel module</foreignphrase> et <foreignphrase>kernel patch</foreignphrase>, réservés aux paquets contenant des modules noyau." |
| 720 |
|
| 721 |
msgid "<emphasis>TIP</emphasis> Maintainer's name and email address" |
| 722 |
msgstr "<emphasis>ASTUCE</emphasis> Nom et adresse électronique du mainteneur" |
| 723 |
|
| 724 |
msgid "<primary><varname>DEBFULLNAME</varname></primary><see>environment variable</see>" |
| 725 |
msgstr "" |
| 726 |
|
| 727 |
#, fuzzy |
| 728 |
#| msgid "<primary>package</primary><secondary>types</secondary>" |
| 729 |
msgid "<primary>environment variable</primary><secondary><varname>DEBFULLNAME</varname></secondary>" |
| 730 |
msgstr "<primary>paquet</primary><secondary>types</secondary>" |
| 731 |
|
| 732 |
msgid "<primary><varname>DEBEMAIL</varname></primary><see>environment variable</see>" |
| 733 |
msgstr "" |
| 734 |
|
| 735 |
#, fuzzy |
| 736 |
#| msgid "<primary>package</primary><secondary>types</secondary>" |
| 737 |
msgid "<primary>environment variable</primary><secondary><varname>DEBEMAIL</varname></secondary>" |
| 738 |
msgstr "<primary>paquet</primary><secondary>types</secondary>" |
| 739 |
|
| 740 |
msgid "<primary><varname>EMAIL</varname></primary><see>environment variable</see>" |
| 741 |
msgstr "" |
| 742 |
|
| 743 |
#, fuzzy |
| 744 |
#| msgid "<primary>package</primary><secondary>types</secondary>" |
| 745 |
msgid "<primary>environment variable</primary><secondary><varname>EMAIL</varname></secondary>" |
| 746 |
msgstr "<primary>paquet</primary><secondary>types</secondary>" |
| 747 |
|
| 748 |
#, fuzzy |
| 749 |
#| msgid "<primary><filename>Makefile</filename></primary>" |
| 750 |
msgid "<primary><filename>.bashrc</filename></primary>" |
| 751 |
msgstr "<primary><filename>Makefile</filename></primary>" |
| 752 |
|
| 753 |
msgid "Most of the programs involved in package maintenance will look for your name and email address in the <varname>DEBFULLNAME</varname> and <varname>DEBEMAIL</varname> or <varname>EMAIL</varname> environment variables. Defining them once and for all will avoid you having to type them multiple times. If your usual shell is <command>bash</command>, it is a simple matter of adding the following two lines in your <filename>~/.bashrc</filename> file (you will obviously replace the values with more relevant ones!):" |
| 754 |
msgstr "La plupart des programmes qui recherchent vos nom et adresse électronique de responsable de paquet utilisent les valeurs contenues dans les variables d'environnement <varname>DEBFULLNAME</varname> et <varname>DEBEMAIL</varname> ou <varname>EMAIL</varname>. En les définissant une fois pour toutes, vous vous éviterez de devoir les saisir à de multiples reprises. Si votre shell habituel est <command>bash</command>, il suffit pour cela d'ajouter les deux lignes suivantes dans votre fichier <filename>~/.bashrc</filename> (en remplaçant évidemment ces valeurs par celles qui vous correspondent !) :" |
| 755 |
|
| 756 |
msgid "" |
| 757 |
"\n" |
| 758 |
"export EMAIL=\"[email protected]\"\n" |
| 759 |
"export DEBFULLNAME=\"Raphael Hertzog\"" |
| 760 |
msgstr "" |
| 761 |
"\n" |
| 762 |
"export EMAIL=\"[email protected]\"\n" |
| 763 |
"export DEBFULLNAME=\"Raphael Hertzog\"" |
| 764 |
|
| 765 |
#, fuzzy |
| 766 |
#| msgid "<primary><filename>Makefile</filename></primary>" |
| 767 |
msgid "<primary><filename>debian</filename>, directory</primary>" |
| 768 |
msgstr "<primary><filename>Makefile</filename></primary>" |
| 769 |
|
| 770 |
msgid "<primary><filename>debian</filename>, directory</primary><secondary><filename>rules</filename></secondary><seealso><filename>rules</filename></seealso>" |
| 771 |
msgstr "" |
| 772 |
|
| 773 |
#, fuzzy |
| 774 |
#| msgid "<primary><filename>Makefile</filename></primary>" |
| 775 |
msgid "<primary><filename>rules</filename></primary>" |
| 776 |
msgstr "<primary><filename>Makefile</filename></primary>" |
| 777 |
|
| 778 |
msgid "<primary><filename>debian</filename>, directory</primary><secondary><filename>control</filename></secondary><seealso><filename>control</filename></seealso>" |
| 779 |
msgstr "" |
| 780 |
|
| 781 |
#, fuzzy |
| 782 |
#| msgid "<primary><filename>Makefile</filename></primary>" |
| 783 |
msgid "<primary><filename>control</filename></primary>" |
| 784 |
msgstr "<primary><filename>Makefile</filename></primary>" |
| 785 |
|
| 786 |
msgid "<primary><filename>debian</filename>, directory</primary><secondary><filename>changelog</filename></secondary><seealso><filename>changelog</filename></seealso>" |
| 787 |
msgstr "" |
| 788 |
|
| 789 |
#, fuzzy |
| 790 |
#| msgid "<primary><filename>Makefile</filename></primary>" |
| 791 |
msgid "<primary><filename>changelog</filename></primary>" |
| 792 |
msgstr "<primary><filename>Makefile</filename></primary>" |
| 793 |
|
| 794 |
msgid "<primary><filename>debian</filename>, directory</primary><secondary><filename>copyright</filename></secondary><seealso><filename>copyright</filename></seealso>" |
| 795 |
msgstr "" |
| 796 |
|
| 797 |
#, fuzzy |
| 798 |
#| msgid "<primary><filename>Makefile</filename></primary>" |
| 799 |
msgid "<primary><filename>copyright</filename></primary>" |
| 800 |
msgstr "<primary><filename>Makefile</filename></primary>" |
| 801 |
|
| 802 |
#, fuzzy |
| 803 |
#| msgid "The <command>dh_make</command> command created a <filename>debian</filename> subdirectory with many files. Some are required, in particular <filename>rules</filename>, <filename>control</filename>, <filename>changelog</filename> and <filename>copyright</filename>. Files with the <filename>.ex</filename> extension are example files that can be used by modifying them (and removing the extension) when appropriate. When they are not needed, removing them is recommended. The <filename>compat</filename> file should be kept, since it is required for the correct functioning of the <emphasis>debhelper</emphasis> suite of programs (all beginning with the <command>dh_</command> prefix) used at various stages of the package build process." |
| 804 |
msgid "The <command>dh_make</command> command created a <filename>debian</filename> subdirectory with many files. Some are required, in particular <filename>rules</filename>, <filename>control</filename>, <filename>changelog</filename> and <filename>copyright</filename>. Files with the <filename>.ex</filename> extension are example files that can be used by modifying them (and removing the extension) when appropriate. When they are not needed, removing them is recommended. The <filename>compat</filename> file is not used nor created anymore. Instead of defining the debhelper compatibility level as a number in this file, it is now defined as a build-dependency on the <emphasis role=\"pkg\">debhelper-compat</emphasis> virtual package in the <literal>Build-Depends</literal> file in <filename>debian/control</filename>." |
| 805 |
msgstr "Le programme <command>dh_make</command> a créé un sous-répertoire <filename>debian</filename> contenant de nombreux fichiers. Certains sont nécessaires : c'est notamment le cas des fichiers <filename>rules</filename>, <filename>control</filename>, <filename>changelog</filename> et <filename>copyright</filename>. Les fichiers d'extension <filename>.ex</filename> sont des fichiers d'exemples qu'on peut modifier et rebaptiser (en supprimant simplement cette extension) si cela s'avère utile. Dans le cas contraire, il convient de les supprimer. Le fichier <filename>compat</filename> doit être conservé car il est nécessaire au bon fonctionnement des programmes de l'ensemble appelé <emphasis>debhelper</emphasis>, dont les noms commencent par le préfixe <command>dh_</command> et qui sont employés à diverses étapes de la création de paquet." |
| 806 |
|
| 807 |
msgid "The <filename>copyright</filename> file must contain information about the authors of the documents included in the package, and the related copyright and license. In our case, these are internal documents and their use is restricted to within the Falcot Corp company. The default format used for this file is defined in the <literal>Format</literal> field. <ulink type=\"block\" url=\"https://www.debian.org/doc/packaging-manuals/copyright-format/1.0/\" />" |
| 808 |
msgstr "" |
| 809 |
|
| 810 |
msgid "The default <filename>changelog</filename> file is generally appropriate; replacing the “Initial release” with a more verbose explanation and changing the distribution from <literal>UNRELEASED</literal> or <literal>unstable</literal> to the target release name is enough." |
| 811 |
msgstr "" |
| 812 |
|
| 813 |
msgid "The <filename>control</filename> file must also be updated: the <literal>Section</literal> field can be changed to <emphasis>misc</emphasis> and the <literal>Homepage</literal>, <literal>Vcs-Git</literal> and <literal>Vcs-Browser</literal> fields were removed. The <literal>Depends</literal> fields was completed with <literal>firefox-esr | www-browser</literal> so as to ensure the availability of a web browser able to display the documents in the package. If the package does not require to run any commands as root (see <xref linkend=\"sidebar.fakeroot\" />), the <literal>Rules-Requires-Root</literal> field can be left as is." |
| 814 |
msgstr "" |
| 815 |
|
| 816 |
#, fuzzy |
| 817 |
#| msgid "<primary>package</primary><secondary>types</secondary>" |
| 818 |
msgid "<primary><filename>control</filename></primary><secondary><literal>Depends</literal>, header field</secondary>" |
| 819 |
msgstr "<primary>paquet</primary><secondary>types</secondary>" |
| 820 |
|
| 821 |
msgid "<primary><filename>control</filename></primary><secondary><literal>Homepage</literal>, header field</secondary>" |
| 822 |
msgstr "" |
| 823 |
|
| 824 |
msgid "<primary><filename>control</filename></primary><secondary><literal>Rules-Requires-Root</literal>, header field</secondary>" |
| 825 |
msgstr "" |
| 826 |
|
| 827 |
msgid "<primary><filename>control</filename></primary><secondary><literal>Section</literal>, header field</secondary>" |
| 828 |
msgstr "" |
| 829 |
|
| 830 |
msgid "<primary><filename>control</filename></primary><secondary><literal>Vcs-Browser</literal>, header field</secondary>" |
| 831 |
msgstr "" |
| 832 |
|
| 833 |
msgid "<primary><filename>control</filename></primary><secondary><literal>Vcs-Git</literal>, header field</secondary>" |
| 834 |
msgstr "" |
| 835 |
|
| 836 |
msgid "The <filename>control</filename> file" |
| 837 |
msgstr "Le fichier <filename>control</filename>" |
| 838 |
|
| 839 |
#, fuzzy |
| 840 |
#| msgid "" |
| 841 |
#| "\n" |
| 842 |
#| "Source: falcot-data\n" |
| 843 |
#| "Section: misc\n" |
| 844 |
#| "Priority: optional\n" |
| 845 |
#| "Maintainer: Raphael Hertzog <[email protected]>\n" |
| 846 |
#| "Build-Depends: debhelper (>= 9)\n" |
| 847 |
#| "Standards-Version: 3.9.5\n" |
| 848 |
#| "\n" |
| 849 |
#| "Package: falcot-data\n" |
| 850 |
#| "Architecture: all\n" |
| 851 |
#| "Depends: iceweasel | www-browser, ${misc:Depends}\n" |
| 852 |
#| "Description: Internal Falcot Corp Documentation\n" |
| 853 |
#| " This package provides several documents describing the internal\n" |
| 854 |
#| " structure at Falcot Corp. This includes:\n" |
| 855 |
#| " - organization diagram\n" |
| 856 |
#| " - contacts for each department.\n" |
| 857 |
#| " .\n" |
| 858 |
#| " These documents MUST NOT leave the company.\n" |
| 859 |
#| " Their use is INTERNAL ONLY." |
| 860 |
msgid "" |
| 861 |
"<![CDATA[\n" |
| 862 |
"Source: falcot-data\n" |
| 863 |
"Section: misc\n" |
| 864 |
"Priority: optional\n" |
| 865 |
"Maintainer: Raphael Hertzog <[email protected]>\n" |
| 866 |
"Build-Depends: debhelper-compat (= 13)\n" |
| 867 |
"Standards-Version: 4.5.1\n" |
| 868 |
"Rules-Requires-Root: no\n" |
| 869 |
"\n" |
| 870 |
"Package: falcot-data\n" |
| 871 |
"Architecture: all\n" |
| 872 |
"Depends: firefox-esr | www-browser, ${misc:Depends}\n" |
| 873 |
"Description: Internal Falcot Corp Documentation\n" |
| 874 |
" This package provides several documents describing the internal\n" |
| 875 |
" structure at Falcot Corp. This includes:\n" |
| 876 |
" - organization diagram\n" |
| 877 |
" - contacts for each department.\n" |
| 878 |
" .\n" |
| 879 |
" These documents MUST NOT leave the company.\n" |
| 880 |
" Their use is INTERNAL ONLY.\n" |
| 881 |
"]]>" |
| 882 |
msgstr "" |
| 883 |
"\n" |
| 884 |
"Source: falcot-data\n" |
| 885 |
"Section: misc\n" |
| 886 |
"Priority: optional\n" |
| 887 |
"Maintainer: Raphael Hertzog <[email protected]>\n" |
| 888 |
"Build-Depends: debhelper (>= 9)\n" |
| 889 |
"Standards-Version: 3.9.5\n" |
| 890 |
"\n" |
| 891 |
"Package: falcot-data\n" |
| 892 |
"Architecture: all\n" |
| 893 |
"Depends: iceweasel | www-browser, ${misc:Depends}\n" |
| 894 |
"Description: Documentation interne de Falcot SA\n" |
| 895 |
" Ce paquet fournit plusieurs documents décrivant\n" |
| 896 |
" la structure interne de Falcot SA. Cela comprend:\n" |
| 897 |
" - l'organigramme\n" |
| 898 |
" - les contacts pour chaque département\n" |
| 899 |
" .\n" |
| 900 |
" Ces documents NE DOIVENT PAS sortir de la société.\n" |
| 901 |
" Ils sont réservés à un USAGE INTERNE." |
| 902 |
|
| 903 |
msgid "The <filename>changelog</filename> file" |
| 904 |
msgstr "Le fichier <filename>changelog</filename>" |
| 905 |
|
| 906 |
#, fuzzy |
| 907 |
#| msgid "" |
| 908 |
#| "\n" |
| 909 |
#| "falcot-data (1.0) internal; urgency=low\n" |
| 910 |
#| "\n" |
| 911 |
#| " * Initial Release.\n" |
| 912 |
#| " * Let's start with few documents:\n" |
| 913 |
#| " - internal company structure;\n" |
| 914 |
#| " - contacts for each department.\n" |
| 915 |
#| "\n" |
| 916 |
#| " -- Raphael Hertzog <[email protected]> Fri, 04 Sep 2015 12:09:39 -0400" |
| 917 |
msgid "" |
| 918 |
"<![CDATA[\n" |
| 919 |
"falcot-data (1.0) bullseye; urgency=low\n" |
| 920 |
"\n" |
| 921 |
" * Initial Release.\n" |
| 922 |
" * Let's start with few documents:\n" |
| 923 |
" - internal company structure;\n" |
| 924 |
" - contacts for each department.\n" |
| 925 |
"\n" |
| 926 |
" -- Raphael Hertzog <[email protected]> Sat, 26 Feb 2022 15:12:06 +0100\n" |
| 927 |
"]]>" |
| 928 |
msgstr "" |
| 929 |
"\n" |
| 930 |
"falcot-data (1.0) internal; urgency=low\n" |
| 931 |
"\n" |
| 932 |
" * Initial Release.\n" |
| 933 |
" * Commençons avec peu de documents:\n" |
| 934 |
" - la structure interne de la société\n" |
| 935 |
" - les contacts de chaque département\n" |
| 936 |
"\n" |
| 937 |
" -- Raphael Hertzog <[email protected]> Fri, 04 Sep 2015 12:09:39 -0400" |
| 938 |
|
| 939 |
msgid "The <filename>copyright</filename> file" |
| 940 |
msgstr "Le fichier <filename>copyright</filename>" |
| 941 |
|
| 942 |
#, fuzzy |
| 943 |
#| msgid "" |
| 944 |
#| "\n" |
| 945 |
#| "Format: http://www.debian.org/doc/packaging-manuals/copyright-format/1.0/\n" |
| 946 |
#| "Upstream-Name: falcot-data\n" |
| 947 |
#| "\n" |
| 948 |
#| "Files: *\n" |
| 949 |
#| "Copyright: 2004-2015 Falcot Corp\n" |
| 950 |
#| "License: \n" |
| 951 |
#| " All rights reserved." |
| 952 |
msgid "" |
| 953 |
"\n" |
| 954 |
"Format: https://www.debian.org/doc/packaging-manuals/copyright-format/1.0/\n" |
| 955 |
"Upstream-Name: falcot-data\n" |
| 956 |
"\n" |
| 957 |
"Files: *\n" |
| 958 |
"Copyright: 2004-2021 Falcot Corp\n" |
| 959 |
"License:\n" |
| 960 |
" All rights reserved." |
| 961 |
msgstr "" |
| 962 |
"\n" |
| 963 |
"Format: http://www.debian.org/doc/packaging-manuals/copyright-format/1.0/\n" |
| 964 |
"Upstream-Name: falcot-data\n" |
| 965 |
"\n" |
| 966 |
"Files: *\n" |
| 967 |
"Copyright: 2004-2015 Falcot Corp\n" |
| 968 |
"License: \n" |
| 969 |
" All rights reserved." |
| 970 |
|
| 971 |
msgid "<emphasis>BACK TO BASICS</emphasis> <filename>Makefile</filename> file" |
| 972 |
msgstr "<emphasis>B.A.-BA</emphasis> Fichier <filename>Makefile</filename>" |
| 973 |
|
| 974 |
msgid "<primary><filename>Makefile</filename></primary>" |
| 975 |
msgstr "<primary><filename>Makefile</filename></primary>" |
| 976 |
|
| 977 |
#, fuzzy |
| 978 |
#| msgid "<primary><command>debi</command></primary>" |
| 979 |
msgid "<primary><command>make</command></primary>" |
| 980 |
msgstr "<primary><command>debi</command></primary>" |
| 981 |
|
| 982 |
msgid "A <filename>Makefile</filename> file is a script used by the <command>make</command> program; it describes rules for how to build a set of files from each other in a tree of dependencies (for instance, a program can be built from a set of source files). The <filename>Makefile</filename> file describes these rules in the following format:" |
| 983 |
msgstr "Un fichier <filename>Makefile</filename> est un script détaillant au programme <command>make</command> les règles nécessaires pour reconstruire des fichiers issus d'un réseau de dépendances (un programme, fruit de la compilation de fichiers sources, en est un exemple). Le fichier <filename>Makefile</filename> contient la liste de ces règles en respectant le format suivant :" |
| 984 |
|
| 985 |
msgid "" |
| 986 |
"\n" |
| 987 |
"target: source1 source2 ...\n" |
| 988 |
" command1\n" |
| 989 |
" command2" |
| 990 |
msgstr "" |
| 991 |
"\n" |
| 992 |
"cible: source1 source2 ...\n" |
| 993 |
" commande1\n" |
| 994 |
" commande2" |
| 995 |
|
| 996 |
#, fuzzy |
| 997 |
#| msgid "The interpretation of such a rule is as follows: if one of the <literal>source*</literal> files is more recent than the <literal>target</literal> file, then the target needs to be generated, using <command>command1</command> and <command>command2</command>." |
| 998 |
msgid "The basic interpretation of such a rule is as follows: if one of the <literal>source*</literal> files is more recent than the <literal>target</literal> file, then the target needs to be generated, using <command>command1</command> and <command>command2</command>." |
| 999 |
msgstr "Cette règle peut se traduire ainsi : si l'un des fichiers <literal>source*</literal> est plus récent que le fichier <literal>cible</literal>, il faut exécuter <command>command1</command> et <command>command2</command> pour régénérer la cible à partir des sources." |
| 1000 |
|
| 1001 |
msgid "Note that the command lines must start with a tab character; also note that when a command line starts with a dash character (<literal>-</literal>), failure of the command does not interrupt the whole process." |
| 1002 |
msgstr "Attention, un caractère de tabulation doit impérativement précéder toutes les commandes. Sachez aussi que si la ligne de commande débute par un signe moins (<literal>-</literal>), la commande peut échouer sans que tout le processus avorte." |
| 1003 |
|
| 1004 |
msgid "The <filename>rules</filename> file usually contains a set of rules used to configure, build and install the software in a dedicated subdirectory (named after the generated binary package). The contents of this subdirectory is then archived within the Debian package as if it were the root of the filesystem. In our case, files will be installed in the <filename>debian/falcot-data/usr/share/falcot-data/</filename> subdirectory, so that installing the generated package will deploy the files under <filename>/usr/share/falcot-data/</filename>. The <filename>rules</filename> file is used as a <filename>Makefile</filename>, with a few standard targets (including <literal>clean</literal> and <literal>binary</literal>, used respectively to clean the source directory and generate the binary package)." |
| 1005 |
msgstr "Le fichier <filename>rules</filename> contient normalement un ensemble de règles employées pour configurer, compiler et installer le logiciel dans un sous-répertoire dédié (portant le nom du paquet binaire généré). Le contenu de ce sous-répertoire est ensuite intégré au paquet Debian comme s'il était la racine du système de fichiers. Dans le cas qui nous concerne, les fichiers seront installés dans le répertoire <filename>debian/falcot-data/usr/share/falcot-data/</filename> pour que les documents ainsi diffusés soient disponibles sous <filename>/usr/share/falcot-data/</filename> dans le paquet généré. Le fichier <filename>rules</filename> est de type <filename>Makefile</filename> avec quelques cibles standardisées (notamment <literal>clean</literal> et <literal>binary</literal>, respectivement pour nettoyer et produire le binaire)." |
| 1006 |
|
| 1007 |
msgid "Although this file is the heart of the process, it increasingly contains only the bare minimum for running a standard set of commands provided by the <command>debhelper</command> tool. Such is the case for files generated by <command>dh_make</command>. To install our files, we simply configure the behavior of the <command>dh_install</command> command by creating the following <filename>debian/falcot-data.install</filename> file:" |
| 1008 |
msgstr "Bien que ce fichier soit au cœur du processus, il est fréquent qu'il ne contienne que le strict minimum pour lancer un ensemble standardisé de commandes qui sont fournies par le paquet <command>debhelper</command>. C'est le cas dans le fichier préparé par <command>dh_make</command>. Pour installer nos fichiers, nous allons simplement modifier le comportement de la commande <command>dh_install</command> en créant le fichier <filename>debian/falcot-data.install</filename> :" |
| 1009 |
|
| 1010 |
#, fuzzy |
| 1011 |
#| msgid "<primary>package</primary><secondary>types</secondary>" |
| 1012 |
msgid "<primary><command>dh</command></primary><secondary><command>dh_install</command></secondary>" |
| 1013 |
msgstr "<primary>paquet</primary><secondary>types</secondary>" |
| 1014 |
|
| 1015 |
msgid "" |
| 1016 |
"\n" |
| 1017 |
"data/* usr/share/falcot-data/" |
| 1018 |
msgstr "" |
| 1019 |
"\n" |
| 1020 |
"data/* usr/share/falcot-data/" |
| 1021 |
|
| 1022 |
#, fuzzy |
| 1023 |
#| msgid "At this point, the package can be created. We will however add a lick of paint. Since the administrators want the documents to be easily accessed from the menus of graphical desktop environments, we add a <filename>falcot-data.desktop</filename> file and get it installed in <filename>/usr/share/applications</filename> by adding a second line to <filename>debian/falcot-data.install</filename>." |
| 1024 |
msgid "At this point, the package can be created. We will, however, add a lick of paint. Since the administrators want the documents to be easily accessed from the menus of graphical desktop environments, we add a <filename>falcot-data.desktop</filename> file and get it installed in <filename>/usr/share/applications</filename> by adding a second line to <filename>debian/falcot-data.install</filename>." |
| 1025 |
msgstr "À ce stade, il est déjà possible de créer le paquet. Nous allons toutefois y ajouter une dernière touche. Les administrateurs souhaitent que ces documents soient facilement accessibles depuis les menus des bureaux graphiques. Pour cela, ils ajoutent un fichier <filename>falcot-data.desktop</filename> et l'installent dans <filename>/usr/share/applications</filename> en ajoutant une deuxième ligne au fichier <filename>debian/falcot-data.install</filename>." |
| 1026 |
|
| 1027 |
#, fuzzy |
| 1028 |
#| msgid "<primary><filename>Makefile</filename></primary>" |
| 1029 |
msgid "<primary><filename>.desktop</filename></primary>" |
| 1030 |
msgstr "<primary><filename>Makefile</filename></primary>" |
| 1031 |
|
| 1032 |
#, fuzzy |
| 1033 |
#| msgid "<primary><filename>Makefile</filename></primary>" |
| 1034 |
msgid "<primary><filename>.install</filename></primary>" |
| 1035 |
msgstr "<primary><filename>Makefile</filename></primary>" |
| 1036 |
|
| 1037 |
msgid "The <filename>falcot-data.desktop</filename> file" |
| 1038 |
msgstr "Le fichier <filename>falcot-data.desktop</filename>" |
| 1039 |
|
| 1040 |
msgid "" |
| 1041 |
"\n" |
| 1042 |
"[Desktop Entry]\n" |
| 1043 |
"Name=Internal Falcot Corp Documentation\n" |
| 1044 |
"Comment=Starts a browser to read the documentation\n" |
| 1045 |
"Exec=x-www-browser /usr/share/falcot-data/index.html\n" |
| 1046 |
"Terminal=false\n" |
| 1047 |
"Type=Application\n" |
| 1048 |
"Categories=Documentation;" |
| 1049 |
msgstr "" |
| 1050 |
"\n" |
| 1051 |
"[Desktop Entry]\n" |
| 1052 |
"Name=Internal Falcot Corp Documentation\n" |
| 1053 |
"Comment=Starts a browser to read the documentation\n" |
| 1054 |
"Name[fr]=Documentation interne Falcot SA\n" |
| 1055 |
"Comment[fr]=Lance un navigateur pour lire la documentation\n" |
| 1056 |
"Exec=x-www-browser /usr/share/falcot-data/index.html\n" |
| 1057 |
"Terminal=false\n" |
| 1058 |
"Type=Application\n" |
| 1059 |
"Categories=Documentation;" |
| 1060 |
|
| 1061 |
msgid "The updated <filename>debian/falcot-data.install</filename> looks like this:" |
| 1062 |
msgstr "Le fichier <filename>debian/falcot-data.install</filename> mis à jour ressemble donc à ceci :" |
| 1063 |
|
| 1064 |
msgid "" |
| 1065 |
"\n" |
| 1066 |
"data/* usr/share/falcot-data/\n" |
| 1067 |
"falcot-data.desktop usr/share/applications/" |
| 1068 |
msgstr "" |
| 1069 |
"\n" |
| 1070 |
"data/* usr/share/falcot-data/\n" |
| 1071 |
"falcot-data.desktop usr/share/applications/" |
| 1072 |
|
| 1073 |
#, fuzzy |
| 1074 |
#| msgid "Our source package is now ready. All that's left to do is to generate the binary package, with the same method we used previously for rebuilding packages: we run the <command>dpkg-buildpackage -us -uc</command> command from within the <filename>falcot-data-1.0</filename> directory." |
| 1075 |
msgid "Our source package is now ready. All that is left to do is to generate the binary package, with the same method we used previously for rebuilding packages: we run the <command>dpkg-buildpackage -us -uc</command> command from within the <filename>falcot-data-1.0</filename> directory." |
| 1076 |
msgstr "Le paquet source est prêt ! Il ne reste plus qu'à générer le paquet binaire avec la commande déjà employée pour des recompilations de paquets : on se place dans le répertoire <filename>falcot-data-1.0</filename> et on exécute <command>dpkg-buildpackage -us -uc</command>." |
| 1077 |
|
| 1078 |
msgid "Creating a Package Repository for APT" |
| 1079 |
msgstr "Créer une archive de paquets pour APT" |
| 1080 |
|
| 1081 |
#, fuzzy |
| 1082 |
#| msgid "<primary>package</primary><secondary>types</secondary>" |
| 1083 |
msgid "<primary>package</primary><secondary>archive</secondary>" |
| 1084 |
msgstr "<primary>paquet</primary><secondary>types</secondary>" |
| 1085 |
|
| 1086 |
msgid "<primary>package</primary><secondary>Debian</secondary><tertiary>archive of</tertiary>" |
| 1087 |
msgstr "<primary>paquet</primary><secondary>Debian</secondary><tertiary>archive de</tertiary>" |
| 1088 |
|
| 1089 |
msgid "Falcot Corp gradually started maintaining a number of Debian packages either locally modified from existing packages or created from scratch to distribute internal data and programs." |
| 1090 |
msgstr "Les administrateurs de Falcot SA maintiennent désormais un certain nombre de paquets Debian modifiés ou créés par eux et qui leur servent à diffuser des données et programmes internes." |
| 1091 |
|
| 1092 |
msgid "To make deployment easier, they want to integrate these packages in a package archive that can be directly used by APT. For obvious maintenance reasons, they wish to separate internal packages from locally-rebuilt packages. The goal is for the matching entries in a <filename>/etc/apt/sources.list.d/falcot.list</filename> file to be as follows:" |
| 1093 |
msgstr "Pour faciliter leur déploiement, ils souhaitent les intégrer dans une archive de paquets directement utilisable par APT. Pour des raisons évidentes de maintenance, ils désirent y séparer les paquets internes des paquets officiels recompilés. Les entrées qui correspondraient à cette situation dans un fichier <filename>/etc/apt/sources.list.d/falcot.list</filename> seraient les suivantes :" |
| 1094 |
|
| 1095 |
#, fuzzy |
| 1096 |
#| msgid "<primary>package</primary><secondary>types</secondary>" |
| 1097 |
msgid "<primary>APT</primary><secondary><filename>/etc/apt/sources.list.d/</filename></secondary>" |
| 1098 |
msgstr "<primary>paquet</primary><secondary>types</secondary>" |
| 1099 |
|
| 1100 |
msgid "" |
| 1101 |
"\n" |
| 1102 |
"deb http://packages.falcot.com/ updates/\n" |
| 1103 |
"deb http://packages.falcot.com/ internal/" |
| 1104 |
msgstr "" |
| 1105 |
"\n" |
| 1106 |
"deb http://packages.falcot.com/ updates/\n" |
| 1107 |
"deb http://packages.falcot.com/ internal/" |
| 1108 |
|
| 1109 |
msgid "<primary><command>mini-dinstall</command></primary>" |
| 1110 |
msgstr "<primary><command>mini-dinstall</command></primary>" |
| 1111 |
|
| 1112 |
msgid "The administrators therefore configure a virtual host on their internal HTTP server, with <filename>/srv/vhosts/packages/</filename> as the root of the associated web space. The management of the archive itself is delegated to the <command>mini-dinstall</command> command (in the similarly-named package). This tool keeps an eye on an <filename>incoming/</filename> directory (in our case, <filename>/srv/vhosts/packages/mini-dinstall/incoming/</filename>) and waits for new packages there; when a package is uploaded, it is installed into a Debian archive at <filename>/srv/vhosts/packages/</filename>. The <command>mini-dinstall</command> command reads the <filename>*.changes</filename> file created when the Debian package is generated. These files contain a list of all other files associated with the version of the package (<filename>*.deb</filename>, <filename>*.dsc</filename>, <filename>*.diff.gz</filename>/<filename>*.debian.tar.gz</filename>, <filename>*.orig.tar.gz</filename>, or their equivalents with other compression tools), and these allow <command>mini-dinstall</command> to know which files to install. <filename>*.changes</filename> files also contain the name of the target distribution (often <literal>unstable</literal>) mentioned in the latest <filename>debian/changelog</filename> entry, and <command>mini-dinstall</command> uses this information to decide where the package should be installed. This is why administrators must always change this field before building a package, and set it to <literal>internal</literal> or <literal>updates</literal>, depending on the target location. <command>mini-dinstall</command> then generates the files required by APT, such as <filename>Packages.gz</filename>." |
| 1113 |
msgstr "Les administrateurs configurent donc un hôte virtuel sur leur serveur HTTP interne. La racine de l'espace web associé est <filename>/srv/vhosts/packages/</filename>. Pour gérer ces archives, ils ont décidé d'employer le programme <command>mini-dinstall</command> (du paquet éponyme). Celui-ci scrute un répertoire d'arrivée <filename>incoming/</filename> (en l'occurrence, il s'agira de <filename>/srv/vhosts/packages/mini-dinstall/incoming/</filename>) pour y récupérer tout paquet Debian déposé et l'installer dans une archive Debian (dont le répertoire est <filename>/srv/vhosts/packages/</filename>). Ce programme fonctionne en traitant les fichiers <filename>.changes</filename> créés lors de la génération d'un paquet Debian. Un tel fichier contient en effet la liste de tous les autres fichiers associés à cette version du paquet (<filename>.deb</filename>, <filename>.dsc</filename>, <filename>.diff.gz</filename>/<filename>debian.tar.gz</filename>, <filename>.orig.tar.gz</filename> ou fichiers équivalents utilisant d'autres outils de compression) et indique donc à <command>mini-dinstall</command> quels fichiers installer. Accessoirement, ce fichier reprend le nom de la distribution de destination (c'est souvent <literal>unstable</literal>) indiquée en tête du fichier <filename>debian/changelog</filename>, information utilisée par <command>mini-dinstall</command> pour décider de l'emplacement d'installation du paquet. C'est la raison pour laquelle les administrateurs doivent systématiquement modifier ce champ avant la génération d'un paquet et y placer <literal>internal</literal> ou <literal>updates</literal>, selon l'emplacement souhaité. <command>mini-dinstall</command> génère alors les fichiers indispensables au bon fonctionnement d'APT, par exemple <filename>Packages.gz</filename>." |
| 1114 |
|
| 1115 |
#, fuzzy |
| 1116 |
#| msgid "<emphasis>ALTERNATIVE</emphasis> <command>apt-ftparchive</command>" |
| 1117 |
msgid "<emphasis>ALTERNATIVE</emphasis> <command>apt-ftparchive</command>, <command>aptly</command>, and <command>reprepro</command>" |
| 1118 |
msgstr "<emphasis>ALTERNATIVE</emphasis> <command>apt-ftparchive</command>" |
| 1119 |
|
| 1120 |
msgid "<primary><command>apt-ftparchive</command></primary>" |
| 1121 |
msgstr "<primary><command>apt-ftparchive</command></primary>" |
| 1122 |
|
| 1123 |
msgid "If <command>mini-dinstall</command> seems too complex for your Debian archive needs, you can also use the <command>apt-ftparchive</command> command. This tool scans the contents of a directory and displays (on its standard output) a matching <filename>Packages</filename> file. In the Falcot Corp case, administrators could upload the packages directly into <filename>/srv/vhosts/packages/updates/</filename> or <filename>/srv/vhosts/packages/internal/</filename>, then run the following commands to create the <filename>Packages.gz</filename> files:" |
| 1124 |
msgstr "Si l'emploi de <command>mini-dinstall</command> semble trop complexe par rapport à vos besoins de création d'une archive Debian, il est possible d'utiliser directement le programme <command>apt-ftparchive</command>. Ce dernier inspecte le contenu d'un répertoire et affiche sur sa sortie standard le contenu du fichier <filename>Packages</filename> correspondant. Pour reprendre le cas de Falcot SA, les administrateurs pourraient directement déposer les paquets dans <filename>/srv/vhosts/packages/updates/</filename> ou <filename>/srv/vhosts/packages/internal/</filename> et exécuter les commandes suivantes pour créer les fichiers <filename>Packages.gz</filename> :" |
| 1125 |
|
| 1126 |
msgid "" |
| 1127 |
"\n" |
| 1128 |
"<computeroutput>$ </computeroutput><userinput>cd /srv/vhosts/packages</userinput>\n" |
| 1129 |
"<computeroutput>$ </computeroutput><userinput>apt-ftparchive packages updates >updates/Packages</userinput>\n" |
| 1130 |
"<computeroutput>$ </computeroutput><userinput>gzip updates/Packages</userinput>\n" |
| 1131 |
"<computeroutput>$ </computeroutput><userinput>apt-ftparchive packages internal >internal/Packages</userinput>\n" |
| 1132 |
"<computeroutput>$ </computeroutput><userinput>gzip internal/Packages</userinput>" |
| 1133 |
msgstr "" |
| 1134 |
"\n" |
| 1135 |
"<computeroutput>$ </computeroutput><userinput>cd /srv/vhosts/packages</userinput>\n" |
| 1136 |
"<computeroutput>$ </computeroutput><userinput>apt-ftparchive packages updates >updates/Packages</userinput>\n" |
| 1137 |
"<computeroutput>$ </computeroutput><userinput>gzip updates/Packages</userinput>\n" |
| 1138 |
"<computeroutput>$ </computeroutput><userinput>apt-ftparchive packages internal >internal/Packages</userinput>\n" |
| 1139 |
"<computeroutput>$ </computeroutput><userinput>gzip internal/Packages</userinput>" |
| 1140 |
|
| 1141 |
msgid "The <command>apt-ftparchive sources</command> command allows creating <filename>Sources.gz</filename> files in a similar fashion." |
| 1142 |
msgstr "La commande <command>apt-ftparchive sources</command> crée de manière similaire les fichiers <filename>Sources.gz</filename>." |
| 1143 |
|
| 1144 |
msgid "<command>reprepro</command> and <command>aptly</command> are more advanced tools for the same purpose. They can produce, manage and synchronize a number of package repositories, mirror other repositories, even cherry-pick packages from official repositories and provide them locally, create signatures of the generated package indices and thus provide signed repositories. <command>reprepro</command> stores packages and checksums in a Berkeley DB database file, so no database server is needed. <command>aptly</command> provides the same functionality, but it can be easier in handling. Unfortunately, both projects, although probably the most feature-rich solutions, are not actively developed at the moment." |
| 1145 |
msgstr "" |
| 1146 |
|
| 1147 |
msgid "<command>reprepro</command> comes with a lot of documentation and examples in <filename>/usr/share/doc/reprepro/</filename>, while <command>aptly</command> has a vast online documentation. <ulink type=\"block\" url=\"https://www.aptly.info/\" />" |
| 1148 |
msgstr "" |
| 1149 |
|
| 1150 |
#, fuzzy |
| 1151 |
#| msgid "<primary><command>pbuilder</command></primary>" |
| 1152 |
msgid "<primary><command>reprepro</command></primary>" |
| 1153 |
msgstr "<primary><command>pbuilder</command></primary>" |
| 1154 |
|
| 1155 |
#, fuzzy |
| 1156 |
#| msgid "<primary><command>dput</command></primary>" |
| 1157 |
msgid "<primary><command>aptly</command></primary>" |
| 1158 |
msgstr "<primary><command>dput</command></primary>" |
| 1159 |
|
| 1160 |
msgid "Configuring <command>mini-dinstall</command> requires setting up a <filename>~/.mini-dinstall.conf</filename> file; in the Falcot Corp case, the contents are as follows:" |
| 1161 |
msgstr "La configuration de <command>mini-dinstall</command> nécessite de mettre en place un fichier <filename>~/.mini-dinstall.conf</filename>, que les administrateurs de Falcot SA ont renseigné comme suit :" |
| 1162 |
|
| 1163 |
msgid "" |
| 1164 |
"\n" |
| 1165 |
"[DEFAULT]\n" |
| 1166 |
"archive_style = flat\n" |
| 1167 |
"archivedir = /srv/vhosts/packages\n" |
| 1168 |
"\n" |
| 1169 |
"verify_sigs = 0\n" |
| 1170 |
"mail_to = [email protected]\n" |
| 1171 |
"\n" |
| 1172 |
"generate_release = 1\n" |
| 1173 |
"release_origin = Falcot Corp\n" |
| 1174 |
"release_codename = stable\n" |
| 1175 |
"\n" |
| 1176 |
"[updates]\n" |
| 1177 |
"release_label = Recompiled Debian Packages\n" |
| 1178 |
"\n" |
| 1179 |
"[internal]\n" |
| 1180 |
"release_label = Internal Packages" |
| 1181 |
msgstr "" |
| 1182 |
"\n" |
| 1183 |
"[DEFAULT]\n" |
| 1184 |
"archive_style = flat\n" |
| 1185 |
"archivedir = /srv/vhosts/packages\n" |
| 1186 |
"\n" |
| 1187 |
"verify_sigs = 0\n" |
| 1188 |
"mail_to = [email protected]\n" |
| 1189 |
"\n" |
| 1190 |
"generate_release = 1\n" |
| 1191 |
"release_origin = Falcot SA\n" |
| 1192 |
"release_codename = stable\n" |
| 1193 |
"\n" |
| 1194 |
"[updates]\n" |
| 1195 |
"release_label = Recompiled Debian Packages\n" |
| 1196 |
"\n" |
| 1197 |
"[internal]\n" |
| 1198 |
"release_label = Internal Packages" |
| 1199 |
|
| 1200 |
msgid "One decision worth noting is the generation of <filename>Release</filename> files for each archive. This can help manage package installation priorities using the <filename>/etc/apt/preferences</filename> configuration file (see <xref linkend=\"sect.apt.priorities\" /> for details)." |
| 1201 |
msgstr "Il est intéressant d'y remarquer la décision de générer des fichiers <filename>Release</filename> pour chacune des archives. Cela permettra éventuellement de gérer les priorités d'installation des paquets à l'aide du fichier de configuration <filename>/etc/apt/preferences</filename> (voir <xref linkend=\"sect.apt.priorities\" /> pour les détails)." |
| 1202 |
|
| 1203 |
msgid "<emphasis>SECURITY</emphasis> <command>mini-dinstall</command> and permissions" |
| 1204 |
msgstr "<emphasis>SÉCURITÉ</emphasis> <command>mini-dinstall</command> et droits" |
| 1205 |
|
| 1206 |
#, fuzzy |
| 1207 |
#| msgid "Since <command>mini-dinstall</command> has been designed to run as a regular user, there's no need to run it as root. The easiest way is to configure everything within the user account belonging to the administrator in charge of creating the Debian packages. Since only this administrator has the required permissions to put files in the <filename>incoming/</filename> directory, we can deduce that the administrator authenticated the origin of each package prior to deployment and <command>mini-dinstall</command> does not need to do it again. This explains the <literal>verify_sigs = 0</literal> parameter (which means that signatures need not be verified). However, if the contents of packages are sensitive, we can reverse the setting and elect to authenticate with a keyring containing the public keys of persons allowed to create packages (configured with the <literal>extra_keyrings</literal> parameter); <command>mini-dinstall</command> will then check the origin of each incoming package by analyzing the signature integrated to the <filename>*.changes</filename> file." |
| 1208 |
msgid "Since <command>mini-dinstall</command> has been designed to run as a regular user, there is no need to run it as root. The easiest way is to configure everything within the user account belonging to the administrator in charge of creating the Debian packages. Since only this administrator has the required permissions to put files in the <filename>incoming/</filename> directory, we can deduce that the administrator authenticated the origin of each package prior to deployment and <command>mini-dinstall</command> does not need to do it again. This explains the <literal>verify_sigs = 0</literal> parameter (which means that signatures need not be verified). However, if the contents of packages are sensitive, we can reverse the setting and elect to authenticate with a keyring containing the public keys of persons allowed to create packages (configured with the <literal>extra_keyrings</literal> parameter); <command>mini-dinstall</command> will then check the origin of each incoming package by analyzing the signature integrated to the <filename>*.changes</filename> file." |
| 1209 |
msgstr "<command>mini-dinstall</command> étant prévu pour fonctionner dans un compte utilisateur, il ne serait pas raisonnable de l'employer avec le compte <literal>root</literal>. La solution la plus simple est de tout configurer au sein du compte utilisateur de l'administrateur qui a la responsabilité de créer les paquets Debian. Étant donné que lui seul a le droit de déposer des fichiers dans le répertoire <filename>incoming/</filename>, il n'est pas nécessaire d'authentifier l'origine de chaque paquet à installer : on peut considérer que l'administrateur l'aura fait préalablement. Cela justifie le paramètre <literal>verify_sigs = 0</literal> (pas de vérification des signatures). Toutefois, si le contenu des paquets est très sensible, il est possible de revenir sur ce choix et d'avoir un trousseau de clés publiques identifiant les personnes habilitées à créer des paquets (le paramètre <literal>extra_keyrings</literal> existe à cette fin) ; <command>mini-dinstall</command> vérifiera la provenance de chaque paquet déposé en analysant la signature intégrée au fichier <filename>.changes</filename>." |
| 1210 |
|
| 1211 |
msgid "Invoking <command>mini-dinstall</command> actually starts a daemon in the background. As long as this daemon runs, it will check for new packages in the <filename>incoming/</filename> directory every half-hour; when a new package arrives, it will be moved to the archive and the appropriate <filename>Packages.gz</filename> and <filename>Sources.gz</filename> files will be regenerated. If running a daemon is a problem, <command>mini-dinstall</command> can also be manually invoked in batch mode (with the <literal>-b</literal> option) every time a package is uploaded into the <filename>incoming/</filename> directory. Other possibilities provided by <command>mini-dinstall</command> are documented in its <citerefentry><refentrytitle>mini-dinstall</refentrytitle> <manvolnum>1</manvolnum></citerefentry> manual page." |
| 1212 |
msgstr "L'exécution de <command>mini-dinstall</command> démarre en fait le démon en arrière-plan. Tant qu'il fonctionne, il vérifie toutes les demi-heures si un nouveau paquet est disponible dans le répertoire <filename>incoming/</filename>, le place dans l'archive et régénère les différents fichiers <filename>Packages.gz</filename> et <filename>Sources.gz</filename>. Si la présence d'un démon constitue un problème, il est possible de l'invoquer en mode non interactif (ou <foreignphrase>batch</foreignphrase>), à l'aide de l'option <literal>-b</literal>, à chaque fois qu'un paquet aura été déposé dans le répertoire <filename>incoming/</filename>. Découvrez les autres possibilités offertes par <command>mini-dinstall</command> en consultant sa page de manuel <citerefentry><refentrytitle>mini-dinstall</refentrytitle><manvolnum>1</manvolnum></citerefentry>." |
| 1213 |
|
| 1214 |
msgid "<emphasis>EXTRA</emphasis> Generating a signed archive" |
| 1215 |
msgstr "<emphasis>COMPLÉMENTS</emphasis> Générer une archive signée" |
| 1216 |
|
| 1217 |
msgid "The APT suite checks a chain of cryptographic signatures on the packages it handles before installing them, in order to ensure their authenticity (see <xref linkend=\"sect.package-authentication\" />). Private APT archives can then be a problem, since the machines using them will keep displaying warnings about unsigned packages. A diligent administrator will therefore integrate private archives with the secure APT mechanism." |
| 1218 |
msgstr "Les outils APT effectuent par défaut une vérification d'une chaîne de signatures cryptographiques apposées sur les paquets qu'ils manipulent, avant de les installer, dans le but de s'assurer de leur authenticité (voir la <xref linkend=\"sect.package-authentication\" />). Les archives APT privées posent alors problème, car les machines qui doivent les utiliser vont sans arrêt afficher des messages d'avertissement pour signaler que les paquets que ces archives contiennent ne sont pas signés. Il est donc souvent judicieux de s'assurer que même les archives privées bénéficient du mécanisme <foreignphrase>secure APT</foreignphrase>." |
| 1219 |
|
| 1220 |
msgid "To help with this process, <command>mini-dinstall</command> includes a <literal>release_signscript</literal> configuration option that allows specifying a script to use for generating the signature. A good starting point is the <filename>sign-release.sh</filename> script provided by the <emphasis role=\"pkg\">mini-dinstall</emphasis> package in <filename>/usr/share/doc/mini-dinstall/examples/</filename>; local changes may be relevant." |
| 1221 |
msgstr "<command>mini-dinstall</command> propose pour cela l'option de configuration <literal>release_signscript</literal>, qui permet de spécifier un script à utiliser pour générer la signature. On pourra par exemple utiliser le script <filename>sign-release.sh</filename> fourni par le paquet <emphasis role=\"pkg\">mini-dinstall</emphasis> dans <filename>/usr/share/doc/mini-dinstall/examples/</filename>, après l'avoir éventuellement adapté aux besoins locaux." |
| 1222 |
|
| 1223 |
msgid "Becoming a Package Maintainer" |
| 1224 |
msgstr "Devenir mainteneur de paquet" |
| 1225 |
|
| 1226 |
#, fuzzy |
| 1227 |
#| msgid "<primary>package</primary><secondary>types</secondary>" |
| 1228 |
msgid "<primary>package</primary><secondary>maintainer</secondary>" |
| 1229 |
msgstr "<primary>paquet</primary><secondary>types</secondary>" |
| 1230 |
|
| 1231 |
#, fuzzy |
| 1232 |
#| msgid "<primary>package</primary><secondary>types</secondary>" |
| 1233 |
msgid "<primary>package</primary><secondary>new maintainer</secondary>" |
| 1234 |
msgstr "<primary>paquet</primary><secondary>types</secondary>" |
| 1235 |
|
| 1236 |
#, fuzzy |
| 1237 |
#| msgid "<primary>package</primary><secondary>types</secondary>" |
| 1238 |
msgid "<primary>maintainer</primary><secondary>package maintainer</secondary>" |
| 1239 |
msgstr "<primary>paquet</primary><secondary>types</secondary>" |
| 1240 |
|
| 1241 |
msgid "Learning to Make Packages" |
| 1242 |
msgstr "Apprendre à faire des paquets" |
| 1243 |
|
| 1244 |
#, fuzzy |
| 1245 |
#| msgid "<primary>package</primary><secondary>types</secondary>" |
| 1246 |
msgid "<primary>package</primary><secondary>creation</secondary>" |
| 1247 |
msgstr "<primary>paquet</primary><secondary>types</secondary>" |
| 1248 |
|
| 1249 |
#, fuzzy |
| 1250 |
#| msgid "Creating a quality Debian package is not always a simple task, and becoming a package maintainer takes some learning, both with theory and practice. It's not a simple matter of building and installing software; rather, the bulk of the complexity comes from understanding the problems and conflicts, and more generally the interactions, with the myriad of other packages available." |
| 1251 |
msgid "Creating a quality Debian package is not always a simple task, and becoming a package maintainer takes some learning, both with theory and practice in technical and legal matters. It is not a simple matter of building and installing software; rather, the bulk of the complexity comes from understanding the problems and conflicts, and more generally the interactions, with the myriad of other packages available." |
| 1252 |
msgstr "Construire un paquet Debian de qualité n'est pas chose facile et on ne s'improvise pas responsable de paquet. C'est une activité qui s'apprend par la pratique et par la théorie. Elle ne se limite pas à compiler et installer un logiciel. Elle implique surtout de maîtriser les problèmes, conflits et interactions qui se produiront avec les milliers d'autres paquets logiciels." |
| 1253 |
|
| 1254 |
msgid "Rules" |
| 1255 |
msgstr "Les règles" |
| 1256 |
|
| 1257 |
#, fuzzy |
| 1258 |
#| msgid "<primary>package</primary><secondary>types</secondary>" |
| 1259 |
msgid "<primary>package</primary><secondary>policy</secondary>" |
| 1260 |
msgstr "<primary>paquet</primary><secondary>types</secondary>" |
| 1261 |
|
| 1262 |
#, fuzzy |
| 1263 |
#| msgid "<primary>package</primary><secondary>types</secondary>" |
| 1264 |
msgid "<primary>Debian</primary><secondary>Policy</secondary>" |
| 1265 |
msgstr "<primary>paquet</primary><secondary>types</secondary>" |
| 1266 |
|
| 1267 |
msgid "<primary><filename>control</filename></primary><secondary><literal>Standards-Version</literal>, header field</secondary>" |
| 1268 |
msgstr "" |
| 1269 |
|
| 1270 |
#, fuzzy |
| 1271 |
#| msgid "A Debian package must comply with the precise rules compiled in the Debian policy, and each package maintainer must know them. There is no requirement to know them by heart, but rather to know they exist and to refer to them whenever a choice presents a non-trivial alternative. Every Debian maintainer has made mistakes by not knowing about a rule, but this is not a huge problem as long as the error gets fixed when a user reports it as a bug report (which tends to happen fairly soon thanks to advanced users). <ulink type=\"block\" url=\"https://www.debian.org/doc/debian-policy/\" />" |
| 1272 |
msgid "A Debian package must comply with the precise rules compiled in the Debian policy, and each package maintainer must know them. There is no requirement to know them by heart, but rather to know they exist and to refer to them whenever a choice presents a non-trivial alternative. Every Debian maintainer has made mistakes by not knowing about a rule, but this is not a huge problem as long as the error gets fixed when a user reports it as a bug report (which tends to happen fairly soon thanks to advanced users). The <literal>Standards-Version</literal> field in <filename>debian/control</filename> specifies the version of the Debian policy with which a package complies. Maintainers should comply to the latest version of the Debian policy. <ulink type=\"block\" url=\"https://www.debian.org/doc/debian-policy/\" />" |
| 1273 |
msgstr "Un paquet Debian est conforme aux règles précises édictées dans la charte Debian. Chaque responsable de paquet se doit de les connaître. Il ne s'agit pas de les réciter par cœur, mais de savoir qu'elles existent et de s'y référer lorsque l'on n'est pas sûr de son choix. Tout mainteneur Debian officiel a déjà commis des erreurs en ignorant l'existence d'une règle, mais ce n'est pas dramatique : un utilisateur avancé de ses paquets finit tôt ou tard par signaler cette négligence sous la forme d'un rapport de bogue. <ulink type=\"block\" url=\"http://www.debian.org/doc/debian-policy/\" />" |
| 1274 |
|
| 1275 |
msgid "Procedures" |
| 1276 |
msgstr "Les procédures" |
| 1277 |
|
| 1278 |
#, fuzzy |
| 1279 |
#| msgid "<primary>package</primary><secondary>types</secondary>" |
| 1280 |
msgid "<primary>Debian</primary><secondary>Developer's Reference</secondary>" |
| 1281 |
msgstr "<primary>paquet</primary><secondary>types</secondary>" |
| 1282 |
|
| 1283 |
#, fuzzy |
| 1284 |
#| msgid "<primary>package</primary><secondary>types</secondary>" |
| 1285 |
msgid "<primary>package</primary><secondary>developer's reference</secondary>" |
| 1286 |
msgstr "<primary>paquet</primary><secondary>types</secondary>" |
| 1287 |
|
| 1288 |
msgid "Debian is not a simple collection of individual packages. Everyone's packaging work is part of a collective project; being a Debian developer involves knowing how the Debian project operates as a whole. Every developer will, sooner or later, interact with others. The Debian Developer's Reference (in the <emphasis role=\"pkg\">developers-reference</emphasis> package) summarizes what every developer must know in order to interact as smoothly as possible with the various teams within the project, and to take the best possible advantages of the available resources. This document also enumerates a number of duties a developer is expected to fulfill. <ulink type=\"block\" url=\"https://www.debian.org/doc/manuals/developers-reference/\" />" |
| 1289 |
msgstr "Debian n'est pas une collection de paquets réalisés individuellement. Le travail de chacun s'inscrit dans un projet collectif et, à ce titre, on ne peut être développeur Debian et ignorer le fonctionnement global de la distribution. Tôt ou tard, chaque développeur doit interagir avec d'autres volontaires. La référence du développeur Debian (paquet <emphasis role=\"pkg\">developers-reference-fr</emphasis>) reprend tout ce qu'il faut savoir pour interagir au mieux avec les différentes équipes du projet et profiter au maximum des ressources mises à disposition. Ce document précise également un certain nombre de devoirs que chaque développeur se doit de remplir. <ulink type=\"block\" url=\"https://www.debian.org/doc/manuals/developers-reference/\" />" |
| 1290 |
|
| 1291 |
msgid "Tools" |
| 1292 |
msgstr "Les outils" |
| 1293 |
|
| 1294 |
msgid "Many tools help package maintainers in their work. This section describes them quickly, but does not give the full details, since they all have comprehensive documentation of their own." |
| 1295 |
msgstr "Toute une panoplie d'outils aide les responsables de paquets dans leur travail. Ce chapitre les décrit rapidement sans détailler leur emploi, car ils sont tous bien documentés." |
| 1296 |
|
| 1297 |
#, fuzzy |
| 1298 |
#| msgid "<primary>package</primary><secondary>types</secondary>" |
| 1299 |
msgid "<primary>package</primary><secondary>tools</secondary>" |
| 1300 |
msgstr "<primary>paquet</primary><secondary>types</secondary>" |
| 1301 |
|
| 1302 |
msgid "devscripts" |
| 1303 |
msgstr "devscripts" |
| 1304 |
|
| 1305 |
msgid "<primary><command>dch</command></primary>" |
| 1306 |
msgstr "<primary><command>dch</command></primary>" |
| 1307 |
|
| 1308 |
msgid "<primary><command>uscan</command></primary>" |
| 1309 |
msgstr "<primary><command>uscan</command></primary>" |
| 1310 |
|
| 1311 |
msgid "<primary><command>debi</command></primary>" |
| 1312 |
msgstr "<primary><command>debi</command></primary>" |
| 1313 |
|
| 1314 |
msgid "<primary><command>debc</command></primary>" |
| 1315 |
msgstr "<primary><command>debc</command></primary>" |
| 1316 |
|
| 1317 |
#, fuzzy |
| 1318 |
#| msgid "<primary><command>debi</command></primary>" |
| 1319 |
msgid "<primary><command>bts</command></primary>" |
| 1320 |
msgstr "<primary><command>debi</command></primary>" |
| 1321 |
|
| 1322 |
msgid "The <emphasis role=\"pkg\">devscripts</emphasis> package contains many programs helping with a wide array of a Debian developer's job:" |
| 1323 |
msgstr "Le paquet <emphasis role=\"pkg\">devscripts</emphasis> contient de nombreux programmes couvrant bien des aspects du travail d'un développeur Debian :" |
| 1324 |
|
| 1325 |
msgid "<command>debuild</command> allows generating a package (with <command>dpkg-buildpackage</command>) and running <command>lintian</command> to check its compliance with the Debian policy afterwards." |
| 1326 |
msgstr "<command>debuild</command> sert à générer un paquet (<command>dpkg-buildpackage</command>) et à vérifier dans la foulée s'il est conforme à la charte Debian (<command>lintian</command>)." |
| 1327 |
|
| 1328 |
msgid "<command>debclean</command> cleans a source package after a binary package has been generated." |
| 1329 |
msgstr "<command>debclean</command> nettoie un paquet source après la génération d'un paquet binaire." |
| 1330 |
|
| 1331 |
msgid "<command>dch</command> allows quick and easy editing of a <filename>debian/changelog</filename> file in a source package." |
| 1332 |
msgstr "<command>dch</command> permet d'éditer facilement un fichier <filename>debian/changelog</filename> dans un paquet source." |
| 1333 |
|
| 1334 |
msgid "<command>uscan</command> checks whether a new version of a software has been released by the upstream author; this requires a <filename>debian/watch</filename> file with a description of the location of such releases." |
| 1335 |
msgstr "<command>uscan</command> vérifie si l'auteur amont a publié une nouvelle version de son logiciel. Ce programme nécessite un fichier <filename>debian/watch</filename> décrivant l'emplacement de publication de ces archives." |
| 1336 |
|
| 1337 |
msgid "<primary><filename>debian</filename>, directory</primary><secondary><filename>watch</filename></secondary>" |
| 1338 |
msgstr "" |
| 1339 |
|
| 1340 |
msgid "<command>debi</command> allows installing (with <command>dpkg -i</command>) the Debian package that was just generated without the need to type its full name and path." |
| 1341 |
msgstr "<command>debi</command> installe (<command>dpkg -i</command>) le paquet Debian qui vient d'être généré (sans devoir saisir son nom complet)." |
| 1342 |
|
| 1343 |
msgid "In a similar fashion, <command>debc</command> allows scanning the contents of the recently-generated package (with <command>dpkg -c</command>), without needing to type its full name and path." |
| 1344 |
msgstr "<command>debc</command> sert à consulter le contenu (<command>dpkg -c</command>) du paquet qui vient d'être généré (sans devoir saisir son nom complet)." |
| 1345 |
|
| 1346 |
#, fuzzy |
| 1347 |
#| msgid "<command>bts</command> controls the bug tracking system from the command line; this program automatically generates the appropriate emails." |
| 1348 |
msgid "<command>bts</command> controls the bug tracking system from the command line; this program automatically generates the appropriate emails. <ulink type=\"block\" url=\"https://www.debian.org/Bugs/server-refcard\" />" |
| 1349 |
msgstr "<command>bts</command> manipule le système de suivi de bogues depuis la ligne de commande ; ce programme génère automatiquement les courriers électroniques adéquats." |
| 1350 |
|
| 1351 |
msgid "<command>debrelease</command> uploads a recently-generated package to a remote server, without needing to type the full name and path of the related <filename>.changes</filename> file." |
| 1352 |
msgstr "<command>debrelease</command> envoie la nouvelle version du paquet sur un serveur distant sans devoir saisir le nom complet du fichier <filename>.changes</filename> concerné." |
| 1353 |
|
| 1354 |
#, fuzzy |
| 1355 |
#| msgid "<primary><filename>Makefile</filename></primary>" |
| 1356 |
msgid "<primary><filename>.changes</filename></primary>" |
| 1357 |
msgstr "<primary><filename>Makefile</filename></primary>" |
| 1358 |
|
| 1359 |
msgid "<command>debsign</command> signs the <filename>*.dsc</filename> and <filename>*.changes</filename> files." |
| 1360 |
msgstr "<command>debsign</command> signe les fichiers <filename>.dsc</filename> et <filename>.changes</filename>." |
| 1361 |
|
| 1362 |
msgid "<command>uupdate</command> automates the creation of a new revision of a package when a new upstream version has been released." |
| 1363 |
msgstr "<command>uupdate</command> crée automatiquement une nouvelle révision du paquet lors de la publication d'une nouvelle version amont." |
| 1364 |
|
| 1365 |
msgid "All of the mentioned commands are documented in their respective manual pages. They can further be configured per user in one file: <filename>~/.devscripts</filename>." |
| 1366 |
msgstr "" |
| 1367 |
|
| 1368 |
msgid "<emphasis role=\"pkg\">debhelper</emphasis> and <emphasis role=\"pkg\">dh-make</emphasis>" |
| 1369 |
msgstr "<emphasis role=\"pkg\">debhelper</emphasis> et <emphasis role=\"pkg\">dh-make</emphasis>" |
| 1370 |
|
| 1371 |
msgid "<primary><emphasis>debhelper</emphasis></primary>" |
| 1372 |
msgstr "<primary><emphasis>debhelper</emphasis></primary>" |
| 1373 |
|
| 1374 |
msgid "<primary><emphasis>dh-make</emphasis></primary>" |
| 1375 |
msgstr "<primary><emphasis>dh-make</emphasis></primary>" |
| 1376 |
|
| 1377 |
#, fuzzy |
| 1378 |
#| msgid "<primary><command>dch</command></primary>" |
| 1379 |
msgid "<primary><command>dh</command></primary>" |
| 1380 |
msgstr "<primary><command>dch</command></primary>" |
| 1381 |
|
| 1382 |
#, fuzzy |
| 1383 |
#| msgid "<primary>package</primary><secondary>types</secondary>" |
| 1384 |
msgid "<primary><filename>debian</filename></primary><secondary><filename>rules</filename></secondary>" |
| 1385 |
msgstr "<primary>paquet</primary><secondary>types</secondary>" |
| 1386 |
|
| 1387 |
#, fuzzy |
| 1388 |
#| msgid "Debhelper is a set of scripts easing the creation of policy-compliant packages; these scripts are invoked from <filename>debian/rules</filename>. Debhelper has been widely adopted within Debian, as evidenced by the fact that it is used by the majority of official Debian packages. All the commands it contains have a <command>dh_</command> prefix." |
| 1389 |
msgid "Debhelper is a set of scripts easing the creation of policy-compliant packages; these scripts are invoked from <filename>debian/rules</filename>. Debhelper has been widely adopted within Debian, as evidenced by the fact that it is used by the majority of official Debian packages. All the commands it contains have a <command>dh_</command> prefix. Each of them is documented in a manual page. The different compatibility levels and common options are described in <citerefentry><refentrytitle>debhelper</refentrytitle> <manvolnum>7</manvolnum></citerefentry>." |
| 1390 |
msgstr "debhelper est un ensemble de scripts facilitant la création d'un paquet conforme à la charte Debian, invoqués depuis <filename>debian/rules</filename>. Il a conquis de très nombreux développeurs Debian ; pour preuve, la majorité des paquets officiels l'utilisent. Tous les scripts sont préfixés par <command>dh_</command>." |
| 1391 |
|
| 1392 |
msgid "The <command>dh_make</command> script (in the <emphasis>dh-make</emphasis> package) creates files required for generating a Debian package in a directory initially containing the sources for a piece of software. As can be guessed from the name of the program, the generated files use debhelper by default." |
| 1393 |
msgstr "Le script <command>dh_make</command> (du paquet <emphasis>dh-make</emphasis>) intègre les fichiers nécessaires à la génération d'un paquet Debian dans un répertoire contenant les sources d'un logiciel. Les fichiers qu'il ajoute utilisent debhelper de manière standard, comme son nom le laisse supposer." |
| 1394 |
|
| 1395 |
#, fuzzy |
| 1396 |
#| msgid "The <command>lintian</command> Program" |
| 1397 |
msgid "<command>lintian</command>" |
| 1398 |
msgstr "Le programme <command>lintian</command>" |
| 1399 |
|
| 1400 |
msgid "<primary><command>lintian</command></primary>" |
| 1401 |
msgstr "<primary><command>lintian</command></primary>" |
| 1402 |
|
| 1403 |
#, fuzzy |
| 1404 |
#| msgid "<primary>package</primary><secondary>types</secondary>" |
| 1405 |
msgid "<primary>package</primary><secondary>checker</secondary>" |
| 1406 |
msgstr "<primary>paquet</primary><secondary>types</secondary>" |
| 1407 |
|
| 1408 |
#, fuzzy |
| 1409 |
#| msgid "This tool is one of the most important: it's the Debian package checker. It is based on a large array of tests created from the Debian policy, and detects quickly and automatically many errors that can then be fixed before packages are released." |
| 1410 |
msgid "This tool is one of the most important: it is the Debian package checker. It is based on a large array of tests created from the Debian policy, and detects quickly and automatically many errors that can then be fixed before packages are released." |
| 1411 |
msgstr "Ce programme fait partie des outils les plus importants : c'est le vérificateur de paquets Debian. Il dispose d'une vaste batterie de tests créés en fonction de la charte Debian. Il permet de trouver rapidement et automatiquement de nombreuses erreurs et donc de les corriger avant de publier les paquets." |
| 1412 |
|
| 1413 |
msgid "This tool is only a helper, and it sometimes gets it wrong (for instance, since the Debian policy changes over time, <command>lintian</command> is sometimes outdated). It is also not exhaustive: not getting any Lintian error should not be interpreted as a proof that the package is perfect; at most, it avoids the most common errors." |
| 1414 |
msgstr "Cet outil ne fournit qu'une aide et il arrive qu'il se trompe (la charte Debian évolue parfois, <command>lintian</command> peut alors être momentanément en retard). Par ailleurs, il n'est pas exhaustif : qu'il ne signale aucune erreur ne signifie pas qu'un paquet est parfait, tout au plus qu'il évite les erreurs les plus communes." |
| 1415 |
|
| 1416 |
#, fuzzy |
| 1417 |
#| msgid "The <command>piuparts</command> Program" |
| 1418 |
msgid "<command>piuparts</command>" |
| 1419 |
msgstr "Le programme <command>piuparts</command>" |
| 1420 |
|
| 1421 |
msgid "<primary><command>piuparts</command></primary>" |
| 1422 |
msgstr "<primary><command>piuparts</command></primary>" |
| 1423 |
|
| 1424 |
msgid "This is another important tool: it automates the installation, upgrade, removal and purge of a package (in an isolated environment), and checks that none of these operations leads to an error. It can help in detecting missing dependencies, and it also detects when files are incorrectly left over after the package got purged." |
| 1425 |
msgstr "Il s'agit d'un autre outil important : il automatise l'installation, la mise à jour, la suppression et la purge d'un paquet (dans un environnement isolé) et vérifie qu'aucune de ces opérations n'entraîne d'erreur. Il peut aider à détecter les dépendances manquantes et détecte également lorsque des fichiers subsistent de manière inattendue après que le paquet a été purgé." |
| 1426 |
|
| 1427 |
#, fuzzy |
| 1428 |
#| msgid "<primary><emphasis role=\"pkg\">devscripts</emphasis></primary>" |
| 1429 |
msgid "<emphasis role=\"pkg\">autopkgtest</emphasis>" |
| 1430 |
msgstr "<primary><emphasis role=\"pkg\">devscripts</emphasis></primary>" |
| 1431 |
|
| 1432 |
msgid "<primary><emphasis>autopkgtest</emphasis></primary>" |
| 1433 |
msgstr "<primary><emphasis>autopkgtest</emphasis></primary>" |
| 1434 |
|
| 1435 |
#, fuzzy |
| 1436 |
#| msgid "<primary>package</primary><secondary>types</secondary>" |
| 1437 |
msgid "<primary>package</primary><secondary>tests</secondary>" |
| 1438 |
msgstr "<primary>paquet</primary><secondary>types</secondary>" |
| 1439 |
|
| 1440 |
msgid "<command>autopkgtest</command> runs tests on binary packages, using the tests supplied in the source package in <filename>debian/tests/</filename>. Several commands allow the easy creation of chrooted or virtual test environments." |
| 1441 |
msgstr "" |
| 1442 |
|
| 1443 |
#, fuzzy |
| 1444 |
#| msgid "<primary><emphasis role=\"pkg\">devscripts</emphasis></primary>" |
| 1445 |
msgid "<emphasis role=\"pkg\">reprotest</emphasis>" |
| 1446 |
msgstr "<primary><emphasis role=\"pkg\">devscripts</emphasis></primary>" |
| 1447 |
|
| 1448 |
msgid "<primary><emphasis>reprotest</emphasis></primary>" |
| 1449 |
msgstr "<primary><emphasis>reprotest</emphasis></primary>" |
| 1450 |
|
| 1451 |
msgid "<command>reprotest</command> builds the same source code twice in different environments, and then checks the binaries produced by each build for differences. If any are found, then <command>diffoscope</command> (if unavailable, <command>diff</command>) is used to display them in detail for later analysis." |
| 1452 |
msgstr "" |
| 1453 |
|
| 1454 |
#, fuzzy |
| 1455 |
#| msgid "<primary><command>dch</command></primary>" |
| 1456 |
msgid "<primary><command>diffoscope</command></primary>" |
| 1457 |
msgstr "<primary><command>dch</command></primary>" |
| 1458 |
|
| 1459 |
msgid "<command>dupload</command> and <command>dput</command>" |
| 1460 |
msgstr "<command>dupload</command> et <command>dput</command>" |
| 1461 |
|
| 1462 |
msgid "<primary><command>dupload</command></primary>" |
| 1463 |
msgstr "<primary><command>dupload</command></primary>" |
| 1464 |
|
| 1465 |
msgid "<primary><command>dput</command></primary>" |
| 1466 |
msgstr "<primary><command>dput</command></primary>" |
| 1467 |
|
| 1468 |
#, fuzzy |
| 1469 |
#| msgid "The <command>dupload</command> and <command>dput</command> commands allow uploading a Debian package to a (possibly remote) server. This allows developers to publish their package on the main Debian server (<literal>ftp-master.debian.org</literal>) so that it can be integrated to the archive and distributed by mirrors. These commands take a <filename>*.changes</filename> file as a parameter, and deduce the other relevant files from its contents." |
| 1470 |
msgid "The <command>dupload</command> and <command>dput</command> commands allow uploading a Debian package to a (possibly remote) server. This allows developers to publish their package on the main Debian server (<literal>ftp-master.debian.org</literal>) so that it can be integrated to the archive and distributed by mirrors. These commands take a <filename>.changes</filename> file as a parameter, and deduce the other relevant files from its contents." |
| 1471 |
msgstr "<command>dupload</command> et <command>dput</command> servent à envoyer une nouvelle version d'un paquet Debian sur un serveur local ou distant. C'est ainsi que les développeurs envoient leur paquet sur le serveur principal de Debian (<literal>ftp-master.debian.org</literal>) pour qu'il soit intégré à l'archive et distribué par les miroirs. Ces commandes prennent en paramètre un fichier <filename>.changes</filename> et en déduisent les autres fichiers à envoyer." |
| 1472 |
|
| 1473 |
#, fuzzy |
| 1474 |
#| msgid "<emphasis role=\"pkg\">debhelper</emphasis> and <emphasis role=\"pkg\">dh-make</emphasis>" |
| 1475 |
msgid "<emphasis role=\"pkg\">git-buildpackage</emphasis> and <emphasis role=\"pkg\">dgit</emphasis>" |
| 1476 |
msgstr "<emphasis role=\"pkg\">debhelper</emphasis> et <emphasis role=\"pkg\">dh-make</emphasis>" |
| 1477 |
|
| 1478 |
#, fuzzy |
| 1479 |
#| msgid "<primary><emphasis role=\"pkg\">devscripts</emphasis></primary>" |
| 1480 |
msgid "<primary><emphasis role=\"pkg\">git-buildpackage</emphasis></primary>" |
| 1481 |
msgstr "<primary><emphasis role=\"pkg\">devscripts</emphasis></primary>" |
| 1482 |
|
| 1483 |
#, fuzzy |
| 1484 |
#| msgid "<primary><emphasis role=\"pkg\">devscripts</emphasis></primary>" |
| 1485 |
msgid "<primary><emphasis role=\"pkg\">dgit</emphasis></primary>" |
| 1486 |
msgstr "<primary><emphasis role=\"pkg\">devscripts</emphasis></primary>" |
| 1487 |
|
| 1488 |
msgid "The project has been using various version control systems over the years to store packaging efforts or package source code, or allow collaborative package maintenance. In an effort to unify the systems and efforts, it was ultimately decided in 2017 to move (almost) all package sources into <emphasis>Git</emphasis> (<xref linkend=\"sidebar.git\" />) onto a Gitlab instance called <literal>salsa.debian.org</literal>. <ulink type=\"block\" url=\"https://salsa.debian.org/\" />" |
| 1489 |
msgstr "" |
| 1490 |
|
| 1491 |
#, fuzzy |
| 1492 |
#| msgid "<primary><literal>Build-Depends</literal>, control field</primary>" |
| 1493 |
msgid "<primary><literal>salsa.debian.org</literal></primary>" |
| 1494 |
msgstr "<primary><literal>Build-Depends</literal>, champ d'en-tête du paquet source</primary>" |
| 1495 |
|
| 1496 |
msgid "To make packaging using Git easier for Debian developers, tools have been developed. These allow not only to store the packaging files in Git, but also to use the Git repositories (and their history) of software projects, put patches applied to package sources into Git history, maintain software versions per distribution, etc." |
| 1497 |
msgstr "" |
| 1498 |
|
| 1499 |
msgid "One of the most famous packages is <emphasis role=\"pkg\">git-buildpackage</emphasis>. An alternative is <emphasis role=\"pkg\">dgit</emphasis>. Of course it is still possible to use neither of those." |
| 1500 |
msgstr "" |
| 1501 |
|
| 1502 |
msgid "Below is an example for a <filename>~/.gbp.conf</filename> configuration file" |
| 1503 |
msgstr "" |
| 1504 |
|
| 1505 |
msgid "" |
| 1506 |
"<![CDATA[[DEFAULT]\n" |
| 1507 |
"builder = sbuild -d bullseye --build-dep-resolver=aptitude -s --source-only-changes --build-failed-commands \"%SBUILD_SHELL\"\n" |
| 1508 |
"pristine-tar = true\n" |
| 1509 |
"\n" |
| 1510 |
"[buildpackage]\n" |
| 1511 |
"sign-tags = true\n" |
| 1512 |
"keyid = XXXX\n" |
| 1513 |
"postbuild = autopkgtest --user debci --apt-upgrade -s \"$GBP_CHANGES_FILE\" -- lxc --sudo autopkgtest-bullseye-amd64 \n" |
| 1514 |
"export-dir = /tmp/build-area/\n" |
| 1515 |
"notify = off\n" |
| 1516 |
"\n" |
| 1517 |
"[import-orig]\n" |
| 1518 |
"filter-pristine-tar = true\n" |
| 1519 |
"sign-tags = true\n" |
| 1520 |
"\n" |
| 1521 |
"[pq]\n" |
| 1522 |
"drop = true\n" |
| 1523 |
"]]>" |
| 1524 |
msgstr "" |
| 1525 |
|
| 1526 |
msgid "Building the package is then as easy as running <command>gbp buildpackage</command> in the Git tree. It will start a package build in a Debian <emphasis role=\"distribution\">Bullseye</emphasis> chroot using <command>sbuild</command>. When the build succeeds, the created files are checked running the <command>autopkgtest</command>-testsuite (if defined). All the various options are explained in <citerefentry><refentrytitle>gbp.conf</refentrytitle> <manvolnum>5</manvolnum></citerefentry> and <filename>/etc/git-buildpackage/gbp.conf</filename>." |
| 1527 |
msgstr "" |
| 1528 |
|
| 1529 |
#, fuzzy |
| 1530 |
#| msgid "<primary><command>debi</command></primary>" |
| 1531 |
msgid "<primary><command>gbp</command></primary>" |
| 1532 |
msgstr "<primary><command>debi</command></primary>" |
| 1533 |
|
| 1534 |
msgid "<primary><filename>/etc</filename></primary><secondary><filename>/etc/git-buildpackage/gbp.conf</filename></secondary>" |
| 1535 |
msgstr "" |
| 1536 |
|
| 1537 |
msgid "All the tools mentioned so far have been included in the continuous integration (CI) process in the <literal>salsa.debian.org</literal> instance as well: <ulink type=\"block\" url=\"https://salsa.debian.org/salsa-ci-team/pipeline\" />" |
| 1538 |
msgstr "" |
| 1539 |
|
| 1540 |
msgid "Acceptance Process" |
| 1541 |
msgstr "Processus d'acceptation" |
| 1542 |
|
| 1543 |
#, fuzzy |
| 1544 |
#| msgid "<primary>package</primary><secondary>types</secondary>" |
| 1545 |
msgid "<primary>Debian</primary><secondary>Developer</secondary>" |
| 1546 |
msgstr "<primary>paquet</primary><secondary>types</secondary>" |
| 1547 |
|
| 1548 |
#, fuzzy |
| 1549 |
#| msgid "<primary><literal>Build-Depends</literal>, control field</primary>" |
| 1550 |
msgid "<primary><literal>nm.debian.org</literal></primary>" |
| 1551 |
msgstr "<primary><literal>Build-Depends</literal>, champ d'en-tête du paquet source</primary>" |
| 1552 |
|
| 1553 |
msgid "Becoming a “Debian developer” is not a simple administrative matter. The process comprises several steps, and is as much an initiation as it is a selection process. In any case, it is formalized and well-documented, so anyone can track their progression on the website dedicated to the new member process. <ulink type=\"block\" url=\"https://nm.debian.org/\" />" |
| 1554 |
msgstr "Ne devient pas développeur Debian qui veut. Différentes étapes jalonnent le processus d'acceptation, qui se veut autant un parcours initiatique qu'une sélection. Ce processus est formalisé et chacun peut suivre sa progression sur le site web des nouveaux mainteneurs (<literal>nm</literal> est l'abréviation de <foreignphrase>New Maintainer</foreignphrase>). <ulink type=\"block\" url=\"http://nm.debian.org/\" />" |
| 1555 |
|
| 1556 |
msgid "<emphasis>EXTRA</emphasis> Lightweight process for “Debian Maintainers”" |
| 1557 |
msgstr "<emphasis>COMPLÉMENTS</emphasis> Processus allégé pour les « Mainteneurs Debian »" |
| 1558 |
|
| 1559 |
#, fuzzy |
| 1560 |
#| msgid "<primary>package</primary><secondary>types</secondary>" |
| 1561 |
msgid "<primary>Debian</primary><secondary>Maintainer</secondary>" |
| 1562 |
msgstr "<primary>paquet</primary><secondary>types</secondary>" |
| 1563 |
|
| 1564 |
msgid "“Debian Maintainer” is another status that gives less privileges than “Debian developer” but whose associated process is quicker. With this status, the contributors can maintain their own packages only. A Debian developer only needs to perform a check on an initial upload, and issue a statement to the effect that they trust the prospective maintainer with the ability to maintain the package on their own." |
| 1565 |
msgstr "Un statut de « Mainteneur Debian » (<foreignphrase>Debian Maintainer</foreignphrase>, DM) a été introduit. Le processus associé est plus léger et les droits que ce statut accorde se restreignent à pouvoir maintenir ses propres paquets. Il suffit qu'un développeur Debian vérifie préalablement tout nouveau paquet et qu'il indique qu'il considère le mainteneur capable de gérer son paquet tout seul." |
| 1566 |
|
| 1567 |
msgid "Prerequisites" |
| 1568 |
msgstr "Prérequis" |
| 1569 |
|
| 1570 |
msgid "All candidates are expected to have at least a working knowledge of the English language. This is required at all levels: for the initial communications with the examiner, of course, but also later, since English is the preferred language for most of the documentation; also, package users will be communicating in English when reporting bugs, and they will expect replies in English." |
| 1571 |
msgstr "Il est demandé à tous les candidats de maîtriser un minimum l'anglais. Cela est nécessaire à tous les niveaux : dans un premier temps pour communiquer avec l'examinateur, mais c'est aussi la langue de prédilection pour une grande partie de la documentation. De plus, les utilisateurs de vos paquets communiqueront avec vous en anglais pour vous signaler des bogues et il faudra être capable de leur répondre." |
| 1572 |
|
| 1573 |
msgid "The other prerequisite deals with motivation. Becoming a Debian developer is a process that only makes sense if the candidate knows that their interest in Debian will last for many months. The acceptance process itself may last for several months, and Debian needs developers for the long haul; each package needs permanent maintenance, and not just an initial upload." |
| 1574 |
msgstr "Le deuxième prérequis porte sur la motivation. Il faut être pleinement conscient que la démarche consistant à devenir développeur Debian n'a de sens que si vous savez par avance que Debian restera un sujet d'intérêt pendant de nombreux mois. En effet, la procédure en elle-même dure plusieurs mois et Debian a besoin de mainteneurs qui s'inscrivent dans la durée, car chaque paquet a besoin d'un mainteneur en permanence (et pas seulement lorsqu'il est créé)." |
| 1575 |
|
| 1576 |
msgid "Registration" |
| 1577 |
msgstr "Inscription" |
| 1578 |
|
| 1579 |
#, fuzzy |
| 1580 |
#| msgid "<primary>package</primary><secondary>types</secondary>" |
| 1581 |
msgid "<primary>package</primary><secondary>sponsor</secondary>" |
| 1582 |
msgstr "<primary>paquet</primary><secondary>types</secondary>" |
| 1583 |
|
| 1584 |
msgid "The first (real) step consists in finding a sponsor or advocate; this means an official developer willing to state that they believe that accepting <emphasis>X</emphasis> would be a good thing for Debian. This usually implies that the candidate has already been active within the community, and that their work has been appreciated. If the candidate is shy and their work is not publicly touted, they can try to convince a Debian developer to advocate them by showing their work in a private way." |
| 1585 |
msgstr "La première étape (réelle) consiste à trouver un sponsor, ou avocat <foreignphrase>(advocate)</foreignphrase> ; c'est un développeur officiel qui affirme « je pense que l'acceptation de <emphasis>X</emphasis> serait une bonne chose pour Debian ». Cela implique normalement que le candidat ait déjà été actif au sein de la communauté et que quelqu'un ait apprécié son travail. Si le candidat est timide et n'affiche pas en public le fruit de son travail, il peut tenter de convaincre individuellement un développeur Debian officiel de le soutenir en lui présentant ses travaux en privé." |
| 1586 |
|
| 1587 |
msgid "<primary>key pair</primary>" |
| 1588 |
msgstr "<primary>biclé</primary>" |
| 1589 |
|
| 1590 |
msgid "At the same time, the candidate must generate a public/private RSA key pair with GnuPG, which should be signed by at least two official Debian developers. The signature authenticates the name on the key. Effectively, during a key signing party, each participant must show an official identification (usually an ID card or passport) together with their key identifiers. This step confirms the link between the human and the keys. This signature thus requires meeting in real life. If you have not yet met any Debian developers in a public free software conference, you can explicitly seek developers living nearby using the list on the following webpage as a starting point. <ulink type=\"block\" url=\"https://wiki.debian.org/Keysigning\" />" |
| 1591 |
msgstr "En parallèle, le candidat doit se générer une biclé (paire publique-privée) RSA avec GnuPG, qu'il doit faire signer par au moins deux développeurs Debian officiels. La signature certifie l'authenticité du nom présent sur la clé. En effet, lors d'une séance de signature de clés, il est d'usage de présenter des papiers d'identité (habituellement une carte d'identité ou un passeport) et les identifiants de ses clés pour officialiser la correspondance entre la personne physique et les clés. Cette signature nécessite donc une rencontre réelle ; si vous n'avez pas encore eu l'occasion de croiser un développeur Debian lors d'une manifestation de logiciels libres, il est possible de solliciter expressément les développeurs en demandant qui serait dans la région concernée par le biais de la liste de diffusion <email>[email protected]</email>. Il existe également une liste de personnes disponibles pour signer des clés, organisée par pays et par ville. <ulink type=\"block\" url=\"http://wiki.debian.org/Keysigning\" />" |
| 1592 |
|
| 1593 |
msgid "Once the registration on <literal>nm.debian.org</literal> has been validated by the advocate, an <emphasis>Application Manager</emphasis> is assigned to the candidate. The application manager will then drive the process through multiple pre-defined steps and checks." |
| 1594 |
msgstr "Une fois l'inscription sur <literal>nm.debian.org</literal> validée par le sponsor, un <foreignphrase>Application Manager</foreignphrase> (« gestionnaire de candidature ») sera chargé de suivre le candidat dans ses démarches et de réaliser les différentes vérifications prévues dans le processus." |
| 1595 |
|
| 1596 |
msgid "The first verification is an identity check. If you already have a key signed by two Debian developers, this step is easy; otherwise, the application manager will try and guide you in your search for Debian developers close by to organize a meet-up and a key signing." |
| 1597 |
msgstr "La première vérification est celle de l'identité. Si vous avez une clé signée par un développeur Debian, cette étape est facile. Dans le cas contraire, l'<foreignphrase>Application Manager</foreignphrase> essaiera de guider le candidat dans sa recherche de développeurs Debian à proximité de chez lui pour qu'une rencontre et une signature de clés puissent être arrangées." |
| 1598 |
|
| 1599 |
msgid "Accepting the Principles" |
| 1600 |
msgstr "Acceptation des principes" |
| 1601 |
|
| 1602 |
msgid "These administrative formalities are followed by philosophical considerations. The point is to make sure that the candidate understands and accepts the social contract and the principles behind Free Software. Joining Debian is only possible if one shares the values that unite the current developers, as expressed in the founding texts (and summarized in <xref linkend=\"the-debian-project\" />)." |
| 1603 |
msgstr "Ces formalités administratives sont suivies de considérations philosophiques. Il est question de s'assurer que le candidat comprend le contrat social et les principes du logiciel libre. En effet, il n'est pas possible de rejoindre Debian si l'on ne partage pas les valeurs qui unissent les développeurs actuels, exprimées dans les deux textes fondateurs (et résumées au <xref linkend=\"the-debian-project\" />)." |
| 1604 |
|
| 1605 |
msgid "In addition, each candidate wishing to join the Debian ranks is expected to know the workings of the project, and how to interact appropriately to solve the problems they will doubtless encounter as time passes. All of this information is generally documented in manuals targeting the new maintainers, and in the Debian developer's reference. An attentive reading of this document should be enough to answer the examiner's questions. If the answers are not satisfactory, the candidate will be informed. They will then have to read (again) the relevant documentation before trying again. In the cases where the existing documentation does not contain the appropriate answer for the question, the candidate can usually reach an answer with some practical experience within Debian, or potentially by discussing with other Debian developers. This mechanism ensures that candidates get involved somewhat in Debian before becoming a full part of it. It is a deliberate policy, by which candidates who eventually join the project are integrated as another piece of an infinitely extensible jigsaw puzzle." |
| 1606 |
msgstr "En plus de cela, il est souhaité que chaque personne qui rejoint les rangs de Debian connaisse déjà son fonctionnement et sache interagir comme il se doit pour résoudre les problèmes qu'elle rencontrera au fil du temps. Toutes ces informations sont généralement documentées dans les divers manuels ciblant les nouveaux mainteneurs, mais aussi et surtout dans le guide de référence du développeur Debian. Une lecture attentive de ce document devrait suffire pour répondre aux questions de l'examinateur. Si les réponses ne sont pas satisfaisantes, il le fera savoir et invitera le candidat à se documenter davantage avant de retenter sa chance. Si la documentation ne semble pas répondre à la question, c'est qu'un peu de pratique au sein de Debian permet de découvrir la réponse par soi-même (éventuellement en discutant avec d'autres développeurs Debian). Ce mécanisme entraîne les gens dans les rouages de Debian avant de pouvoir totalement prendre part au projet. C'est une politique volontaire et les gens qui arrivent finalement à rejoindre le projet s'intègrent comme une pièce supplémentaire d'un puzzle extensible à l'infini." |
| 1607 |
|
| 1608 |
msgid "This step is usually known as the <emphasis>Philosophy & Procedures</emphasis> (P&P for short) in the lingo of the developers involved in the new member process." |
| 1609 |
msgstr "Cette étape est couramment désignée par le terme de <foreignphrase>Philosophy & Procedures</foreignphrase> <foreignphrase>(P&P)</foreignphrase> dans le jargon des personnes impliquées dans le processus d'acceptation de nouveaux mainteneurs." |
| 1610 |
|
| 1611 |
msgid "<primary><emphasis>Philosophy & Procedures</emphasis></primary>" |
| 1612 |
msgstr "<primary><emphasis>Philosophy & Procedures</emphasis></primary>" |
| 1613 |
|
| 1614 |
msgid "Checking Skills" |
| 1615 |
msgstr "Vérification des compétences" |
| 1616 |
|
| 1617 |
msgid "Each application to become an official Debian developer must be justified. Becoming a project member requires showing that this status is legitimate, and that it facilitates the candidate's job in helping Debian. The most common justification is that being granted Debian developer status eases maintenance of a Debian package, but it is not the only one. Some developers join the project to contribute to porting to a specific architecture, others want to improve documentation, and so on." |
| 1618 |
msgstr "Chaque demande pour devenir développeur Debian officiel doit être justifiée. En effet, on ne devient membre que si l'on peut démontrer que ce statut est légitime et qu'il permettra de faciliter le travail du candidat. La justification habituelle est que le statut de développeur Debian facilite la maintenance d'un paquet Debian, mais elle n'est pas universelle. Certains développeurs rejoignent le projet pour contribuer à un portage sur une architecture, d'autres pour contribuer à la documentation, etc." |
| 1619 |
|
| 1620 |
msgid "This step represents the opportunity for the candidate to state what they intend to do within the Debian project and to show what they have already done towards that end. Debian is a pragmatic project and saying something is not enough, if the actions do not match what is announced. Generally, when the intended role within the project is related to package maintenance, a first version of the prospective package will have to be validated technically and uploaded to the Debian servers by a sponsor among the existing Debian developers." |
| 1621 |
msgstr "Cette étape est donc l'occasion pour chaque candidat d'affirmer ce qu'il a l'intention de réaliser dans le cadre de Debian et de montrer ce qu'il a déjà fait dans ce sens. Debian privilégie en effet le pragmatisme et il ne suffit pas de dire quelque chose pour le faire prendre en compte : il faut montrer sa capacité à faire ce qui a été annoncé. En général, lorsqu'il s'agit de mise en paquet, il faudra montrer une première version du paquet et trouver un parrain (parmi les développeurs officiels) qui contrôle sa réalisation technique et l'envoie sur le serveur principal de Debian." |
| 1622 |
|
| 1623 |
msgid "<emphasis>COMMUNITY</emphasis> Sponsoring" |
| 1624 |
msgstr "<emphasis>COMMUNAUTÉ</emphasis> Parrainage" |
| 1625 |
|
| 1626 |
# TODO: INTEGRATE ALTERNATE STRING: <primary><foreignphrase>sponsoring</foreignphrase></primary> |
| 1627 |
msgid "<primary>sponsoring</primary>" |
| 1628 |
msgstr "<primary>parrainage</primary>" |
| 1629 |
|
| 1630 |
#, fuzzy |
| 1631 |
#| msgid "<primary>package</primary><secondary>types</secondary>" |
| 1632 |
msgid "<primary>Debian</primary><secondary>New Member</secondary>" |
| 1633 |
msgstr "<primary>paquet</primary><secondary>types</secondary>" |
| 1634 |
|
| 1635 |
msgid "Debian developers can “sponsor” packages prepared by someone else, meaning that they publish them in the official Debian repositories after having performed a careful review. This mechanism enables external persons, who have not yet gone through the new member process, to contribute occasionally to the project. At the same time, it ensures that all packages included in Debian have always been checked by an official member." |
| 1636 |
msgstr "Le parrainage (ou <foreignphrase>sponsoring</foreignphrase>) est un mécanisme par lequel un développeur Debian ou un mainteneur Debian vérifie un paquet préparé par quelqu'un d'autre et y appose sa signature pour le publier dans les dépôts officiels. Il permet ainsi à des personnes externes au projet, n'ayant pas suivi la procédure des nouveaux mainteneurs, de contribuer ponctuellement au projet, tout en garantissant que les paquets réellement inclus dans Debian ont toujours subi une vérification par un membre officiel." |
| 1637 |
|
| 1638 |
#, fuzzy |
| 1639 |
#| msgid "Finally, the examiner checks the candidate's technical (packaging) skills with a detailed questionnaire. Bad answers are not permitted, but the answer time is not limited. All the documentation is available and several tries are allowed if the first answers are not satisfactory. This step does not intend to discriminate, but to ensure at least a modicum of knowledge common to new contributors." |
| 1640 |
msgid "Finally, the examiner checks the candidate's technical (packaging) skills with a detailed questionnaire. Bad answers are not permitted, but the answer time is not limited. All the documentation is available and several attempts are allowed if the first answers are not satisfactory. This step does not intend to discriminate, but to ensure at least a modicum of knowledge common to new contributors." |
| 1641 |
msgstr "Enfin, l'examinateur vérifiera les compétences techniques du candidat en matière de mise en paquet grâce à un questionnaire assez étoffé. Une erreur bloque le processus (sans l'interrompre définitivement), mais le temps pour répondre n'est pas limité, toute la documentation est disponible et il est possible d'essayer plusieurs fois en cas d'erreur. Le questionnaire ne se veut pas discriminatoire mais a pour seul objectif de garantir un niveau minimum de connaissances aux nouveaux contributeurs." |
| 1642 |
|
| 1643 |
msgid "This step is known as the <emphasis>Tasks & Skills</emphasis> step (T&S for short) in the examiners' jargon." |
| 1644 |
msgstr "Cette étape se nomme <foreignphrase>Tasks & Skills</foreignphrase> (T&S en abrégé) dans le jargon des examinateurs." |
| 1645 |
|
| 1646 |
msgid "<primary><emphasis>Tasks & Skills</emphasis></primary>" |
| 1647 |
msgstr "<primary><emphasis>Tasks & Skills</emphasis></primary>" |
| 1648 |
|
| 1649 |
msgid "Final Approval" |
| 1650 |
msgstr "Approbation finale" |
| 1651 |
|
| 1652 |
#, fuzzy |
| 1653 |
#| msgid "<primary>key pair</primary>" |
| 1654 |
msgid "<primary>DAM</primary>" |
| 1655 |
msgstr "<primary>biclé</primary>" |
| 1656 |
|
| 1657 |
#, fuzzy |
| 1658 |
#| msgid "<primary>package</primary><secondary>types</secondary>" |
| 1659 |
msgid "<primary>Debian</primary><secondary>Account Managers</secondary><seealso>DAM</seealso>" |
| 1660 |
msgstr "<primary>paquet</primary><secondary>types</secondary>" |
| 1661 |
|
| 1662 |
msgid "At the very last step, the whole process is reviewed by a DAM (<emphasis>Debian Account Manager</emphasis>). The DAM will review all the information about the candidate that the examiner collected, and makes the decision on whether or not to create an account on the Debian servers. In cases where extra information is required, the account creation may be delayed. Refusals are rather rare if the examiner does a good job of following the process, but they sometimes happen. They are never permanent, and the candidate is free to try again at a later time." |
| 1663 |
msgstr "La toute dernière étape est la validation du parcours par un DAM (<foreignphrase>Debian Account Manager</foreignphrase>, ou gestionnaire des comptes Debian). Il consulte les informations fournies à propos du candidat par l'examinateur et prend la décision de lui créer ou non un compte sur les serveurs Debian. Parfois, il temporisera cette création dans l'attente d'informations supplémentaires s'il le juge nécessaire. Les refus sont assez rares si l'examinateur a bien fait son travail d'encadrement, mais ils se produisent parfois. Ils ne sont jamais définitifs et le candidat est libre de retenter sa chance ultérieurement." |
| 1664 |
|
| 1665 |
msgid "The DAM's decision is authoritative and (almost) without appeal, which explains why the people in that seat have often been criticized in the past." |
| 1666 |
msgstr "La décision du DAM est souveraine et quasiment incontestable. C'est pourquoi les responsables concernés ont souvent été la cible de critiques par le passé." |
| 1667 |
|
| 1668 |
#, fuzzy |
| 1669 |
#~| msgid "The <filename>copyright</filename> file must contain information about the authors of the documents included in the package, and the related license. In our case, these are internal documents and their use is restricted to within the Falcot Corp company. The default <filename>changelog</filename> file is generally appropriate; replacing the “Initial release” with a more verbose explanation and changing the distribution from <literal>unstable</literal> to <literal>internal</literal> is enough. The <filename>control</filename> file was also updated: the <literal>Section</literal> field has been changed to <emphasis>misc</emphasis> and the <literal>Homepage</literal>, <literal>Vcs-Git</literal> and <literal>Vcs-Browser</literal> fields were removed. The <literal>Depends</literal> fields was completed with <literal>iceweasel | www-browser</literal> so as to ensure the availability of a web browser able to display the documents in the package." |
| 1670 |
#~ msgid "The <filename>copyright</filename> file must contain information about the authors of the documents included in the package, and the related license. In our case, these are internal documents and their use is restricted to within the Falcot Corp company. The default <filename>changelog</filename> file is generally appropriate; replacing the “Initial release” with a more verbose explanation and changing the distribution from <literal>unstable</literal> to <literal>internal</literal> is enough. The <filename>control</filename> file was also updated: the <literal>Section</literal> field has been changed to <emphasis>misc</emphasis> and the <literal>Homepage</literal>, <literal>Vcs-Git</literal> and <literal>Vcs-Browser</literal> fields were removed. The <literal>Depends</literal> fields was completed with <literal>firefox-esr | www-browser</literal> so as to ensure the availability of a web browser able to display the documents in the package." |
| 1671 |
#~ msgstr "Il faut mentionner dans le fichier <filename>copyright</filename> les auteurs des documents inclus dans le paquet et la licence logicielle associée. En l'occurrence, il s'agit de documents internes dont l'usage est limité à la société Falcot. Le fichier <filename>changelog</filename> par défaut convient relativement bien, et l'administrateur s'est contenté d'écrire une explication un peu plus longue que <foreignphrase>Initial release</foreignphrase> (« version initiale ») et de modifier la distribution <literal>unstable</literal> en <literal>internal</literal>. Le fichier <filename>control</filename> a lui aussi changé : le champ <literal>Section</literal> a désormais pour valeur <emphasis>misc</emphasis> et les champs Homepage, Vcs-Git et Vcs-Browser ont été supprimés. Le champ <literal>Depends</literal> a été complété par <literal>iceweasel | www-browser</literal> pour garantir la présence d'un navigateur web capable de consulter les documents ainsi diffusés." |
| 1672 |
|
| 1673 |
#~ msgid "<primary>package archive</primary>" |
| 1674 |
#~ msgstr "<primary>archive de paquets</primary>" |
| 1675 |
|
| 1676 |
#~ msgid "<primary>Debian Developer's Reference</primary>" |
| 1677 |
#~ msgstr "<primary>référence du développeur Debian</primary>" |
| 1678 |
|
| 1679 |
#~ msgid "<emphasis>QUICK LOOK</emphasis> <command>pbuilder</command>" |
| 1680 |
#~ msgstr "<emphasis>DÉCOUVERTE</emphasis> <command>pbuilder</command>" |
| 1681 |
|
| 1682 |
#~ msgid "" |
| 1683 |
#~ "\n" |
| 1684 |
#~ "This work was packaged for Debian by Raphael Hertzog <[email protected]>\n" |
| 1685 |
#~ "on Mon, 11 Apr 2011 20:46:33 +0200\n" |
| 1686 |
#~ "\n" |
| 1687 |
#~ "Copyright:\n" |
| 1688 |
#~ "\n" |
| 1689 |
#~ " Copyright (C) 2004-2011 Falcot Corp\n" |
| 1690 |
#~ "\n" |
| 1691 |
#~ "License:\n" |
| 1692 |
#~ "\n" |
| 1693 |
#~ " All rights reserved." |
| 1694 |
#~ msgstr "" |
| 1695 |
#~ "\n" |
| 1696 |
#~ "This work was packaged for Debian by:\n" |
| 1697 |
#~ "\n" |
| 1698 |
#~ " Raphael Hertzog <[email protected]> on Mon, 11 Apr 2011 20:46:33 +0200\n" |
| 1699 |
#~ "\n" |
| 1700 |
#~ "Copyright:\n" |
| 1701 |
#~ "\n" |
| 1702 |
#~ " Copyright (C) 2004-2011 Falcot SA\n" |
| 1703 |
#~ "\n" |
| 1704 |
#~ "License:\n" |
| 1705 |
#~ "\n" |
| 1706 |
#~ " All rights reserved.\n" |
| 1707 |
|
| 1708 |
#~ msgid "The <filename>menu</filename> file" |
| 1709 |
#~ msgstr "Le fichier <filename>menu</filename>" |
| 1710 |
|
| 1711 |
#~ msgid "" |
| 1712 |
#~ "\n" |
| 1713 |
#~ "?package(falcot-data):needs=X11|wm section=Help\\\n" |
| 1714 |
#~ " title=\"Internal Falcot Corp Documentation\" \\\n" |
| 1715 |
#~ " command=\"/usr/bin/x-www-browser /usr/share/falcot-data/index.html\"\n" |
| 1716 |
#~ "?package(falcot-data):needs=text section=Help\\\n" |
| 1717 |
#~ " title=\"Internal Falcot Corp Documentation\" \\\n" |
| 1718 |
#~ " command=\"/usr/bin/www-browser /usr/share/falcot-data/index.html\"" |
| 1719 |
#~ msgstr "" |
| 1720 |
#~ "\n" |
| 1721 |
#~ "?package(falcot-data):needs=X11|wm section=Help\\\n" |
| 1722 |
#~ " title=\"Documentation interne à Falcot SA\" \\\n" |
| 1723 |
#~ " command=\"/usr/bin/x-www-browser /usr/share/falcot-data/index.html\"\n" |
| 1724 |
#~ "?package(falcot-data):needs=text section=Help\\\n" |
| 1725 |
#~ " title=\"Documentation interne à Falcot SA\" \\\n" |
| 1726 |
#~ " command=\"/usr/bin/www-browser /usr/share/falcot-data/index.html\"\n" |
| 1727 |
|
| 1728 |
#~ msgid "The <literal>needs</literal> field, when set to <literal>X11|wm</literal> indicates that this entry only makes sense in a graphical interface. It will therefore only be integrated into the menus of the graphical (X11) applications and window managers (hence the <literal>wm</literal>). The <literal>section</literal> field states where in the menu the entry should be displayed. In our case, the entry will be in the Help menu. The <literal>title</literal> field contains the text that will be displayed in the menu. Finally, the <literal>command</literal> field describes the command to run when the user selects the menu entry." |
| 1729 |
#~ msgstr "Le champ <literal>needs</literal> positionné à <literal>X11|wm</literal> indique que cette entrée de menu n'a de sens que dans l'interface graphique. Elle sera donc intégrée uniquement dans les menus des applications graphiques (ou X11) et les gestionnaires de fenêtres (<literal>wm</literal> est en effet l'abréviation de <foreignphrase>window manager</foreignphrase>). Le champ <literal>section</literal> précise l'emplacement de l'entrée dans le menu. Dans notre cas, elle sera intégrée au sous-menu d'aide <foreignphrase>Help</foreignphrase>. Le champ <literal>title</literal> (titre) est le texte que les utilisateurs verront dans le menu. Enfin, le champ <literal>command</literal> décrit la commande à exécuter lorsqu'un utilisateur sélectionne cet élément de menu." |
| 1730 |
|
| 1731 |
#~ msgid "The second entry matches the first one, with slight adaptations adapted to the Linux console text mode." |
| 1732 |
#~ msgstr "La deuxième entrée est le pendant de la première, mais adaptée au mode texte d'une console Linux." |
| 1733 |
|
| 1734 |
#~ msgid "<emphasis>DEBIAN POLICY</emphasis> Menu organization" |
| 1735 |
#~ msgstr "<emphasis>CHARTE DEBIAN</emphasis> L'organisation des menus" |
| 1736 |
|
| 1737 |
#~ msgid "The Debian menus are organized in a formal structure, documented in the following text: <ulink type=\"block\" url=\"http://www.debian.org/doc/packaging-manuals/menu-policy/\" />" |
| 1738 |
#~ msgstr "L'organisation des menus Debian suit une structure précise, documentée dans le texte suivant : <ulink type=\"block\" url=\"http://www.debian.org/doc/packaging-manuals/menu-policy/\" />" |
| 1739 |
|
| 1740 |
#~ msgid "The <literal>section</literal> in a <filename>menu</filename> file should be picked from the list mentioned in this document." |
| 1741 |
#~ msgstr "Il est recommandé de choisir une section listée dans ce document pour remplir le champ <literal>section</literal> d'un fichier <filename>menu</filename>." |
| 1742 |
|
| 1743 |
#~ msgid "Simply creating the <filename>debian/menu</filename> file is enough to enable the menu in the package, since the <command>dh_installmenu</command> command is automatically invoked by <command>dh</command> during the package build process." |
| 1744 |
#~ msgstr "La simple création du fichier <filename>debian/menu</filename> est suffisante pour activer le menu dans le paquet généré car le programme <command>dh_installmenu</command> est automatiquement appelé par <command>dh</command> au cours de la fabrication du paquet." |
| 1745 |
|
| 1746 |
#~ msgid "<primary>Hess, Joey</primary>" |
| 1747 |
#~ msgstr "<primary>Hess, Joey</primary>" |
| 1748 |
|
| 1749 |
#~ msgid "<emphasis>ALTERNATIVE</emphasis> CDBS" |
| 1750 |
#~ msgstr "<emphasis>ALTERNATIVE</emphasis> CDBS" |
| 1751 |
|
| 1752 |
#~ msgid "<emphasis role=\"pkg\">cdbs</emphasis> is another approach to Debian packaging, based exclusively on an inheritance system across <filename>Makefile</filename> files." |
| 1753 |
#~ msgstr "<emphasis role=\"pkg\">cdbs</emphasis> offre une autre approche de la réalisation des paquets Debian, entièrement basée sur un système d'héritage entre fichiers <filename>Makefile</filename>." |
| 1754 |
|
| 1755 |
#~ msgid "That tool has its advocates, since it avoids duplicating the same list of <command>dh_*</command> commands in the <filename>debian/rules</filename> file. However, Debhelper version 7 introduced the <command>dh</command> command, which itself automates the appropriate sequence of calls to all the individual commands in the correct order, and CDBS has lost most of its appeal since then." |
| 1756 |
#~ msgstr "L'outil a conquis bon nombre de mainteneurs car il évitait de dupliquer toujours la même liste de commande <command>dh_*</command> dans <filename>debian/rules</filename>. Cependant, la version 7 de debhelper a introduit la commande <command>dh</command>, qui automatise l'appel en séquence (et dans le bon ordre) de toutes les commandes individuelles, et CDBS a depuis perdu son principal attrait." |