This file is indexed.

/usr/share/doc/live-manual/html/customizing-package-installation.it.html is in live-manual-html 1:3.0~a9-1ubuntu1.

This file is owned by root:root, with mode 0o644.

The actual contents of the file can be viewed below.

  1
  2
  3
  4
  5
  6
  7
  8
  9
 10
 11
 12
 13
 14
 15
 16
 17
 18
 19
 20
 21
 22
 23
 24
 25
 26
 27
 28
 29
 30
 31
 32
 33
 34
 35
 36
 37
 38
 39
 40
 41
 42
 43
 44
 45
 46
 47
 48
 49
 50
 51
 52
 53
 54
 55
 56
 57
 58
 59
 60
 61
 62
 63
 64
 65
 66
 67
 68
 69
 70
 71
 72
 73
 74
 75
 76
 77
 78
 79
 80
 81
 82
 83
 84
 85
 86
 87
 88
 89
 90
 91
 92
 93
 94
 95
 96
 97
 98
 99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
502
503
504
505
506
507
508
509
510
511
512
513
514
515
516
517
518
519
520
521
522
523
524
525
526
527
528
529
530
531
532
533
534
535
536
537
538
539
540
541
542
543
544
545
546
547
548
549
550
551
552
553
554
555
556
557
558
559
560
561
562
563
564
565
566
567
568
569
570
571
572
573
574
575
576
577
578
579
580
581
582
583
584
585
586
587
588
589
590
591
592
593
594
595
596
597
598
599
600
601
602
603
604
605
606
607
608
609
610
611
612
613
614
615
616
617
618
619
620
621
622
623
624
625
626
627
628
629
630
631
632
633
634
635
636
637
638
639
640
641
642
643
644
645
646
647
648
649
650
651
652
653
654
655
656
657
658
659
660
661
662
663
664
665
666
667
668
669
670
671
672
673
674
675
676
677
678
679
680
681
682
683
684
685
686
687
688
689
690
691
692
693
694
695
696
697
698
699
700
701
702
703
704
705
706
707
708
709
710
711
712
713
714
715
716
717
718
719
720
721
722
723
724
725
726
727
728
729
730
731
732
733
734
735
736
737
738
739
740
741
742
743
744
745
746
747
748
749
750
751
752
753
754
755
756
757
758
759
760
761
762
763
764
765
766
767
768
769
770
771
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">

<head>
  <title>
    customizing-package-installation -
    Manuale di Debian Live
  </title>
<meta http-equiv="Content-Type" content="text/html;charset=utf-8" />
  <meta name="dc.title" content="Manuale di Debian Live" />
  <meta name="dc.author" content="Debian Live Project &#60;debian-live@lists.debian.org&#62;" />
  <meta name="dc.publisher" content="Debian Live Project &#60;debian-live@lists.debian.org&#62;" />
  <meta name="dc.date" content="2011-12-04"  />
  <meta name="dc.rights" content="Copyright (C) 2006-2011 Debian Live Project;&#60;br&#62; License: Questo programma &#232; software libero: &#232; possibile ridistribuirlo e modificarlo secondo i termini della GNU General Public License come pubblicata dalla Free Software Foundation, sia la versione 3 della licenza o (a scelta) una versione successiva.&#60;br&#62;&#60;br&#62;Questo programma &#232; distribuito nella speranza che possa essere utile, ma SENZA ALCUNA GARANZIA, nemmeno la garanzia implicita di COMMERCIABILIT&#192; o IDONEIT&#192; PER UN PARTICOLARE SCOPO. Vedere la GNU General Public License per ulteriori dettagli.&#60;br&#62;&#60;br&#62;Si dovrebbe aver ricevuto una copia della GNU General Public License con questo programma. In caso contrario, vedere http://www.gnu.org/licenses/. &#60;br&#62;&#60;br&#62;Il testo completo della GNU General Public License pu&#242; essere trovato nel file /usr/share/common-licenses/GPL-3." />

  <meta name="generator" content="SiSU 3.1.9 of 2011w51/1 (2011-12-19) (n*x and Ruby!)" />
    <link rel="generator" href="http://www.sisudoc.org/" />
  <link rel="shortcut icon" href="../_sisu/image/rb7.ico" />

  <link rel="stylesheet" href="../_sisu/css/html.css" type="text/css" />
</head>
<body bgcolor="#ffffff" text="#000000" link="#003090" lang="en" xml:lang="en">
<a name="top" id="top"></a>
<a name="up" id="up"></a>
<a name="start" id="start"></a><table summary="segment navigation band with banner" bgcolor="#ffffff" width="100%"><tr>
<td width="20%" align="left">
<table summary="band" border="0" cellpadding="3" cellspacing="0"><tr><td align="left" bgcolor="#ffffff"><a href="http://live.debian.net/" target="_top"><img border="0" src="../_sisu/image/debian_home.png" alt="Debian --&gt;" /></a></td></tr>
</table>
</td>
<td width="75%" align="center">
  
<table summary="segment navigation available documents types: toc,doc,pdf,concordance" border="0" cellpadding="3" cellspacing="0">
<tr>
<td align="center" bgcolor="#ffffff">
  <td align="center" bgcolor="#ffffff">
  <a href="sisu_manifest.it.html" target="_top" >
      <font face="verdana, arial, georgia, tahoma, sans-serif, helvetica, times, roman" size="2">
    [&nbsp;document&nbsp;manifest&nbsp;]
  </font> 
  </a>
</td>
  
</tr></table>
</td>
<td width="5%" align="right">
  <table summary="segment navigation pre/next" border="0" cellpadding="3" cellspacing="0">
<tr>
<td align="center" bgcolor="#ffffff">
  <a href="customization-overview.it.html" target="_top" >
    <img border="0" width="22" height="22" src="../_sisu/image_sys/arrow_prev_red.png" alt="&lt;&lt;&nbsp;previous" />
  </a>
</td>
<td align="center" bgcolor="#ffffff">
  <a href="toc.it.html" target="_top" >
    <img border="0" width="22" height="22" src="../_sisu/image_sys/arrow_up_red.png" alt="TOC" />
  </a>
</td>
<td align="center" bgcolor="#ffffff">
  <a href="customizing-contents.it.html" target="_top" >
    <img border="0" width="22" height="22" src="../_sisu/image_sys/arrow_next_red.png" alt="next&nbsp;&gt;&gt;" />
  </a>
</td>
<td>
</td></tr>
</table>
</td></tr>
</table>
<table summary="segment hidden control pre and next" width="100%" border="0" cellpadding="0" bgcolor=#eeeeee align="center">
<tr><td align="left">
  <a href="customization-overview.it.html" target="_top" >
    <img border="0" width="100%" height="20" src="../_sisu/image_sys/dot_white.png" alt="&lt;" />
  </a>
</td>
<td align="center">
  <a href="toc.it.html" target="_top" >
    <img border="0" width="100%" height="20" src="../_sisu/image_sys/dot_white.png" alt="&#094;" />
  </a>
</td>
<td align="right">
  <a href="customizing-contents.it.html" target="_top" >
    <img border="0" width="100%" height="20" src="../_sisu/image_sys/dot_white.png" alt="&gt;" />
  </a>
