« back to all changes in this revision
Viewing changes to po4a/fr/tools.po
- browse files at revision 4
- compare with another revision
- download diff
- download tarball
- view history from revision 4
- Committer: Bazaar Package Importer
- Author(s): Lucas Nussbaum, Lucas Nussbaum, Marc 'HE' Brockschmidt
- Date: 2008-06-13 13:45:49 UTC
- mfrom: (3.1.1 intrepid)
- Revision ID: james.westby@ubuntu.com-20080613134549-dgtrirzhelf7xrfy
Tags: 3.4.0
[ Lucas Nussbaum ]
* Update Vcs-* fields after DDP's SVN restructuring. Closes: #483428.
* Fix conditions for updates from unstable to testing. Closes: #470754.
* linda has been removed. Remove section A.2.2. Closes: #483242.
* Co-maintainers are listed in the Uploaders field. Closes: #483230.
* Collaborative Maintenance: the 'global part' of debian/control
is the first paragraph, about the source package. Closes: #483231.
* debian-private archives are on master. Closes: #475531.
* Mention Debian Maintainers and the debian-maintainers package.
Closes: #483225.
* README.contrib: document that short lines are preferred.
Closes: #278267.
* build-rdeps allows to list reverse build-dependencies.
Closes: #376582.
[ Marc 'HE' Brockschmidt ]
* Replace abused <emphasis> tags with <literal> tags.
* In the same spirit, wrap all uses of stable/testing/unstable and
release codenames in <literal>
* Remove reference to upload queue on auric in section 5.6.5, auric
doesn't exist anymore.
* Fix several typesetting errors and typos noticed by Sandro Tosi,
thanks for the notes! Closes: #483223
* Update several bits about release management/testing transitions
and release-critical bugs. Closes: #483237, #456494
* Update and rewrite the porting guidelines in chapter 5, bringing
the dev-ref up to the state of porting in the year 2008. Also
fixes several wording issues, such as possible misunderstandings
about the need to rebuild uploads. Closes: #483226
* Update the instructions for uploads to the (old)stable
distributions. Emphasize the importance of contacting the SRM
team before upload. Closes: #459343
* Update instructions for package removal requests. Closes: #454216
* Clarify instructions for bug reassignment, emphasizing the
need to inform the maintainers you reassign the bug to. Also
hint to using cloned bugs to avoid re-reporting. Heavily based
on patch by Marc Haber - thanks for the work! Closes: #484806
* Clarify instructions for replacing/renaming binary packages,
pointing out that using Provides is sometimes advisable. Closes:
#467102
* Update description of the madison tool (by replacing it with a
description of the dak ls tool). Update the example while we're
at it.
* Update explanation of best practice for closing bugs, seems to
have been forgotten when everything was upgraded to use
debbugs version-tracking. Closes: #485969
* Clarify ITP instructions and emphasize our wish that people send
ITPs, explaining a few of the reasons. Thanks for the note,
Thomas. Closes: #485837
* debian/control:
+ Update Uploaders to include Lucas, Raphael and me.
+ Bump Standards-Version to 3.8.0. No changes needed!
* Update Vcs-* fields after DDP's SVN restructuring. Closes: #483428.
* Fix conditions for updates from unstable to testing. Closes: #470754.
* linda has been removed. Remove section A.2.2. Closes: #483242.
* Co-maintainers are listed in the Uploaders field. Closes: #483230.
* Collaborative Maintenance: the 'global part' of debian/control
is the first paragraph, about the source package. Closes: #483231.
* debian-private archives are on master. Closes: #475531.
* Mention Debian Maintainers and the debian-maintainers package.
Closes: #483225.
* README.contrib: document that short lines are preferred.
Closes: #278267.
* build-rdeps allows to list reverse build-dependencies.
Closes: #376582.
[ Marc 'HE' Brockschmidt ]
* Replace abused <emphasis> tags with <literal> tags.
* In the same spirit, wrap all uses of stable/testing/unstable and
release codenames in <literal>
* Remove reference to upload queue on auric in section 5.6.5, auric
doesn't exist anymore.
* Fix several typesetting errors and typos noticed by Sandro Tosi,
thanks for the notes! Closes: #483223
* Update several bits about release management/testing transitions
and release-critical bugs. Closes: #483237, #456494
* Update and rewrite the porting guidelines in chapter 5, bringing
the dev-ref up to the state of porting in the year 2008. Also
fixes several wording issues, such as possible misunderstandings
about the need to rebuild uploads. Closes: #483226
* Update the instructions for uploads to the (old)stable
distributions. Emphasize the importance of contacting the SRM
team before upload. Closes: #459343
* Update instructions for package removal requests. Closes: #454216
* Clarify instructions for bug reassignment, emphasizing the
need to inform the maintainers you reassign the bug to. Also
hint to using cloned bugs to avoid re-reporting. Heavily based
on patch by Marc Haber - thanks for the work! Closes: #484806
* Clarify instructions for replacing/renaming binary packages,
pointing out that using Provides is sometimes advisable. Closes:
#467102
* Update description of the madison tool (by replacing it with a
description of the dak ls tool). Update the example while we're
at it.
* Update explanation of best practice for closing bugs, seems to
have been forgotten when everything was upgraded to use
debbugs version-tracking. Closes: #485969
* Clarify ITP instructions and emphasize our wish that people send
ITPs, explaining a few of the reasons. Thanks for the note,
Thomas. Closes: #485837
* debian/control:
+ Update Uploaders to include Lucas, Raphael and me.
+ Bump Standards-Version to 3.8.0. No changes needed!
- files added:
- best-pkging-practices.dbk
- po4a
- po4a/fr
- po4a/ja
- po4a/po
- files removed:
- ChangeLog
- files modified:
- Makefile
added
removed
po4a/fr/tools.po
1
# SOME DESCRIPTIVE TITLE
2
# Copyright (C) 2007 Free Software Foundation, Inc.
3
# <>, 2007.
4
# , fuzzy
5
#
6
#
7
msgid ""
8
msgstr ""
9
"Project-Id-Version: PACKAGE VERSION\n"
10
"Report-Msgid-Bugs-To: \n"
11
"POT-Creation-Date: 2007-07-01 21:16+0000\n"
12
"PO-Revision-Date: 2007-07-01 23:19+0000\n"
13
"Last-Translator: <>\n"
14
"Language-Team: \n"
15
"MIME-Version: 1.0\n"
16
"Content-Type: text/plain; charset=UTF-8\n"
17
"Content-Transfer-Encoding: "
18
19
# type: Content of: <appendix><title>
20
#: tools.dbk:7
21
msgid "Overview of Debian Maintainer Tools"
22
msgstr "Aperçu des outils du responsable Debian"
23
24
# type: Content of: <appendix><para>
25
#: tools.dbk:9
26
msgid ""
27
"This section contains a rough overview of the tools available to "
28
"maintainers. The following is by no means complete or definitive, but just "
29
"a guide to some of the more popular tools."
30
msgstr "Cette section contient un aperçu rapide des outils dont dispose le"
31
"responsable. Cette liste n'est ni complète, ni définitive, il s'agit"
32
"juste d'un guide des outils les plus utilisés."
33
34
# type: Content of: <appendix><para>
35
#: tools.dbk:14
36
msgid ""
37
"Debian maintainer tools are meant to aid developers and free their time for "
38
"critical tasks. As Larry Wall says, there's more than one way to do it."
39
msgstr "Les outils du responsable Debian sont destinés à aider les responsables"
40
"et libérer leur temps pour des tâches plus cruciales. Comme le dit Larry"
41
"Wall, il y a plus d'une manière de le faire."
42
43
# type: Content of: <appendix><para>
44
#: tools.dbk:18
45
msgid ""
46
"Some people prefer to use high-level package maintenance tools and some do "
47
"not. Debian is officially agnostic on this issue; any tool which gets the "
48
"job done is fine. Therefore, this section is not meant to stipulate to "
49
"anyone which tools they should use or how they should go about their duties "
50
"of maintainership. Nor is it meant to endorse any particular tool to the "
51
"exclusion of a competing tool."
52
msgstr "Certaines personnes préfèrent utiliser des outils de haut niveau,"
53
"d'autres pas. Debian n'a pas de position officielle sur la"
54
"question ; tout outil conviendra du moment qu'il fait le"
55
"boulot. C'est pourquoi cette section n'a pas été conçue pour indiquer à"
56
"chacun quel outil il doit utiliser ou comment il devrait faire pour"
57
"gérer sa charge de responsable Debian. Elle n'est pas non plus destinée"
58
"à favoriser l'utilisation d'un outil aux dépens d'un autre."
59
60
# type: Content of: <appendix><para>
61
#: tools.dbk:26
62
msgid ""
63
"Most of the descriptions of these packages come from the actual package "
64
"descriptions themselves. Further information can be found in the package "
65
"documentation itself. You can also see more info with the command "
66
"<command>apt-cache show <package-name></command>."
67
msgstr "La plupart des descriptions de ces outils proviennent des descriptions"
68
"de leurs paquets. Vous trouverez plus d'informations dans les"
69
"documentations de ces paquets. Vous pouvez aussi obtenir plus"
70
"d'informations avec la commande <literal>apt-cache show"
71
"<nom_paquet></literal>."
72
73
# type: Content of: <appendix><section><title>
74
#: tools.dbk:32
75
msgid "Core tools"
76
msgstr "Outils de base"
77
78
# type: Content of: <appendix><section><para>
79
#: tools.dbk:34
80
msgid "The following tools are pretty much required for any maintainer."
81
msgstr "Les outils suivants sont pratiquement nécessaires à tout responsable."
82
83
# type: Content of: <appendix><section><section><para>
84
#: tools.dbk:39
85
msgid ""
86
"<systemitem role=\"package\">dpkg-dev</systemitem> contains the tools "
87
"(including <command>dpkg-source</command>) required to unpack, build, and "
88
"upload Debian source packages. These utilities contain the fundamental, low-"
89
"level functionality required to create and manipulate packages; as such, "
90
"they are essential for any Debian maintainer."
91
msgstr ""
92
93
# type: Content of: <appendix><section><section><para>
94
#: tools.dbk:50
95
msgid ""
96
"<systemitem role=\"package\">debconf</systemitem> provides a consistent "
97
"interface to configuring packages interactively. It is user interface "
98
"independent, allowing end-users to configure packages with a text-only "
99
"interface, an HTML interface, or a dialog interface. New interfaces can be "
100
"added as modules."
101
msgstr ""
102
103
# type: Content of: <appendix><section><section><para>
104
#: tools.dbk:56
105
msgid ""
106
"You can find documentation for this package in the <systemitem role=\"package"
107
"\">debconf-doc</systemitem> package."
108
msgstr ""
109
110
# type: Content of: <appendix><section><section><para>
111
#: tools.dbk:60
112
msgid ""
113
"Many feel that this system should be used for all packages which require "
114
"interactive configuration; see <xref linkend=\"bpp-config-mgmt\"/> . "
115
"<systemitem role=\"package\">debconf</systemitem> is not currently required "
116
"by Debian Policy, but that may change in the future."
117
msgstr ""
118
119
# type: Content of: <appendix><section><section><para>
120
#: tools.dbk:70
121
msgid ""
122
"<systemitem role=\"package\">fakeroot</systemitem> simulates root "
123
"privileges. This enables you to build packages without being root (packages "
124
"usually want to install files with root ownership). If you have <systemitem "
125
"role=\"package\">fakeroot</systemitem> installed, you can build packages as "
126
"a regular user: <literal>dpkg-buildpackage -rfakeroot</literal>."
127
msgstr ""
128
129
# type: Content of: <appendix><section><title>
130
#: tools.dbk:81
131
msgid "Package lint tools"
132
msgstr ""
133
134
# type: Content of: <appendix><section><para>
135
#: tools.dbk:83
136
msgid ""
137
"According to the Free On-line Dictionary of Computing (FOLDOC), `lint' is a "
138
"Unix C language processor which carries out more thorough checks on the code "
139
"than is usual with C compilers. Package lint tools help package maintainers "
140
"by automatically finding common problems and policy violations in their "
141
"packages."
142
msgstr ""
143
144
# type: Content of: <appendix><section><section><para>
145
#: tools.dbk:91
146
msgid ""
147
"<systemitem role=\"package\">lintian</systemitem> dissects Debian packages "
148
"and emits information about bugs and policy violations. It contains "
149
"automated checks for many aspects of Debian policy as well as some checks "
150
"for common errors."
151
msgstr ""
152
153
# type: Content of: <appendix><section><section><para>
154
#: tools.dbk:97
155
msgid ""
156
"You should periodically get the newest <systemitem role=\"package\">lintian</"
157
"systemitem> from `unstable' and check over all your packages. Notice that "
158
"the <literal>-i</literal> option provides detailed explanations of what each "
159
"error or warning means, what its basis in Policy is, and commonly how you "
160
"can fix the problem."
161
msgstr ""
162
163
# type: Content of: <appendix><section><section><para>
164
#: tools.dbk:104
165
msgid ""
166
"Refer to <xref linkend=\"sanitycheck\"/> for more information on how and "
167
"when to use Lintian."
168
msgstr ""
169
170
# type: Content of: <appendix><section><section><para>
171
#: tools.dbk:108
172
msgid ""
173
"You can also see a summary of all problems reported by Lintian on your "
174
"packages at <ulink url=\"&url-lintian;\"></ulink>. These reports contain "
175
"the latest <command>lintian</command> output for the whole development "
176
"distribution (unstable)."
177
msgstr ""
178
179
# type: Content of: <appendix><section><section><para>
180
#: tools.dbk:118
181
msgid ""
182
"<systemitem role=\"package\">linda</systemitem> is another package linter. "
183
"It is similar to <systemitem role=\"package\">lintian</systemitem> but has a "
184
"different set of checks. Its written in Python rather than Perl."
185
msgstr ""
186
187
# type: Content of: <appendix><section><section><para>
188
#: tools.dbk:127
189
msgid ""
190
"<command>debdiff</command> (from the <systemitem role=\"package"
191
"\">devscripts</systemitem> package, <xref linkend=\"devscripts\"/> ) "
192
"compares file lists and control files of two packages. It is a simple "
193
"regression test, as it will help you notice if the number of binary packages "
194
"has changed since the last upload, or if something has changed in the "
195
"control file. Of course, some of the changes it reports will be all right, "
196
"but it can help you prevent various accidents."
197
msgstr ""
198
199
# type: Content of: <appendix><section><section><para>
200
#: tools.dbk:136
201
msgid "You can run it over a pair of binary packages:"
202
msgstr ""
203
204
# type: Content of: <appendix><section><section><screen>
205
#: tools.dbk:139
206
#, no-wrap
207
msgid "debdiff package_1-1_arch.deb package_2-1_arch.deb"
208
msgstr ""
209
210
# type: Content of: <appendix><section><section><para>
211
#: tools.dbk:142
212
msgid "Or even a pair of changes files:"
213
msgstr ""
214
215
# type: Content of: <appendix><section><section><screen>
216
#: tools.dbk:145
217
#, no-wrap
218
msgid "debdiff package_1-1_arch.changes package_2-1_arch.changes"
219
msgstr ""
220
221
# type: Content of: <appendix><section><section><para>
222
#: tools.dbk:148
223
msgid ""
224
"For more information please see <citerefentry> <refentrytitle>debdiff</"
225
"refentrytitle> <manvolnum>1</manvolnum> </citerefentry>."
226
msgstr ""
227
228
# type: Content of: <appendix><section><title>
229
#: tools.dbk:157
230
msgid "Helpers for <filename>debian/rules</filename>"
231
msgstr ""
232
233
# type: Content of: <appendix><section><para>
234
#: tools.dbk:159
235
msgid ""
236
"Package building tools make the process of writing <filename>debian/rules</"
237
"filename> files easier. See <xref linkend=\"helper-scripts\"/> for more "
238
"information about why these might or might not be desired."
239
msgstr ""
240
241
# type: Content of: <appendix><section><section><para>
242
#: tools.dbk:167
243
msgid ""
244
"<systemitem role=\"package\">debhelper</systemitem> is a collection of "
245
"programs which can be used in <filename>debian/rules</filename> to automate "
246
"common tasks related to building binary Debian packages. <systemitem role="
247
"\"package\">debhelper</systemitem> includes programs to install various "
248
"files into your package, compress files, fix file permissions, and integrate "
249
"your package with the Debian menu system."
250
msgstr ""
251
252
# type: Content of: <appendix><section><section><para>
253
#: tools.dbk:175
254
msgid ""
255
"Unlike some approaches, <systemitem role=\"package\">debhelper</systemitem> "
256
"is broken into several small, simple commands which act in a consistent "
257
"manner. As such, it allows more fine-grained control than some of the other "
258
"debian/rules tools."
259
msgstr ""
260
261
# type: Content of: <appendix><section><section><para>
262
#: tools.dbk:181
263
msgid ""
264
"There are a number of little <systemitem role=\"package\">debhelper</"
265
"systemitem> add-on packages, too transient to document. You can see the "
266
"list of most of them by doing <literal>apt-cache search ^dh-</literal>."
267
msgstr ""
268
269
# type: Content of: <appendix><section><section><para>
270
#: tools.dbk:190
271
msgid ""
272
"<systemitem role=\"package\">debmake</systemitem>, a precursor to "
273
"<systemitem role=\"package\">debhelper</systemitem>, is a more coarse-"
274
"grained <filename>debian/rules</filename> assistant. It includes two main "
275
"programs: <command>deb-make</command>, which can be used to help a "
276
"maintainer convert a regular (non-Debian) source archive into a Debian "
277
"source package; and <command>debstd</command>, which incorporates in one big "
278
"shot the same sort of automated functions that one finds in <systemitem role="
279
"\"package\">debhelper</systemitem>."
280
msgstr ""
281
282
# type: Content of: <appendix><section><section><para>
283
#: tools.dbk:200
284
msgid ""
285
"The consensus is that <systemitem role=\"package\">debmake</systemitem> is "
286
"now deprecated in favor of <systemitem role=\"package\">debhelper</"
287
"systemitem>. It is a bug to use <systemitem role=\"package\">debmake</"
288
"systemitem> in new packages. New packages using <systemitem role=\"package"
289
"\">debmake</systemitem> will be rejected from the archive."
290
msgstr ""
291
292
# type: Content of: <appendix><section><section><para>
293
#: tools.dbk:211
294
msgid ""
295
"The <systemitem role=\"package\">dh-make</systemitem> package contains "
296
"<command>dh_make</command>, a program that creates a skeleton of files "
297
"necessary to build a Debian package out of a source tree. As the name "
298
"suggests, <command>dh_make</command> is a rewrite of <systemitem role="
299
"\"package\">debmake</systemitem> and its template files use dh_* programs "
300
"from <systemitem role=\"package\">debhelper</systemitem>."
301
msgstr ""
302
303
# type: Content of: <appendix><section><section><para>
304
#: tools.dbk:219
305
msgid ""
306
"While the rules files generated by <command>dh_make</command> are in general "
307
"a sufficient basis for a working package, they are still just the "
308
"groundwork: the burden still lies on the maintainer to finely tune the "
309
"generated files and make the package entirely functional and Policy-"
310
"compliant."
311
msgstr ""
312
313
# type: Content of: <appendix><section><section><para>
314
#: tools.dbk:229
315
msgid ""
316
"<systemitem role=\"package\">yada</systemitem> is another packaging helper "
317
"tool. It uses a <filename>debian/packages</filename> file to auto-generate "
318
"<filename>debian/rules</filename> and other necessary files in the "
319
"<filename>debian/</filename> subdirectory. The <filename>debian/packages</"
320
"filename> file contains instruction to build packages and there is no need "
321
"to create any <filename>Makefile</filename> files. There is possibility to "
322
"use macro engine similar to the one used in SPECS files from RPM source "
323
"packages."
324
msgstr ""
325
326
# type: Content of: <appendix><section><section><para>
327
#: tools.dbk:239
328
msgid ""
329
"For more informations see <literal><ulink url=\"http://yada.alioth.debian."
330
"org/\">YADA site</ulink></literal>."
331
msgstr ""
332
333
# type: Content of: <appendix><section><section><para>
334
#: tools.dbk:247
335
msgid ""
336
"<systemitem role=\"package\">equivs</systemitem> is another package for "
337
"making packages. It is often suggested for local use if you need to make a "
338
"package simply to fulfill dependencies. It is also sometimes used when "
339
"making ``meta-packages'', which are packages whose only purpose is to depend "
340
"on other packages."
341
msgstr ""
342
343
# type: Content of: <appendix><section><title>
344
#: tools.dbk:258
345
msgid "Package builders"
346
msgstr ""
347
348
# type: Content of: <appendix><section><para>
349
#: tools.dbk:260
350
msgid ""
351
"The following packages help with the package building process, general "
352
"driving <command>dpkg-buildpackage</command> as well as handling supporting "
353
"tasks."
354
msgstr ""
355
356
# type: Content of: <appendix><section><section><para>
357
#: tools.dbk:266
358
msgid ""
359
"<systemitem role=\"package\">cvs-buildpackage</systemitem> provides the "
360
"capability to inject or import Debian source packages into a CVS repository, "
361
"build a Debian package from the CVS repository, and helps in integrating "
362
"upstream changes into the repository."
363
msgstr ""
364
365
# type: Content of: <appendix><section><section><para>
366
#: tools.dbk:272
367
msgid ""
368
"These utilities provide an infrastructure to facilitate the use of CVS by "
369
"Debian maintainers. This allows one to keep separate CVS branches of a "
370
"package for <emphasis>stable</emphasis>, <emphasis>unstable</emphasis> and "
371
"possibly <emphasis>experimental</emphasis> distributions, along with the "
372
"other benefits of a version control system."
373
msgstr ""
374
375
# type: Content of: <appendix><section><section><para>
376
#: tools.dbk:283
377
msgid ""
378
"The <systemitem role=\"package\">debootstrap</systemitem> package and script "
379
"allows you to bootstrap a Debian base system into any part of your "
380
"filesystem. By base system, we mean the bare minimum of packages required "
381
"to operate and install the rest of the system."
382
msgstr ""
383
384
# type: Content of: <appendix><section><section><para>
385
#: tools.dbk:289
386
msgid ""
387
"Having a system like this can be useful in many ways. For instance, you can "
388
"<command>chroot</command> into it if you want to test your build "
389
"dependencies. Or you can test how your package behaves when installed into "
390
"a bare base system. Chroot builders use this package; see below."
391
msgstr ""
392
393
# type: Content of: <appendix><section><section><para>
394
#: tools.dbk:299
395
msgid ""
396
"<systemitem role=\"package\">pbuilder</systemitem> constructs a chrooted "
397
"system, and builds a package inside the chroot. It is very useful to check "
398
"that a package's build-dependencies are correct, and to be sure that "
399
"unnecessary and wrong build dependencies will not exist in the resulting "
400
"package."
401
msgstr ""
402
403
# type: Content of: <appendix><section><section><para>
404
#: tools.dbk:305
405
msgid ""
406
"A related package is <systemitem role=\"package\">pbuilder-uml</systemitem>, "
407
"which goes even further by doing the build within a User Mode Linux "
408
"environment."
409
msgstr ""
410
411
# type: Content of: <appendix><section><section><para>
412
#: tools.dbk:314
413
msgid ""
414
"<systemitem role=\"package\">sbuild</systemitem> is another automated "
415
"builder. It can use chrooted environments as well. It can be used stand-"
416
"alone, or as part of a networked, distributed build environment. As the "
417
"latter, it is part of the system used by porters to build binary packages "
418
"for all the available architectures. See <xref linkend=\"buildd\"/> for "
419
"more information, and <ulink url=\"&url-buildd;\"></ulink> to see the system "
420
"in action."
421
msgstr ""
422
423
# type: Content of: <appendix><section><title>
424
#: tools.dbk:326
425
msgid "Package uploaders"
426
msgstr ""
427
428
# type: Content of: <appendix><section><para>
429
#: tools.dbk:328
430
msgid ""
431
"The following packages help automate or simplify the process of uploading "
432
"packages into the official archive."
433
msgstr ""
434
435
# type: Content of: <appendix><section><section><para>
436
#: tools.dbk:334
437
msgid ""
438
"<systemitem role=\"package\">dupload</systemitem> is a package and a script "
439
"to automatically upload Debian packages to the Debian archive, to log the "
440
"upload, and to send mail about the upload of a package. You can configure "
441
"it for new upload locations or methods."
442
msgstr ""
443
444
# type: Content of: <appendix><section><section><para>
445
#: tools.dbk:344
446
msgid ""
447
"The <systemitem role=\"package\">dput</systemitem> package and script does "
448
"much the same thing as <systemitem role=\"package\">dupload</systemitem>, "
449
"but in a different way. It has some features over <systemitem role=\"package"
450
"\">dupload</systemitem>, such as the ability to check the GnuPG signature "
451
"and checksums before uploading, and the possibility of running "
452
"<command>dinstall</command> in dry-run mode after the upload."
453
msgstr ""
454
455
# type: Content of: <appendix><section><section><para>
456
#: tools.dbk:356
457
msgid ""
458
"The <systemitem role=\"package\">dcut</systemitem> script (part of the "
459
"package <xref linkend=\"dput\"/> ) helps in removing files from the ftp "
460
"upload directory."
461
msgstr ""
462
463
# type: Content of: <appendix><section><title>
464
#: tools.dbk:364
465
msgid "Maintenance automation"
466
msgstr ""
467
468
# type: Content of: <appendix><section><para>
469
#: tools.dbk:366
470
msgid ""
471
"The following tools help automate different maintenance tasks, from adding "
472
"changelog entries or signature lines and looking up bugs in Emacs to making "
473
"use of the newest and official <filename>config.sub</filename>."
474
msgstr ""
475
476
# type: Content of: <appendix><section><section><para>
477
#: tools.dbk:373
478
msgid ""
479
"<systemitem role=\"package\">devscripts</systemitem> is a package containing "
480
"wrappers and tools which are very helpful for maintaining your Debian "
481
"packages. Example scripts include <command>debchange</command> and "
482
"<command>dch</command>, which manipulate your <filename>debian/changelog</"
483
"filename> file from the command-line, and <command>debuild</command>, which "
484
"is a wrapper around <command>dpkg-buildpackage</command>. The <command>bts</"
485
"command> utility is also very helpful to update the state of bug reports on "
486
"the command line. <command>uscan</command> can be used to watch for new "
487
"upstream versions of your packages. <command>debrsign</command> can be used "
488
"to remotely sign a package prior to upload, which is nice when the machine "
489
"you build the package on is different from where your GPG keys are."
490
msgstr ""
491
492
# type: Content of: <appendix><section><section><para>
493
#: tools.dbk:387
494
msgid ""
495
"See the <citerefentry> <refentrytitle>devscripts</refentrytitle> "
496
"<manvolnum>1</manvolnum> </citerefentry> manual page for a complete list of "
497
"available scripts."
498
msgstr ""
499
500
# type: Content of: <appendix><section><section><para>
501
#: tools.dbk:396
502
msgid ""
503
"<systemitem role=\"package\">autotools-dev</systemitem> contains best "
504
"practices for people who maintain packages which use <command>autoconf</"
505
"command> and/or <command>automake</command>. Also contains canonical "
506
"<filename>config.sub</filename> and <filename>config.guess</filename> files "
507
"which are known to work on all Debian ports."
508
msgstr ""
509
510
# type: Content of: <appendix><section><section><para>
511
#: tools.dbk:407
512
msgid ""
513
"<command>dpkg-repack</command> creates Debian package file out of a package "
514
"that has already been installed. If any changes have been made to the "
515
"package while it was unpacked (e.g., files in <filename>/etc</filename> were "
516
"modified), the new package will inherit the changes."
517
msgstr ""
518
519
# type: Content of: <appendix><section><section><para>
520
#: tools.dbk:413
521
msgid ""
522
"This utility can make it easy to copy packages from one computer to another, "
523
"or to recreate packages which are installed on your system but no longer "
524
"available elsewhere, or to save the current state of a package before you "
525
"upgrade it."
526
msgstr ""
527
528
# type: Content of: <appendix><section><section><para>
529
#: tools.dbk:422
530
msgid ""
531
"<command>alien</command> converts binary packages between various packaging "
532
"formats, including Debian, RPM (RedHat), LSB (Linux Standard Base), Solaris, "
533
"and Slackware packages."
534
msgstr ""
535
536
# type: Content of: <appendix><section><section><para>
537
#: tools.dbk:431
538
msgid ""
539
"<command>debsums</command> checks installed packages against their MD5 "
540
"sums. Note that not all packages have MD5 sums, since they aren't required "
541
"by Policy."
542
msgstr ""
543
544
# type: Content of: <appendix><section><section><para>
545
#: tools.dbk:439
546
msgid ""
547
"<systemitem role=\"package\">dpkg-dev-el</systemitem> is an Emacs lisp "
548
"package which provides assistance when editing some of the files in the "
549
"<filename>debian</filename> directory of your package. For instance, there "
550
"are handy functions for listing a package's current bugs, and for finalizing "
551
"the latest entry in a <filename>debian/changelog</filename> file."
552
msgstr ""
553
554
# type: Content of: <appendix><section><section><para>
555
#: tools.dbk:450
556
msgid ""
557
"<command>dpkg-depcheck</command> (from the <systemitem role=\"package"
558
"\">devscripts</systemitem> package, <xref linkend=\"devscripts\"/> ) runs a "
559
"command under <command>strace</command> to determine all the packages that "
560
"were used by the said command."
561
msgstr ""
562
563
# type: Content of: <appendix><section><section><para>
564
#: tools.dbk:456
565
msgid ""
566
"For Debian packages, this is useful when you have to compose a "
567
"<literal>Build-Depends</literal> line for your new package: running the "
568
"build process through <command>dpkg-depcheck</command> will provide you with "
569
"a good first approximation of the build-dependencies. For example:"
570
msgstr ""
571
572
# type: Content of: <appendix><section><section><screen>
573
#: tools.dbk:462
574
#, no-wrap
575
msgid "dpkg-depcheck -b debian/rules build"
576
msgstr ""
577
578
# type: Content of: <appendix><section><section><para>
579
#: tools.dbk:465
580
msgid ""
581
"<command>dpkg-depcheck</command> can also be used to check for run-time "
582
"dependencies, especially if your package uses exec(2) to run other programs."
583
msgstr ""
584
585
# type: Content of: <appendix><section><section><para>
586
#: tools.dbk:469
587
msgid ""
588
"For more information please see <citerefentry> <refentrytitle>dpkg-depcheck</"
589
"refentrytitle> <manvolnum>1</manvolnum> </citerefentry>."
590
msgstr ""
591
592
# type: Content of: <appendix><section><title>
593
#: tools.dbk:478
594
msgid "Porting tools"
595
msgstr ""
596
597
# type: Content of: <appendix><section><para>
598
#: tools.dbk:480
599
msgid "The following tools are helpful for porters and for cross-compilation."
600
msgstr ""
601
602
# type: Content of: <appendix><section><section><para>
603
#: tools.dbk:485
604
msgid ""
605
"<systemitem role=\"package\">quinn-diff</systemitem> is used to locate the "
606
"differences from one architecture to another. For instance, it could tell "
607
"you which packages need to be ported for architecture <replaceable>Y</"
608
"replaceable>, based on architecture <replaceable>X</replaceable>."
609
msgstr ""
610
611
# type: Content of: <appendix><section><section><para>
612
#: tools.dbk:495
613
msgid ""
614
"<systemitem role=\"package\">dpkg-cross</systemitem> is a tool for "
615
"installing libraries and headers for cross-compiling in a way similar to "
616
"<systemitem role=\"package\">dpkg</systemitem>. Furthermore, the "
617
"functionality of <command>dpkg-buildpackage</command> and <command>dpkg-"
618
"shlibdeps</command> is enhanced to support cross-compiling."
619
msgstr ""
620
621
# type: Content of: <appendix><section><title>
622
#: tools.dbk:506
623
msgid "Documentation and information"
624
msgstr ""
625
626
# type: Content of: <appendix><section><para>
627
#: tools.dbk:508
628
msgid ""
629
"The following packages provide information for maintainers or help with "
630
"building documentation."
631
msgstr ""
632
633
# type: Content of: <appendix><section><section><para>
634
#: tools.dbk:514
635
msgid ""
636
"<systemitem role=\"package\">debiandoc-sgml</systemitem> provides the "
637
"DebianDoc SGML DTD, which is commonly used for Debian documentation. This "
638
"manual, for instance, is written in DebianDoc. It also provides scripts for "
639
"building and styling the source to various output formats."
640
msgstr ""
641
642
# type: Content of: <appendix><section><section><para>
643
#: tools.dbk:520
644
msgid ""
645
"Documentation for the DTD can be found in the <systemitem role=\"package"
646
"\">debiandoc-sgml-doc</systemitem> package."
647
msgstr ""
648
649
# type: Content of: <appendix><section><section><para>
650
#: tools.dbk:544
651
msgid ""
652
"Contains the public GPG and PGP keys of Debian developers. See <xref "
653
"linkend=\"key-maint\"/> and the package documentation for more information."
654
msgstr ""
655
656
# type: Content of: <appendix><section><section><para>
657
#: tools.dbk:552
658
msgid ""
659
"<systemitem role=\"package\">debview</systemitem> provides an Emacs mode for "
660
"viewing Debian binary packages. This lets you examine a package without "
661
"unpacking it."
662
msgstr ""
663
Loggerhead is a web-based interface for Breezy
Version: 2.0.1