</td></tr>
</table><div class="content">
<h1 class="tiny">
    Manuale di Debian Live
  </h1>
</div><div class="content">
<h2 class="tiny">
    Utente
  </h2>
</div><div class="content"><div class="substance">
  <label class="ocn"><a name="339" href="#339" class="lnkocn">339</a></label>
  <h1 class="norm" id="o339"><a name="339"></a>
    8. Personalizzare l'installazione dei  pacchetti
  </h1>
</div><div class="substance">
  <label class="ocn"><a name="340" href="#340" class="lnkocn">340</a></label>
  <p class="i0" id="o340">
    Probabilmente la personalizzazione basilare di un sistema Debian Live &egrave; la  scelta dei pacchetti da includere nell'immagine. Questo capitolo vi guider&agrave;  tra le varie opzioni in fase di costruzione per personalizzare  l'installazione dei pacchetti di <i>live-build</i>. Le ampie scelte che influenzano  quali pacchetti siano disponibili da installare nell'immagine sono le aree  di distribuzione e archivio. Per essere sicuri di avere una ragionevole  velocit&agrave; di scaricamento, dovreste usare un mirror a voi vicino. Si possono  inoltre aggiungere i propri repository per pacchetti di backport,  sperimentali o personalizzati, o aggiungere i pacchetti direttamente come  file. &Egrave; possibile definire una propria lista di pacchetti da includere,  usarne una predefinita di <i>live-build</i>, usare task di <tt>tasksel</tt>, o una  combinazione di tutti e tre. Infine una serie di opzioni fornisce un certo  controllo su apt, o aptitude se si preferisce, in fase di compilazione  quando i pacchetti sono installati. Ci&ograve; pu&ograve; tornare utile se si usa un  proxy, se si vuole disabilitare l'installazione dei pacchetti raccomandati  per risparmiare spazio o controllare quali versioni dei pacchetti vengono  installate con il pinning, giusto per citare alcune possibilit&agrave;.
  </p>
</div><div class="substance">
  <label class="ocn"><a name="341" href="#341" class="lnkocn">341</a></label>
  <p class="bold" id="o341"><a name="341"></a> <a name="h8.1" id="h8.1"></a>
    <a name="8.1" ></a><a name="h8.1" ></a>8.1 Sorgenti dei pacchetti
  </p>
</div><div class="substance">
  <label class="ocn"><a name="342" href="#342" class="lnkocn">342</a></label>
  <p class="bold" id="o342"><a name="342"></a> <a name="h8.1.1" id="h8.1.1"></a>
    <a name="8.1.1" ></a><a name="h8.1.1" ></a>8.1.1 Distribuzione, le aree di archivio e le modalit&agrave;
  </p>
</div><div class="substance">
  <label class="ocn"><a name="343" href="#343" class="lnkocn">343</a></label>
  <p class="i0" id="o343">
    La distribuzione che viene scelta ha un ampio impatto su quali pacchetti  siano disponibili per essere inclusi nell'immagine live. Specificare il nome  in codice, il predefinito per la versione <b>Wheezy</b> di <i>live-build</i> &egrave; <tt>wheezy</tt>;  qualsiasi attuale distribuzione mantenuta negli archivi Debian pu&ograve; essere  qui specificata con il suo nome in codice. (Per ulteriori dettagli  consultare il  <a href="about-manual.html#terms">Glossario</a>).  L'opzione <tt>--distribution</tt> non solo  influenza la sorgente dei pacchetti nell'archivio, ma indica a  <tt>live-build</tt> di comportarsi secondo la necessit&agrave; per compilare ciascuna  distribuzione supportata. Ad esempio se si vuole costruire un rilascio  *unstable*, <b>Sid</b>, specificare:
  </p>
</div><div class="substance">
  <label class="ocn"><a name="344" href="#344" class="lnkocn">344</a></label>
  <p class="code" id="o344">
    $ lb config --distribution sid<br /><br />
  </p>
</div><div class="substance">
  <label class="ocn"><a name="345" href="#345" class="lnkocn">345</a></label>
  <p class="i0" id="o345">
    All'interno dell'archivio dei pacchetti, le aree sono le principali  divisioni dello stesso. In Debian queste sono <tt>main</tt>, <tt>contrib</tt> e  <tt>non-free</tt>; soltanto <tt>main</tt> contiene il software che &egrave; parte di Debian,  perci&ograve; questa &egrave; la predefinita. Possono essere specificati uno o pi&ugrave; valori:
  </p>
</div><div class="substance">
  <label class="ocn"><a name="346" href="#346" class="lnkocn">346</a></label>
  <p class="code" id="o346">
    $ lb config --archive-areas "main contrib"<br /><br />
  </p>
</div><div class="substance">
  <label class="ocn"><a name="347" href="#347" class="lnkocn">347</a></label>
  <p class="i0" id="o347">
    Attraverso l'opzione <tt>--mode</tt> &egrave; disponibile un supporto sperimentale per  alcune derivate di Debian; per impostazione predefinita, questa opzione &egrave;  impostata su <tt>debian</tt>, anche se si sta costruendo un sistema diverso da  Debian. Se si specifica <tt>--mode ubuntu</tt> o <tt>--mode emdebian</tt>, saranno  gestiti i nomi della distribuzione e le aree di archivio per la derivata  specificata e non quelli di Debian. La modalit&agrave; cambia anche il  comportamento di <i>live-build</i> per adattarlo alle derivate.
  </p>
</div><div class="substance">
  <label class="ocn"><a name="348" href="#348" class="lnkocn">348</a></label>
  <p class="i0" id="o348">
    <b>Nota:</b> i progetti per i quali sono state aggiunte tali modalit&agrave; sono i principali responsabili nel supportare gli utenti di queste opzioni. Il progetto Debian Live, a sua volta, fornisce sostegno allo sviluppo solamente sulla base dell'impegno migliore, sui feedback dei progetti derivati cos&igrave; come non sviluppiamo o sosteniamo queste derivate.
  </p>
</div><div class="substance">
  <label class="ocn"><a name="349" href="#349" class="lnkocn">349</a></label>
  <p class="bold" id="o349"><a name="349"></a> <a name="h8.1.2" id="h8.1.2"></a>
    <a name="8.1.2" ></a><a name="h8.1.2" ></a>8.1.2 Mirror delle distribuzioni
  </p>
</div><div class="substance">
  <label class="ocn"><a name="350" href="#350" class="lnkocn">350</a></label>
  <p class="i0" id="o350">
    The Debian archive is replicated across a large network of mirrors around  the world so that people in each region can choose a nearby mirror for best  download speed. Each of the <tt>--parent-mirror-*</tt> options governs which  distribution mirror is used at various stages of the build. Recall from   <a href="customization-overview.html#stages-of-the-build">Stages of the build</a>  that the *bootstrap* stage is when  the chroot is initially populated by debootstrap with a minimal system, and  the *chroot* stage is when the chroot used to construct the live system's  filesystem is built. Thus, the corresponding mirror switches are used for  those stages, and later, in the *binary* stage, the  <tt>--parent-mirror-binary</tt> and <tt>--parent-mirror-binary-security</tt> values  are used, superceding any mirrors used in an earlier stage.
  </p>
</div><div class="substance">
  <label class="ocn"><a name="351" href="#351" class="lnkocn">351</a></label>
  <p class="bold" id="o351"><a name="351"></a> <a name="hdistribution-mirrors-build-time" id="hdistribution-mirrors-build-time"></a>
    <a name="h8.1.3" ></a><a name="distribution-mirrors-build-time" ></a>8.1.3 Mirror delle distribuzioni usati in fase  di compilazione
  </p>
</div><div class="substance">
  <label class="ocn"><a name="352" href="#352" class="lnkocn">352</a></label>
  <p class="i0" id="o352">
    To set the distribution mirrors used at build time to point at a local  mirror, it is sufficient to set <tt>--parent-mirror-bootstrap</tt>,  <tt>--parent-mirror-chroot-security</tt> and <tt>--parent-mirror-chroot-backports</tt>  as follows.
  </p>
</div><div class="substance">
  <label class="ocn"><a name="353" href="#353" class="lnkocn">353</a></label>
  <p class="code" id="o353">
    $ lb config --parent-mirror-bootstrap http://localhost/debian/ \<br />
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;--parent-mirror-chroot-security http://localhost/debian-security/ \<br />
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;--parent-mirror-chroot-backports http://localhost/debian-backports/<br /> <br />
  </p>
</div><div class="substance">
  <label class="ocn"><a name="354" href="#354" class="lnkocn">354</a></label>
  <p class="i0" id="o354">
    The chroot mirror, specified by <tt>--parent-mirror-chroot</tt>, defaults to the  <tt>--parent-mirror-bootstrap</tt> value.
  </p>
</div><div class="substance">
  <label class="ocn"><a name="355" href="#355" class="lnkocn">355</a></label>
  <p class="bold" id="o355"><a name="355"></a> <a name="h8.1.4" id="h8.1.4"></a>
    <a name="8.1.4" ></a><a name="h8.1.4" ></a>8.1.4 Mirror delle distribuzioni usate durante l'esecuzione
  </p>
</div><div class="substance">
  <label class="ocn"><a name="356" href="#356" class="lnkocn">356</a></label>
  <p class="i0" id="o356">
    The <tt>--parent-mirror-binary*</tt> options govern the distribution mirrors  placed in the binary image. These may be used to install additional packages  while running the live system. The defaults employ <tt>cdn.debian.net</tt>, a  service that chooses a geographically close mirror based on the user's IP  number. This is a suitable choice when you cannot predict which mirror will  be best for all of your users. Or you may specify your own values as shown  in the example below. An image built from this configuration would only be  suitable for users on a network where "<tt>mirror</tt>" is reachable.
  </p>
</div><div class="substance">
  <label class="ocn"><a name="357" href="#357" class="lnkocn">357</a></label>
  <p class="code" id="o357">
    $ lb config --parent-mirror-binary http://mirror/debian/ \<br />
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;--parent-mirror-binary-security http://mirror/debian-security/<br /> <br />
  </p>
</div><div class="substance">
  <label class="ocn"><a name="358" href="#358" class="lnkocn">358</a></label>
  <p class="bold" id="o358"><a name="358"></a> <a name="hadditional-repositories" id="hadditional-repositories"></a>
    <a name="h8.1.5" ></a><a name="additional-repositories" ></a>8.1.5 Repository addizionali
  </p>
</div><div class="substance">
  <label class="ocn"><a name="359" href="#359" class="lnkocn">359</a></label>
  <p class="i0" id="o359">
    You may add more repositories, broadening your package choices beyond what  is available in your target distribution. These may be, for example, for  backports, experimental or custom packages. To configure additional  repositories, create <tt>config/archives/your-repository.list.chroot</tt>, and/or  <tt>config/archives/your-repository.list.binary</tt> files. As with the  <tt>--parent-mirror-*</tt> options, these govern the repositories used in the  *chroot* stage when building the image, and in the *binary* stage, i.e. for  use when running the live system.
  </p>
</div><div class="substance">
  <label class="ocn"><a name="360" href="#360" class="lnkocn">360</a></label>
  <p class="i0" id="o360">
    For example, <tt>config/archives/live.list.chroot</tt> allows you to install  packages from the debian live snapshot repository at live system build time.
  </p>
</div><div class="substance">
  <label class="ocn"><a name="361" href="#361" class="lnkocn">361</a></label>
  <p class="code" id="o361">
    deb http://live.debian.net/ sid-snapshots main contrib non-free<br /><br />
  </p>
</div><div class="substance">
  <label class="ocn"><a name="362" href="#362" class="lnkocn">362</a></label>
  <p class="i0" id="o362">
    If you add the same line to <tt>config/archives/live.list.binary</tt>, the  repository will be added to your live system's <tt>/etc/apt/sources.list.d/</tt>  directory.
  </p>
</div><div class="substance">
  <label class="ocn"><a name="363" href="#363" class="lnkocn">363</a></label>
  <p class="i0" id="o363">
    Se il file esiste, saranno prelevati automaticamente.
  </p>
</div><div class="substance">
  <label class="ocn"><a name="364" href="#364" class="lnkocn">364</a></label>
  <p class="i0" id="o364">
    You should also put the GPG key used to sign the repository into  <tt>config/archives/your-repository.gpg.{binary,chroot}</tt> files.
  </p>
</div><div class="substance">
  <label class="ocn"><a name="365" href="#365" class="lnkocn">365</a></label>
  <p class="i0" id="o365">
    <b>Note:</b> some preconfigured package repositories are available for easy selection through the <tt>--archives</tt> option, e.g. for enabling live snapshots, a simple command is enough to enable it:
  </p>
</div><div class="substance">
  <label class="ocn"><a name="366" href="#366" class="lnkocn">366</a></label>
  <p class="code" id="o366">
    $ lb config --archives live.debian.net<br /><br />
  </p>
</div><div class="substance">
  <label class="ocn"><a name="367" href="#367" class="lnkocn">367</a></label>
  <p class="bold" id="o367"><a name="367"></a> <a name="hchoosing-packages-to-install" id="hchoosing-packages-to-install"></a>
    <a name="h8.2" ></a><a name="choosing-packages-to-install" ></a>8.2 Scegliere i pacchetti da installare
  </p>
</div><div class="substance">
  <label class="ocn"><a name="368" href="#368" class="lnkocn">368</a></label>
  <p class="i0" id="o368">
    There are a number of ways to choose which packages <i>live-build</i> will install  in your image, covering a variety of different needs. You can simply name  individual packages to install in a package list. You can also choose  predefined lists of packages, or use APT tasks. And finally, you may place  package files in your <tt>config/</tt> tree, which is well suited to testing of  new or experimental packages before they are available from a repository.
  </p>
</div><div class="substance">
  <label class="ocn"><a name="369" href="#369" class="lnkocn">369</a></label>
  <p class="bold" id="o369"><a name="369"></a> <a name="hpackage-lists" id="hpackage-lists"></a>
    <a name="h8.2.1" ></a><a name="package-lists" ></a>8.2.1 Elenchi di pacchetti
  </p>
</div><div class="substance">
  <label class="ocn"><a name="370" href="#370" class="lnkocn">370</a></label>
  <p class="i0" id="o370">
    Gli elenchi di pacchetti sono un potente mezzo per esprimere quali pacchetti  devono essere installati. La sintassi gestisce file inclusi e sezioni  condizionali rendendo semplice la creazione di elenchi da altri elenchi e  adattarli per l'uso in molteplici configurazioni. Si pu&ograve; usare un elenco  predefinito fornendo una selezione modulare dei pacchetti da ciascuno dei  principali ambienti desktop e alcuni elenchi per uso speciale, cos&igrave; come  elenchi standard sui quali vi si basano altri. &Egrave; inoltre possibile fornire i  propri elenchi o usare una combinazione di entrambi.
  </p>
</div><div class="substance">
  <label class="ocn"><a name="371" href="#371" class="lnkocn">371</a></label>
  <p class="i0" id="o371">
    <b>Note:</b>  The behaviour of <i>live-build</i> when specifying a package that does not exist is determined by your choice of APT utility. See  <a href="customizing-package-installation.html#choosing-apt-or-aptitude">Choosing apt or aptitude</a>  for more details.
  </p>
</div><div class="substance">
  <label class="ocn"><a name="372" href="#372" class="lnkocn">372</a></label>
  <p class="bold" id="o372"><a name="372"></a> <a name="h8.2.2" id="h8.2.2"></a>
    <a name="8.2.2" ></a><a name="h8.2.2" ></a>8.2.2 Elenchi predefiniti di pacchetti
  </p>
</div><div class="substance">
  <label class="ocn"><a name="373" href="#373" class="lnkocn">373</a></label>
  <p class="i0" id="o373">
    The simplest way to use lists is to specify one or more predefined lists  with the <tt>--package-lists</tt> option. For example:
  </p>
</div><div class="substance">
  <label class="ocn"><a name="374" href="#374" class="lnkocn">374</a></label>
  <p class="code" id="o374">
    $ lb config --package-lists "gnome rescue"<br /><br />
  </p>
</div><div class="substance">
  <label class="ocn"><a name="375" href="#375" class="lnkocn">375</a></label>
  <p class="i0" id="o375">
    The default location for the list files on your system is  <tt>/usr/share/live/build/package-lists/</tt>. To determine the packages in a  given list, read the corresponding file, paying attention to included files  and conditionals as described in the following sections.
  </p>
</div><div class="substance">
  <label class="ocn"><a name="376" href="#376" class="lnkocn">376</a></label>
  <p class="bold" id="o376"><a name="376"></a> <a name="h8.2.3" id="h8.2.3"></a>
    <a name="8.2.3" ></a><a name="h8.2.3" ></a>8.2.3 Elenchi locali dei pacchetti
  </p>
</div><div class="substance">
  <label class="ocn"><a name="377" href="#377" class="lnkocn">377</a></label>
  <p class="i0" id="o377">
    You may supplement the predefined lists using local package lists stored in  <tt>config/package-lists/</tt>.
  </p>
</div><div class="substance">
  <label class="ocn"><a name="378" href="#378" class="lnkocn">378</a></label>
  <p class="i0" id="o378">
    Package lists that exist in this directory need to have a <tt>.list</tt> suffix  in order to be processed, and then an additional stage suffix, <tt>.chroot</tt>  or <tt>.binary</tt> to indicate which stage the list is for.
  </p>
</div><div class="substance">
  <label class="ocn"><a name="379" href="#379" class="lnkocn">379</a></label>
  <p class="i0" id="o379">
    <b>Note:</b> If you don't specify the stage suffix, the list will be used for both stages. Normally, you want to specify <tt>.list.chroot</tt> so that the packages will only be installed in the live filesystem and not have an extra copy of the <tt>.deb</tt> placed on the media.
  </p>
</div><div class="substance">
  <label class="ocn"><a name="380" href="#380" class="lnkocn">380</a></label>
  <p class="bold" id="o380"><a name="380"></a> <a name="h8.2.4" id="h8.2.4"></a>
    <a name="8.2.4" ></a><a name="h8.2.4" ></a>8.2.4 Elenchi locali di pacchetti binari
  </p>
</div><div class="substance">
  <label class="ocn"><a name="381" href="#381" class="lnkocn">381</a></label>
  <p class="i0" id="o381">
    To make a binary stage list, place a file suffixed with <tt>.list.binary</tt> in  <tt>config/package-lists/</tt>. These packages are not installed in the live  filesystem, but are included on the live media under <tt>pool/</tt>. You would  typically use such a list with one of the non-live installer variants. As  mentioned above, if you want this list to be the same as your chroot stage  list, simply use the <tt>.list</tt> suffix by itself.
  </p>
</div><div class="substance">
  <label class="ocn"><a name="382" href="#382" class="lnkocn">382</a></label>
  <p class="bold" id="o382"><a name="382"></a> <a name="h8.2.5" id="h8.2.5"></a>
    <a name="8.2.5" ></a><a name="h8.2.5" ></a>8.2.5 Estendere un'elenco di pacchetti usando gli include
  </p>
</div><div class="substance">
  <label class="ocn"><a name="383" href="#383" class="lnkocn">383</a></label>
  <p class="i0" id="o383">
    The package lists that are included with <i>live-build</i> make extensive use of  includes. Refer to these in the <tt>/usr/share/live/build/package-lists/</tt>  directory, as they serve as good examples of how to write your own lists.
  </p>
</div><div class="substance">
  <label class="ocn"><a name="384" href="#384" class="lnkocn">384</a></label>
  <p class="i0" id="o384">
    For example, to make a list that includes the predefined <tt>gnome</tt> list plus  iceweasel, create <tt>config/package-lists/my.list.chroot</tt> with the following  contents:
  </p>
</div><div class="substance">
  <label class="ocn"><a name="385" href="#385" class="lnkocn">385</a></label>
  <p class="code" id="o385">
    #include &lt;gnome&gt;<br />
iceweasel<br /><br />
  </p>
</div><div class="substance">
  <label class="ocn"><a name="386" href="#386" class="lnkocn">386</a></label>
  <p class="bold" id="o386"><a name="386"></a> <a name="h8.2.6" id="h8.2.6"></a>
    <a name="8.2.6" ></a><a name="h8.2.6" ></a>8.2.6 Usare condizioni all'interno degli elenchi di pacchetti
  </p>
</div><div class="substance">
  <label class="ocn"><a name="387" href="#387" class="lnkocn">387</a></label>
  <p class="i0" id="o387">
    Ognuna delle variabili di configurazione di <i>live-build</i> situate in  <tt>config/*</tt> (senza il prefisso <tt>LB_</tt>) possono essere utilizzate per  istruzioni condizionali nell'elenco dei pacchetti. In genere questo  significa qualsiasi opzione di <tt>lb config</tt> in maiuscolo e con trattini  cambiati in trattini bassi; ma in pratica &egrave; la sola ad influenzare la  selezione dei pacchetti che abbia senso, come <tt>DISTRIBUTION</tt>,  <tt>ARCHITECTURE</tt> o <tt>ARCHIVE_AREAS</tt>.
  </p>
</div><div class="substance">
  <label class="ocn"><a name="388" href="#388" class="lnkocn">388</a></label>
  <p class="i0" id="o388">
    Per esempio, per installare <tt>ia32-libs</tt> se &egrave; specificata <tt>--architecture  amd64</tt>:
  </p>
</div><div class="substance">
  <label class="ocn"><a name="389" href="#389" class="lnkocn">389</a></label>
  <p class="code" id="o389">
    #if ARCHITECTURE amd64<br />
ia32-libs<br />
#endif<br /><br />
  </p>
</div><div class="substance">
  <label class="ocn"><a name="390" href="#390" class="lnkocn">390</a></label>
  <p class="i0" id="o390">
    Si pu&ograve; verificare per ognuna di una serie di valori, ad esempio per  installare <tt>memtest86+</tt> specificando sia <tt>--architecture i386</tt> sia  <tt>--architecture amd64</tt>:
  </p>
</div><div class="substance">
  <label class="ocn"><a name="391" href="#391" class="lnkocn">391</a></label>
  <p class="code" id="o391">
    #if ARCHITECTURE i386 amd64<br />
memtest86+<br />
#endif<br /><br />
  </p>
</div><div class="substance">
  <label class="ocn"><a name="392" href="#392" class="lnkocn">392</a></label>
  <p class="i0" id="o392">
    &Egrave; possibile provare altre variabili che contengano pi&ugrave; di un valore, ad  esempio per installare <tt>vrms</tt> specificando sia da <tt>contrib</tt> sia da  <tt>non-free</tt> tramite <tt>--archive-areas</tt>:
  </p>
</div><div class="substance">
  <label class="ocn"><a name="393" href="#393" class="lnkocn">393</a></label>
  <p class="code" id="o393">
    #if ARCHIVE_AREAS contrib non-free<br />
vrms<br />
#endif<br /><br />
  </p>
</div><div class="substance">
  <label class="ocn"><a name="394" href="#394" class="lnkocn">394</a></label>
  <p class="i0" id="o394">
    Una condizione pu&ograve; coinvolegere una direttiva <tt>#include</tt>:
  </p>
</div><div class="substance">
  <label class="ocn"><a name="395" href="#395" class="lnkocn">395</a></label>
  <p class="code" id="o395">
    #if ARCHITECTURE amd64<br />
#include <gnome-full><br />
#endif<br /><br />
  </p>
</div><div class="substance">
  <label class="ocn"><a name="396" href="#396" class="lnkocn">396</a></label>
  <p class="i0" id="o396">
    Le condizioni nidificate non sono supportate.
  </p>
</div><div class="substance">
  <label class="ocn"><a name="397" href="#397" class="lnkocn">397</a></label>
  <p class="bold" id="o397"><a name="397"></a> <a name="h8.2.7" id="h8.2.7"></a>
    <a name="8.2.7" ></a><a name="h8.2.7" ></a>8.2.7 Task
  </p>
</div><div class="substance">
  <label class="ocn"><a name="398" href="#398" class="lnkocn">398</a></label>
  <p class="i0" id="o398">
    The Debian Installer offers the user choices of a number of preselected  lists of packages, each one focused on a particular kind of system, or task  a system may be used for, such as "Graphical desktop environment", "Mail  server" or "Laptop". These lists are called "tasks" and are supported by APT  through the "Task:" field. You can specify one or more tasks in <i>live-build</i>  by putting them in a list in <tt>config/task-lists/</tt>, as in the example  below.
  </p>
</div><div class="substance">
  <label class="ocn"><a name="399" href="#399" class="lnkocn">399</a></label>
  <p class="code" id="o399">
    $ lb config<br />
$ echo "mail-server file-server" >> config/task-lists/my.list.chroot<br /><br />
  </p>
</div><div class="substance">
  <label class="ocn"><a name="400" href="#400" class="lnkocn">400</a></label>
  <p class="i0" id="o400">
    I task principali disponibili nell'installatore Debian possono essere  elencati nel sistema live con <tt>tasksel --list-tasks</tt>. I contenuti di ogni  task, inclusi quelli non inclusi in questo elenco, possono essere esaminati  con <tt>tasksel --task-packages</tt>.
  </p>
</div><div class="substance">
  <label class="ocn"><a name="401" href="#401" class="lnkocn">401</a></label>
  <p class="bold" id="o401"><a name="401"></a> <a name="hdesktop-and-language-tasks" id="hdesktop-and-language-tasks"></a>
    <a name="h8.2.8" ></a><a name="desktop-and-language-tasks" ></a>8.2.8 Task per desktop e lingua
  </p>
</div><div class="substance">
  <label class="ocn"><a name="402" href="#402" class="lnkocn">402</a></label>
  <p class="i0" id="o402">
    Desktop and language tasks are special cases that need some extra planning  and configuration. Live images are different from Debian Installer images in  this respect. In the Debian Installer, if the medium was prepared for a  particular desktop environment flavour, the corresponding task will be  automatically installed. Thus, there are internal <tt>gnome-desktop</tt>,  <tt>kde-desktop</tt>, <tt>lxde-desktop</tt> and <tt>xfce-desktop</tt> tasks, none of which  are offered in <tt>tasksel</tt>'s menu. Likewise, there are no menu entries for  tasks for languages, but the user's language choice during the install  influences the selection of corresponding language tasks.
  </p>
</div><div class="substance">
  <label class="ocn"><a name="403" href="#403" class="lnkocn">403</a></label>
  <p class="i0" id="o403">
    When developing a desktop live image, the image typically boots directly to  a working desktop, the choices of both desktop and default language having  been made at build time, not at run time as in the case of the Debian  Installer. That's not to say that a live image couldn't be built to support  multiple desktops or multiple languages and offer the user a choice, but  that is not <i>live-build</i>' s default behaviour.
  </p>
</div><div class="substance">
  <label class="ocn"><a name="404" href="#404" class="lnkocn">404</a></label>
  <p class="i0" id="o404">
    Because there is no provision made automatically for language tasks, which  include such things as language-specific fonts and input-method packages, if  you want them, you need to specify them in your configuration. For example,  a GNOME desktop image containing support for Japanese might include these  tasks:
  </p>
</div><div class="substance">
  <label class="ocn"><a name="405" href="#405" class="lnkocn">405</a></label>
  <p class="code" id="o405">
    $ lb config<br />
$ echo "gnome-desktop desktop standard laptop" >> config/task-lists/my.list.chroot<br />
$ echo "japanese japanese-desktop japanese-gnome-desktop" >> config/task-lists/my.list.chroot<br /><br />
  </p>
</div><div class="substance">
  <label class="ocn"><a name="406" href="#406" class="lnkocn">406</a></label>
  <p class="i0" id="o406">
    Since desktop tasks are "internal" tasks, for every desktop flavour task  included in the image, the corresponding value, if it differs from the  default, "gnome", must be preseeded in the "tasksel/desktop" debconf  variable or else tasksel will not recognize and install it. Thus:
  </p>
</div><div class="substance">
  <label class="ocn"><a name="407" href="#407" class="lnkocn">407</a></label>
  <p class="code" id="o407">
    $ lb config<br />
$ echo 'tasksel tasksel/desktop multiselect kde' >> config/preseed/my.preseed.chroot<br /><br />
  </p>
</div><div class="substance">
  <label class="ocn"><a name="408" href="#408" class="lnkocn">408</a></label>
  <p class="i0" id="o408">
    This parameter can take multiple values, e.g. "lxde xfce" instead of "kde".
  </p>
</div><div class="substance">
  <label class="ocn"><a name="409" href="#409" class="lnkocn">409</a></label>
  <p class="bold" id="o409"><a name="409"></a> <a name="hinstalling-modified-or-third-party-packages" id="hinstalling-modified-or-third-party-packages"></a>
    <a name="h8.3" ></a><a name="installing-modified-or-third-party-packages" ></a>8.3 Installare pacchetti  modificati o di terze parti
  </p>
</div><div class="substance">
  <label class="ocn"><a name="410" href="#410" class="lnkocn">410</a></label>
  <p class="i0" id="o410">
    Nonostante sia contro la filosofia di Debian Live, a volte pu&ograve; essere  necessario creare un sistema live con versioni modificate dei pacchetti nel  repository Debian. Questo per modificare o gestire funzionalit&agrave; aggiuntive,  lingue e marchi, o anche rimuovere elementi non desiderati da pacchetti  esistenti. Allo stesso modo, i pacchetti di "terze parti" possono essere  utilizzati per aggiungere funzionalit&agrave; proprietarie o su misura.
  </p>
</div><div class="substance">
  <label class="ocn"><a name="411" href="#411" class="lnkocn">411</a></label>
  <p class="i0" id="o411">
    Questa sezione non tratta la compilazione e il mantenimento di pacchetti  modificati. Pu&ograve; comunque essere interessante leggere "How to fork privately"  di Joachim Breitner:  ‹<a href="http://www.joachim-breitner.de/blog/archives/282-How-to-fork-privately.html" target="_top">http://www.joachim-breitner.de/blog/archives/282-How-to-fork-privately.html</a>›  La creazione di pacchetti su misura &egrave; esposta nella "Guida per il nuovo  Maintainer" all'indirizzo ‹<a href="http://www.debian.org/doc/maint-guide/" target="_top">http://www.debian.org/doc/maint-guide/</a>› e altrove.
  </p>
</div><div class="substance">
  <label class="ocn"><a name="412" href="#412" class="lnkocn">412</a></label>
  <p class="i0" id="o412">
    Ci sono due modi per installare pacchetti personalizzati:
  </p>
</div><div class="substance">
  <label class="ocn"><a name="413" href="#413" class="lnkocn">413</a></label>
  <li class="bullet" id="o413">
    <tt>packages.chroot</tt>
  </li>
</div><div class="substance">
  <label class="ocn"><a name="414" href="#414" class="lnkocn">414</a></label>
  <li class="bullet" id="o414">
    Utilizzare repository APT personalizzati
  </li>
</div><div class="substance">
  <label class="ocn"><a name="415" href="#415" class="lnkocn">415</a></label>
  <p class="i0" id="o415">
    Using <tt>packages.chroot</tt> is simpler to achieve and useful for "one-off"  customizations but has a number of drawbacks, whilst using a custom APT  repository is more time-consuming to set up.
  </p>
</div><div class="substance">
  <label class="ocn"><a name="416" href="#416" class="lnkocn">416</a></label>
  <p class="bold" id="o416"><a name="416"></a> <a name="h8.3.1" id="h8.3.1"></a>
    <a name="8.3.1" ></a><a name="h8.3.1" ></a>8.3.1 Using <tt>packages.chroot</tt> to install custom packages
  </p>
</div><div class="substance">
  <label class="ocn"><a name="417" href="#417" class="lnkocn">417</a></label>
  <p class="i0" id="o417">
    To install a custom package, simply copy it to the  <tt>config/packages.chroot/</tt> directory. Packages that are inside this  directory will be automatically installed into the live system during build  - you do not need to specify them elsewhere.
  </p>
</div><div class="substance">
  <label class="ocn"><a name="418" href="#418" class="lnkocn">418</a></label>
  <p class="i0" id="o418">
    I pacchetti <b>devono</b> essere nominati nel modo prescritto, un metodo  semplice per farlo &egrave; usare <tt>dpkg-name</tt>.
  </p>
</div><div class="substance">
  <label class="ocn"><a name="419" href="#419" class="lnkocn">419</a></label>
  <p class="i0" id="o419">
    Using <tt>packages.chroot</tt> for installation of custom packages has  disadvantages:
  </p>
</div><div class="substance">
  <label class="ocn"><a name="420" href="#420" class="lnkocn">420</a></label>
  <li class="bullet" id="o420">
    non &egrave; possibile usare secure APT
  </li>
</div><div class="substance">
  <label class="ocn"><a name="421" href="#421" class="lnkocn">421</a></label>
  <li class="bullet" id="o421">
    You must install all appropriate packages in the  <tt>config/packages.chroot/</tt> directory.
  </li>
</div><div class="substance">
  <label class="ocn"><a name="422" href="#422" class="lnkocn">422</a></label>
  <li class="bullet" id="o422">
    non si presta a salvare le configurazioni di Debian Live nel controllo di  versione.
  </li>
</div><div class="substance">
  <label class="ocn"><a name="423" href="#423" class="lnkocn">423</a></label>
  <p class="bold" id="o423"><a name="423"></a> <a name="h8.3.2" id="h8.3.2"></a>
    <a name="8.3.2" ></a><a name="h8.3.2" ></a>8.3.2 Utilizzare un repository APT per installare pacchetti personalizzati
  </p>
</div><div class="substance">
  <label class="ocn"><a name="424" href="#424" class="lnkocn">424</a></label>
  <p class="i0" id="o424">
    Unlike using <tt>packages.chroot</tt>, when using a custom APT repository you  must ensure that you specify the packages elsewhere. See  <a href="customizing-package-installation.html#choosing-packages-to-install">Choosing packages  to install</a>  for details.
  </p>
</div><div class="substance">
  <label class="ocn"><a name="425" href="#425" class="lnkocn">425</a></label>
  <p class="i0" id="o425">
    Sebbene creare un repository APT possa sembrare uno sforzo inutile,  l'infrastruttura pu&ograve; facilmente essere riutilizzata in un secondo momento  per offrire aggiornamenti dei pacchetti modificati.
  </p>
</div><div class="substance">
  <label class="ocn"><a name="426" href="#426" class="lnkocn">426</a></label>
  <p class="bold" id="o426"><a name="426"></a> <a name="h8.3.3" id="h8.3.3"></a>
    <a name="8.3.3" ></a><a name="h8.3.3" ></a>8.3.3 Pacchetti personalizzati e APT
  </p>
</div><div class="substance">
  <label class="ocn"><a name="427" href="#427" class="lnkocn">427</a></label>
  <p class="i0" id="o427">
    <i>live-build</i> utilizza APT per installare tutti i pacchetti nel sistema live in  modo da ereditare i comportamenti di questo programma. Un esempio rilevante  &egrave; che (considerando una configurazione predefinita) dato un pacchetto  disponibile in due repository differenti con numeri di versione diversi, APT  sceglie di installare quello con il numero di versione pi&ugrave; alto.
  </p>
</div><div class="substance">
  <label class="ocn"><a name="428" href="#428" class="lnkocn">428</a></label>
  <p class="i0" id="o428">
    A causa di questo si pu&ograve; voler incrementare il numero della versione nei  file <tt>debian/changelog</tt> dei pacchetti personalizzati per accertare che la  propria versione avr&agrave; la precedenza sui repository Debian ufficiali. &Egrave; anche  ottenibile modificando le preferenze del APT pinning del sistema live, si  veda  <a href="customizing-package-installation.html#apt-pinning">APT pinning</a>  per maggiori informazioni.
  </p>
</div><div class="substance">
  <label class="ocn"><a name="429" href="#429" class="lnkocn">429</a></label>
  <p class="bold" id="o429"><a name="429"></a> <a name="h8.4" id="h8.4"></a>
    <a name="8.4" ></a><a name="h8.4" ></a>8.4 Configurare APT in fase di costruzione
  </p>
</div><div class="substance">
  <label class="ocn"><a name="430" href="#430" class="lnkocn">430</a></label>
  <p class="i0" id="o430">
    You can configure APT through a number of options applied only at build  time. (APT configuration used in the running live system may be configured  in the normal way for live system contents, that is, by including the  appropriate configurations through <tt>config/includes.chroot/</tt>.) For a  complete list, look for options starting with <tt>apt</tt> in the <tt>lb_config</tt>  man page.
  </p>
</div><div class="substance">
  <label class="ocn"><a name="431" href="#431" class="lnkocn">431</a></label>
  <p class="bold" id="o431"><a name="431"></a> <a name="hchoosing-apt-or-aptitude" id="hchoosing-apt-or-aptitude"></a>
    <a name="h8.4.1" ></a><a name="choosing-apt-or-aptitude" ></a>8.4.1 Scegliere apt o aptitude
  </p>
</div><div class="substance">
  <label class="ocn"><a name="432" href="#432" class="lnkocn">432</a></label>
  <p class="i0" id="o432">
    Per installare pacchetti in fase di compilazione si pu&ograve; optare sia per  <tt>apt</tt> sia per <tt>aptitude</tt>, l'argomento <tt>--apt</tt> di <tt>lb config</tt>  determina quale usare. Sceglie il metodo implementando il comportamento  preferito per l'installazione dei pacchetti, la notevole differenza &egrave; come  vengono gestiti quelli mancanti.
  </p>
</div><div class="substance">
  <label class="ocn"><a name="433" href="#433" class="lnkocn">433</a></label>
  <li class="bullet" id="o433">
    <tt>apt</tt>: se viene specificato un pacchetto mancante, l'installazione avr&agrave;  esito negativo; questo &egrave; l'impostazine predefinita.
  </li>
</div><div class="substance">
  <label class="ocn"><a name="434" href="#434" class="lnkocn">434</a></label>
  <li class="bullet" id="o434">
    <tt>aptitude</tt>: se viene specificato un pacchetto mancante, l'installazione  avr&agrave; successo.
  </li>
</div><div class="substance">
  <label class="ocn"><a name="435" href="#435" class="lnkocn">435</a></label>
  <p class="bold" id="o435"><a name="435"></a> <a name="h8.4.2" id="h8.4.2"></a>
    <a name="8.4.2" ></a><a name="h8.4.2" ></a>8.4.2 Utilizzare un proxy con APT
  </p>
</div><div class="substance">
  <label class="ocn"><a name="436" href="#436" class="lnkocn">436</a></label>
  <p class="i0" id="o436">
    Una configurazione di APT spesso richiesta &egrave; di amministrare la creazione di  un'immagine dietro un proxy, lo si pu&ograve; specificare con le opzioni  <tt>--apt-ftp-proxy</tt> o <tt>--apt-http-proxy</tt> secondo necessit&agrave;:
  </p>
</div><div class="substance">
  <label class="ocn"><a name="437" href="#437" class="lnkocn">437</a></label>
  <p class="code" id="o437">
    $ lb config --apt-http-proxy http://proxy/<br /> <br />
  </p>
</div><div class="substance">
  <label class="ocn"><a name="438" href="#438" class="lnkocn">438</a></label>
  <p class="bold" id="o438"><a name="438"></a> <a name="h8.4.3" id="h8.4.3"></a>
    <a name="8.4.3" ></a><a name="h8.4.3" ></a>8.4.3 Modificare APT per risparmiare spazio
  </p>
</div><div class="substance">
  <label class="ocn"><a name="439" href="#439" class="lnkocn">439</a></label>
  <p class="i0" id="o439">
    Si pu&ograve; aver bisogno di risparmiare dello spazio sul supporto dell'immagine,  in tal caso una o entrambe delle seguenti opzioni possono essere  d'interesse.
  </p>
</div><div class="substance">
  <label class="ocn"><a name="440" href="#440" class="lnkocn">440</a></label>
  <p class="i0" id="o440">
    &Egrave; possibile non includere gli indici di APT con:
  </p>
</div><div class="substance">
  <label class="ocn"><a name="441" href="#441" class="lnkocn">441</a></label>
  <p class="code" id="o441">
    $ lb config --apt-indices false<br /><br />
  </p>
</div><div class="substance">
  <label class="ocn"><a name="442" href="#442" class="lnkocn">442</a></label>
  <p class="i0" id="o442">
    Questo non influenzer&agrave; le voci in /etc/apt/sources.list, determina solo se  /var/lib/apt contiene o meno i file degli indici. Il compromesso &egrave; che APT  necessita di quegli indici per operar enel sistema live, perci&ograve; prima di  eseguire <tt>apt-cache search</tt> o <tt>apt-get install</tt>, per esempio, l'utente  deve usare prima <tt>apt-get update</tt> per crearli.
  </p>
</div><div class="substance">
  <label class="ocn"><a name="443" href="#443" class="lnkocn">443</a></label>
  <p class="i0" id="o443">
    In caso si trovi che l'installazione dei pacchetti raccomandati appesantisca  troppo l'immagine, si pu&ograve; disabilitare l'opzione predefinita di APT con:
  </p>
</div><div class="substance">
  <label class="ocn"><a name="444" href="#444" class="lnkocn">444</a></label>
  <p class="code" id="o444">
    $ lb config --apt-recommends false<br /><br />
  </p>
</div><div class="substance">
  <label class="ocn"><a name="445" href="#445" class="lnkocn">445</a></label>
  <p class="i0" id="o445">
    Qui il compromesso &egrave; dato dal fatto che se non si installano i raccomandati  per un certo pacchetto, ovvero "pacchetti che si trovano assieme a questo  eccetto in installazioni non usuali" (Debian Policy Manual, paragrafo 7.2),  saranno omessi alcuni di quelli realmente necessari. Si suggerisce pertanto  di verificare la differenza ottenuta nel proprio elenco di pacchetti  disabilitando i raccomandati (vedere il file <tt>binary.packages</tt> generato da  <tt>lb build</tt>) e includere nuovamente in esso quelli omessi che si desiderano  installare. In alternativa, se si desidera lasciare un modesto numero di  raccomandati, li si lasci abilitati e si assegni ad APT un pin di priorit&agrave;  negativo sui pacchetti selezionati affinch&eacute; non vengano installati, come  spiegato in  <a href="customizing-package-installation.html#apt-pinning">APT pinning</a>.
  </p>
</div><div class="substance">
  <label class="ocn"><a name="446" href="#446" class="lnkocn">446</a></label>
  <p class="bold" id="o446"><a name="446"></a> <a name="h8.4.4" id="h8.4.4"></a>
    <a name="8.4.4" ></a><a name="h8.4.4" ></a>8.4.4 Passare opzioni ad apt o aptitude
  </p>
</div><div class="substance">
  <label class="ocn"><a name="447" href="#447" class="lnkocn">447</a></label>
  <p class="i0" id="o447">
    Se non c'&egrave; un'opzione di <tt>lb config</tt> per modificare il comportamento di  APT nel modo desiderato, si usi <tt>--apt-options</tt> o <tt>--aptitude-options</tt>  per passare opzioni tramite il proprio strumento APT. Consultare il manuale  di <tt>apt</tt> e <tt>aptitude</tt> per i dettagli.
  </p>
</div><div class="substance">
  <label class="ocn"><a name="448" href="#448" class="lnkocn">448</a></label>
  <p class="bold" id="o448"><a name="448"></a> <a name="hapt-pinning" id="hapt-pinning"></a>
    <a name="h8.4.5" ></a><a name="apt-pinning" ></a>8.4.5 APT pinning
  </p>
</div><div class="substance">
  <label class="ocn"><a name="449" href="#449" class="lnkocn">449</a></label>
  <p class="i0" id="o449">
    For background, please first read the <tt>apt_preferences(5)</tt> man page. APT  pinning can be configured either for build time, or else for run time. For  the former, create <tt>config/chroot_apt/preferences</tt>. For the latter, create  <tt>config/includes.chroot/etc/apt/preferences</tt>.
  </p>
</div><div class="substance">
  <label class="ocn"><a name="450" href="#450" class="lnkocn">450</a></label>
  <p class="i0" id="o450">
    Nell'ipotesi di creare un sistema live <b>Wheezy</b> e avendo la necessit&agrave; di  installare da <b>Sid</b> tutti i pacchetti live destinati all'immagine binaria  questa fase, bisogna aggiungere <b>Sid</b> alle fonti di APT e farne il pinning  affinch&eacute; verranno installati da l&igrave; solo i pacchetti voluti, mentre per tutti  gli altri si attinger&agrave; dalla distribuzione principale, <b>Wheezy</b>. Quanto segue  servir&agrave; allo scopo:
  </p>
</div><div class="substance">
  <label class="ocn"><a name="451" href="#451" class="lnkocn">451</a></label>
  <p class="code" id="o451">
    $ echo "deb http://mirror/debian sid main" > config/archives/sid.list.chroot<br />
$ cat >> config/chroot_apt/preferences <<END<br />
Package: live-boot live-boot-initramfs-tools live-config live-config-sysvinit<br />
Pin: release n=sid<br />
Pin-Priority: 600<br /><br />
Package: *<br />
Pin: release n=sid<br />
Pin-Priority: 1<br />
END<br /><br />
  </p>
</div><div class="substance">
  <label class="ocn"><a name="452" href="#452" class="lnkocn">452</a></label>
  <p class="i0" id="o452">
    <b>Nota:</b> con la versione 0.8.14 o superiore di Apt si possono utilizzare wildcard nei nomi dei pacchetti (<b>Package: live-*</b>). Ci&ograve; significa che funziona con <b>Wheezy</b> usando:
  </p>
</div><div class="substance">
  <label class="ocn"><a name="453" href="#453" class="lnkocn">453</a></label>
  <p class="code" id="o453">
    $ lb config --distribution wheezy<br /><br />
  </p>
</div><div class="substance">
  <label class="ocn"><a name="454" href="#454" class="lnkocn">454</a></label>
  <p class="i0" id="o454">
    Negative pin priorities will prevent a package from being installed, as in  the case where you do not want a package that is recommended by another  package. Suppose you are building an LXDE image using <tt>--package-lists  lxde</tt> option, but don't want the user prompted to store wifi passwords in  the keyring. This list includes <tt>gdm</tt>, which depends on <tt>gksu</tt>, which in  turn recommends <tt>gnome-keyring</tt>. So you want to omit the recommended  <tt>gnome-keyring</tt> package. This can be done by adding the following stanza  to <tt>config/chroot_apt/preferences</tt>:
  </p>
</div><div class="substance">
  <label class="ocn"><a name="455" href="#455" class="lnkocn">455</a></label>
  <p class="code" id="o455">
    Package: gnome-keyring<br />
Pin: version *<br />
Pin-Priority: -1<br /><br />
  </p>
</div></div><br /><div class="main_column">
  <table summary="segment navigation band" bgcolor="#ffffff" width="100%"><tr>
  <td width="70%" align="center">
    
<table summary="segment navigation available documents types: toc,doc,pdf,concordance" border="0" cellpadding="3" cellspacing="0">
<tr>
<td align="center" bgcolor="#ffffff">
  <td align="center" bgcolor="#ffffff">
  <a href="sisu_manifest.it.html" target="_top" >
      <font face="verdana, arial, georgia, tahoma, sans-serif, helvetica, times, roman" size="2">
    [&nbsp;document&nbsp;manifest&nbsp;]
  </font> 
  </a>
</td>
  
</tr></table>
  </td>
  <td width="5%" align="right">
    <table summary="segment navigation pre/next" border="0" cellpadding="3" cellspacing="0">
<tr>
<td align="center" bgcolor="#ffffff">
  <a href="customization-overview.it.html" target="_top" >
    <img border="0" width="22" height="22" src="../_sisu/image_sys/arrow_prev_red.png" alt="&lt;&lt;&nbsp;previous" />
  </a>
</td>
<td align="center" bgcolor="#ffffff">
  <a href="toc.it.html" target="_top" >
    <img border="0" width="22" height="22" src="../_sisu/image_sys/arrow_up_red.png" alt="TOC" />
  </a>
</td>
<td align="center" bgcolor="#ffffff">
  <a href="customizing-contents.it.html" target="_top" >
    <img border="0" width="22" height="22" src="../_sisu/image_sys/arrow_next_red.png" alt="next&nbsp;&gt;&gt;" />
  </a>
</td>
<td>
</td></tr>
</table>
  </td></tr>
  </table>
  <table summary="segment hidden control pre and next" width="100%" border="0" cellpadding="0" bgcolor=#eeeeee align="center">
<tr><td align="left">
  <a href="customization-overview.it.html" target="_top" >
    <img border="0" width="100%" height="20" src="../_sisu/image_sys/dot_white.png" alt="&lt;" />
  </a>
</td>
<td align="center">
  <a href="toc.it.html" target="_top" >
    <img border="0" width="100%" height="20" src="../_sisu/image_sys/dot_white.png" alt="&#094;" />
  </a>
</td>
<td align="right">
  <a href="customizing-contents.it.html" target="_top" >
    <img border="0" width="100%" height="20" src="../_sisu/image_sys/dot_white.png" alt="&gt;" />
  </a>
</td></tr>
</table>
</div><div class="main_column">


<a name="bottom" id="bottom"></a>
<a name="down" id="down"></a>
<a name="end" id="end"></a>
<a name="finish" id="finish"></a>
<a name="stop" id="stop"></a>
<a name="credits" id="credits"></a>
</div></div></body>
</html>