/usr/share/doc/live-manual/html/customizing-package-installation.pt_BR.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 -
Debian Live Manual
</title>
<meta http-equiv="Content-Type" content="text/html;charset=utf-8" />
<meta name="dc.title" content="Debian Live Manual" />
<meta name="dc.author" content="Debian Live Project <debian-live@lists.debian.org>" />
<meta name="dc.publisher" content="Debian Live Project <debian-live@lists.debian.org>" />
<meta name="dc.date" content="2011-12-04" />
<meta name="dc.rights" content="Copyright (C) 2006-2011 Debian Live Project;<br> License: This program is free software: you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation, either version 3 of the License, or (at your option) any later version.<br><br>This program is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for more details.<br><br>You should have received a copy of the GNU General Public License along with this program. If not, see http://www.gnu.org/licenses/. <br><br>The complete text of the GNU General Public License can be found in /usr/share/common-licenses/GPL-3 file." />
<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 -->" /></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.pt_BR.html" target="_top" >
<font face="verdana, arial, georgia, tahoma, sans-serif, helvetica, times, roman" size="2">
[ document manifest ]
</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.pt_BR.html" target="_top" >
<img border="0" width="22" height="22" src="../_sisu/image_sys/arrow_prev_red.png" alt="<< previous" />
</a>
</td>
<td align="center" bgcolor="#ffffff">
<a href="toc.pt_BR.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.pt_BR.html" target="_top" >
<img border="0" width="22" height="22" src="../_sisu/image_sys/arrow_next_red.png" alt="next >>" />
</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.pt_BR.html" target="_top" >
<img border="0" width="100%" height="20" src="../_sisu/image_sys/dot_white.png" alt="<" />
</a>
</td>
<td align="center">
<a href="toc.pt_BR.html" target="_top" >
<img border="0" width="100%" height="20" src="../_sisu/image_sys/dot_white.png" alt="^" />
</a>
</td>
<td align="right">
<a href="customizing-contents.pt_BR.html" target="_top" >
<img border="0" width="100%" height="20" src="../_sisu/image_sys/dot_white.png" alt=">" />
</a>
</td></tr>
</table><div class="content">
<h1 class="tiny">
Debian Live Manual
</h1>
</div><div class="content">
<h2 class="tiny">
User
</h2>
</div><div class="content"><div class="substance">
<label class="ocn"><a name="338" href="#338" class="lnkocn">338</a></label>
<h1 class="norm" id="o338"><a name="338"></a>
8. Customizing package installation
</h1>
</div><div class="substance">
<label class="ocn"><a name="339" href="#339" class="lnkocn">339</a></label>
<p class="i0" id="o339">
Perhaps the most basic customization of a Debian live system is the selection of packages to be included in the image. This chapter guides you through the various build-time options to customize <i>live-build</i>' s installation of packages. The broadest choices influencing which packages are available to install in the image are the distribution and archive areas. To ensure decent download speeds, you should choose a nearby distribution mirror. You can also add your own repositories for backports, experimental or custom packages, or include packages directly as files. You can define your own lists of packages to include, use <i>live-build</i>' s predefined lists, use <tt>tasksel</tt> tasks, or a combination of all three. Finally, a number of options give some control over apt, or if you prefer, aptitude, at build time when packages are installed. You may find these handy if you use a proxy, want to disable installation of recommended packages to save space, or need to control which versions of packages are installed via APT pinning, to name a few possibilities.
</p>
</div><div class="substance">
<label class="ocn"><a name="340" href="#340" class="lnkocn">340</a></label>
<p class="bold" id="o340"><a name="340"></a> <a name="h8.1" id="h8.1"></a>
<a name="8.1" ></a><a name="h8.1" ></a>8.1 Package sources
</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.1" id="h8.1.1"></a>
<a name="8.1.1" ></a><a name="h8.1.1" ></a>8.1.1 Distribution, archive areas and mode
</p>
</div><div class="substance">
<label class="ocn"><a name="342" href="#342" class="lnkocn">342</a></label>
<p class="i0" id="o342">
The distribution you choose has the broadest impact on which packages are available to include in your live image. Specify the codename, which defaults to <tt>wheezy</tt> for the <b>Wheezy</b> version of <i>live-build</i>. Any current distribution carried in the Debian archive may be specified by its codename here. (See <a href="about-manual.html#terms">Terms</a> for more details.) The <tt>--distribution</tt> option not only influences the source of packages within the archive, but also instructs <tt>live-build</tt> to behave as needed to build each supported distribution. For example, to build against the *unstable* release, <b>Sid</b>, specify:
</p>
</div><div class="substance">
<label class="ocn"><a name="343" href="#343" class="lnkocn">343</a></label>
<p class="code" id="o343">
$ lb config --distribution sid<br /><br />
</p>
</div><div class="substance">
<label class="ocn"><a name="344" href="#344" class="lnkocn">344</a></label>
<p class="i0" id="o344">
Within the distribution archive, archive areas are major divisions of the archive. In Debian, these are <tt>main</tt>, <tt>contrib</tt> and <tt>non-free</tt>. Only <tt>main</tt> contains software that is part of the Debian distribution, hence that is the default. One or more values may be specified, e.g.
</p>
</div><div class="substance">
<label class="ocn"><a name="345" href="#345" class="lnkocn">345</a></label>
<p class="code" id="o345">
$ lb config --archive-areas "main contrib"<br /><br />
</p>
</div><div class="substance">
<label class="ocn"><a name="346" href="#346" class="lnkocn">346</a></label>
<p class="i0" id="o346">
Experimental support is available for some Debian derivatives through a <tt>--mode</tt> option. By default, this option is set to <tt>debian</tt>, even if you are building on a non-Debian system. If you specify <tt>--mode ubuntu</tt> or <tt>--mode emdebian</tt>, the distribution names and archive areas for the specified derivative are supported instead of the ones for Debian. The mode also modifies <i>live-build</i> behaviour to suit the derivatives.
</p>
</div><div class="substance">
<label class="ocn"><a name="347" href="#347" class="lnkocn">347</a></label>
<p class="i0" id="o347">
<b>Note:</b> The projects for whom these modes were added are primarily responsible for supporting users of these options. The Debian live project, in turn, provides development support on a best-effort basis only, based on feedback from the derivative projects as we do not develop or support these derivatives ourselves.
</p>
</div><div class="substance">
<label class="ocn"><a name="348" href="#348" class="lnkocn">348</a></label>
<p class="bold" id="o348"><a name="348"></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 Distribution mirrors
</p>
</div><div class="substance">
<label class="ocn"><a name="349" href="#349" class="lnkocn">349</a></label>
<p class="i0" id="o349">
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="350" href="#350" class="lnkocn">350</a></label>
<p class="bold" id="o350"><a name="350"></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 Distribution mirrors used at build time
</p>
</div><div class="substance">
<label class="ocn"><a name="351" href="#351" class="lnkocn">351</a></label>
<p class="i0" id="o351">
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="352" href="#352" class="lnkocn">352</a></label>
<p class="code" id="o352">
$ lb config --parent-mirror-bootstrap http://localhost/debian/ \<br />
--parent-mirror-chroot-security http://localhost/debian-security/ \<br />
--parent-mirror-chroot-backports http://localhost/debian-backports/<br /> <br />
</p>
</div><div class="substance">
<label class="ocn"><a name="353" href="#353" class="lnkocn">353</a></label>
<p class="i0" id="o353">
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="354" href="#354" class="lnkocn">354</a></label>
<p class="bold" id="o354"><a name="354"></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 Distribution mirrors used at run time
</p>
</div><div class="substance">
<label class="ocn"><a name="355" href="#355" class="lnkocn">355</a></label>
<p class="i0" id="o355">
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="356" href="#356" class="lnkocn">356</a></label>
<p class="code" id="o356">
$ lb config --parent-mirror-binary http://mirror/debian/ \<br />
--parent-mirror-binary-security http://mirror/debian-security/<br /> <br />
</p>
</div><div class="substance">
<label class="ocn"><a name="357" href="#357" class="lnkocn">357</a></label>
<p class="bold" id="o357"><a name="357"></a> <a name="hadditional-repositories" id="hadditional-repositories"></a>
<a name="h8.1.5" ></a><a name="additional-repositories" ></a>8.1.5 Additional repositories
</p>
</div><div class="substance">
<label class="ocn"><a name="358" href="#358" class="lnkocn">358</a></label>
<p class="i0" id="o358">
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="359" href="#359" class="lnkocn">359</a></label>
<p class="i0" id="o359">
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="360" href="#360" class="lnkocn">360</a></label>
<p class="code" id="o360">
deb http://live.debian.net/ sid-snapshots main contrib non-free<br /><br />
</p>
</div><div class="substance">
<label class="ocn"><a name="361" href="#361" class="lnkocn">361</a></label>
<p class="i0" id="o361">
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="362" href="#362" class="lnkocn">362</a></label>
<p class="i0" id="o362">
If such files exist, they will be picked up automatically.
</p>
</div><div class="substance">
<label class="ocn"><a name="363" href="#363" class="lnkocn">363</a></label>
<p class="i0" id="o363">
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="364" href="#364" class="lnkocn">364</a></label>
<p class="i0" id="o364">
<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="365" href="#365" class="lnkocn">365</a></label>
<p class="code" id="o365">
$ lb config --archives live.debian.net<br /><br />
</p>
</div><div class="substance">
<label class="ocn"><a name="366" href="#366" class="lnkocn">366</a></label>
<p class="bold" id="o366"><a name="366"></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 Choosing packages to install
</p>
</div><div class="substance">
<label class="ocn"><a name="367" href="#367" class="lnkocn">367</a></label>
<p class="i0" id="o367">
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="368" href="#368" class="lnkocn">368</a></label>
<p class="bold" id="o368"><a name="368"></a> <a name="hpackage-lists" id="hpackage-lists"></a>
<a name="h8.2.1" ></a><a name="package-lists" ></a>8.2.1 Package lists
</p>
</div><div class="substance">
<label class="ocn"><a name="369" href="#369" class="lnkocn">369</a></label>
<p class="i0" id="o369">
Package lists are a powerful way of expressing which packages should be installed. The list syntax supports included files and conditional sections which makes it easy to build lists from other lists and adapt them for use in multiple configurations. You can use predefined package lists, providing in a modular fashion package selections from each of the major desktop environments and some special purpose lists, as well as standard lists the others are based upon. You can also provide your own package lists, or use a combination of both.
</p>
</div><div class="substance">
<label class="ocn"><a name="370" href="#370" class="lnkocn">370</a></label>
<p class="i0" id="o370">
<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="371" href="#371" class="lnkocn">371</a></label>
<p class="bold" id="o371"><a name="371"></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 Predefined package lists
</p>
</div><div class="substance">
<label class="ocn"><a name="372" href="#372" class="lnkocn">372</a></label>
<p class="i0" id="o372">
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="373" href="#373" class="lnkocn">373</a></label>
<p class="code" id="o373">
$ lb config --package-lists "gnome rescue"<br /><br />
</p>
</div><div class="substance">
<label class="ocn"><a name="374" href="#374" class="lnkocn">374</a></label>
<p class="i0" id="o374">
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="375" href="#375" class="lnkocn">375</a></label>
<p class="bold" id="o375"><a name="375"></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 Local package lists
</p>
</div><div class="substance">
<label class="ocn"><a name="376" href="#376" class="lnkocn">376</a></label>
<p class="i0" id="o376">
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="377" href="#377" class="lnkocn">377</a></label>
<p class="i0" id="o377">
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="378" href="#378" class="lnkocn">378</a></label>
<p class="i0" id="o378">
<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="379" href="#379" class="lnkocn">379</a></label>
<p class="bold" id="o379"><a name="379"></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 Local binary package lists
</p>
</div><div class="substance">
<label class="ocn"><a name="380" href="#380" class="lnkocn">380</a></label>
<p class="i0" id="o380">
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="381" href="#381" class="lnkocn">381</a></label>
<p class="bold" id="o381"><a name="381"></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 Extending a provided package list using includes
</p>
</div><div class="substance">
<label class="ocn"><a name="382" href="#382" class="lnkocn">382</a></label>
<p class="i0" id="o382">
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="383" href="#383" class="lnkocn">383</a></label>
<p class="i0" id="o383">
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="384" href="#384" class="lnkocn">384</a></label>
<p class="code" id="o384">
#include <gnome><br />
iceweasel<br /><br />
</p>
</div><div class="substance">
<label class="ocn"><a name="385" href="#385" class="lnkocn">385</a></label>
<p class="bold" id="o385"><a name="385"></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 Using conditionals inside package lists
</p>
</div><div class="substance">
<label class="ocn"><a name="386" href="#386" class="lnkocn">386</a></label>
<p class="i0" id="o386">
Any of the <i>live-build</i> configuration variables stored in <tt>config/*</tt> (minus the <tt>LB_</tt> prefix) may be used in conditional statements in package lists. Generally, this means any <tt>lb config</tt> option uppercased and with dashes changed to underscores. But in practice, it is only the ones that influence package selection that make sense, such as <tt>DISTRIBUTION</tt>, <tt>ARCHITECTURE</tt> or <tt>ARCHIVE_AREAS</tt>.
</p>
</div><div class="substance">
<label class="ocn"><a name="387" href="#387" class="lnkocn">387</a></label>
<p class="i0" id="o387">
For example, to install <tt>ia32-libs</tt> if the <tt>--architecture amd64</tt> is specified:
</p>
</div><div class="substance">
<label class="ocn"><a name="388" href="#388" class="lnkocn">388</a></label>
<p class="code" id="o388">
#if ARCHITECTURE amd64<br />
ia32-libs<br />
#endif<br /><br />
</p>
</div><div class="substance">
<label class="ocn"><a name="389" href="#389" class="lnkocn">389</a></label>
<p class="i0" id="o389">
You may test for any one of a number of values, e.g. to install <tt>memtest86+</tt> if either <tt>--architecture i386</tt> or <tt>--architecture amd64</tt> is specified:
</p>
</div><div class="substance">
<label class="ocn"><a name="390" href="#390" class="lnkocn">390</a></label>
<p class="code" id="o390">
#if ARCHITECTURE i386 amd64<br />
memtest86+<br />
#endif<br /><br />
</p>
</div><div class="substance">
<label class="ocn"><a name="391" href="#391" class="lnkocn">391</a></label>
<p class="i0" id="o391">
You may also test against variables that may contain more than one value, e.g. to install <tt>vrms</tt> if either <tt>contrib</tt> or <tt>non-free</tt> is specified via <tt>--archive-areas</tt>:
</p>
</div><div class="substance">
<label class="ocn"><a name="392" href="#392" class="lnkocn">392</a></label>
<p class="code" id="o392">
#if ARCHIVE_AREAS contrib non-free<br />
vrms<br />
#endif<br /><br />
</p>
</div><div class="substance">
<label class="ocn"><a name="393" href="#393" class="lnkocn">393</a></label>
<p class="i0" id="o393">
A conditional may surround an <tt>#include</tt> directive:
</p>
</div><div class="substance">
<label class="ocn"><a name="394" href="#394" class="lnkocn">394</a></label>
<p class="code" id="o394">
#if ARCHITECTURE amd64<br />
#include <gnome-full><br />
#endif<br /><br />
</p>
</div><div class="substance">
<label class="ocn"><a name="395" href="#395" class="lnkocn">395</a></label>
<p class="i0" id="o395">
The nesting of conditionals is not supported.
</p>
</div><div class="substance">
<label class="ocn"><a name="396" href="#396" class="lnkocn">396</a></label>
<p class="bold" id="o396"><a name="396"></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 Tasks
</p>
</div><div class="substance">
<label class="ocn"><a name="397" href="#397" class="lnkocn">397</a></label>
<p class="i0" id="o397">
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="398" href="#398" class="lnkocn">398</a></label>
<p class="code" id="o398">
$ 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="399" href="#399" class="lnkocn">399</a></label>
<p class="i0" id="o399">
The primary tasks available in the Debian Installer can be listed with <tt>tasksel --list-tasks</tt> in the live system. The contents of any task, including ones not included in this list, may be examined with <tt>tasksel --task-packages</tt>.
</p>
</div><div class="substance">
<label class="ocn"><a name="400" href="#400" class="lnkocn">400</a></label>
<p class="bold" id="o400"><a name="400"></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 Desktop and language tasks
</p>
</div><div class="substance">
<label class="ocn"><a name="401" href="#401" class="lnkocn">401</a></label>
<p class="i0" id="o401">
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="402" href="#402" class="lnkocn">402</a></label>
<p class="i0" id="o402">
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="403" href="#403" class="lnkocn">403</a></label>
<p class="i0" id="o403">
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="404" href="#404" class="lnkocn">404</a></label>
<p class="code" id="o404">
$ 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="405" href="#405" class="lnkocn">405</a></label>
<p class="i0" id="o405">
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="406" href="#406" class="lnkocn">406</a></label>
<p class="code" id="o406">
$ 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="407" href="#407" class="lnkocn">407</a></label>
<p class="i0" id="o407">
This parameter can take multiple values, e.g. "lxde xfce" instead of "kde".
</p>
</div><div class="substance">
<label class="ocn"><a name="408" href="#408" class="lnkocn">408</a></label>
<p class="bold" id="o408"><a name="408"></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 Installing modified or third-party packages
</p>
</div><div class="substance">
<label class="ocn"><a name="409" href="#409" class="lnkocn">409</a></label>
<p class="i0" id="o409">
Whilst it is against the philosophy of Debian Live, it may sometimes be necessary to build a Live system with modified versions of packages that are in the Debian repository. This may be to modify or support additional features, languages and branding, or even to remove elements of existing packages that are undesirable. Similarly, "third-party" packages may be used to add bespoke and/or proprietary functionality.
</p>
</div><div class="substance">
<label class="ocn"><a name="410" href="#410" class="lnkocn">410</a></label>
<p class="i0" id="o410">
This section does not cover advice regarding building or maintaining modified packages. Joachim Breitner's 'How to fork privately' method from ‹<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>› may be of interest, however. The creation of bespoke packages is covered in the Debian New Maintainers' Guide at ‹<a href="http://www.debian.org/doc/maint-guide/" target="_top">http://www.debian.org/doc/maint-guide/</a>› and elsewhere.
</p>
</div><div class="substance">
<label class="ocn"><a name="411" href="#411" class="lnkocn">411</a></label>
<p class="i0" id="o411">
There are two ways of installing modified custom packages:
</p>
</div><div class="substance">
<label class="ocn"><a name="412" href="#412" class="lnkocn">412</a></label>
<li class="bullet" id="o412">
<tt>packages.chroot</tt>
</li>
</div><div class="substance">
<label class="ocn"><a name="413" href="#413" class="lnkocn">413</a></label>
<li class="bullet" id="o413">
Using a custom APT repository
</li>
</div><div class="substance">
<label class="ocn"><a name="414" href="#414" class="lnkocn">414</a></label>
<p class="i0" id="o414">
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="415" href="#415" class="lnkocn">415</a></label>
<p class="bold" id="o415"><a name="415"></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="416" href="#416" class="lnkocn">416</a></label>
<p class="i0" id="o416">
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="417" href="#417" class="lnkocn">417</a></label>
<p class="i0" id="o417">
Packages <b>must</b> be named in the prescribed way. One simple way to do this is to use <tt>dpkg-name</tt>.
</p>
</div><div class="substance">
<label class="ocn"><a name="418" href="#418" class="lnkocn">418</a></label>
<p class="i0" id="o418">
Using <tt>packages.chroot</tt> for installation of custom packages has disadvantages:
</p>
</div><div class="substance">
<label class="ocn"><a name="419" href="#419" class="lnkocn">419</a></label>
<li class="bullet" id="o419">
It is not possible to use secure APT.
</li>
</div><div class="substance">
<label class="ocn"><a name="420" href="#420" class="lnkocn">420</a></label>
<li class="bullet" id="o420">
You must install all appropriate packages in the <tt>config/packages.chroot/</tt> directory.
</li>
</div><div class="substance">
<label class="ocn"><a name="421" href="#421" class="lnkocn">421</a></label>
<li class="bullet" id="o421">
It does not lend itself to storing Debian Live configurations in revision control.
</li>
</div><div class="substance">
<label class="ocn"><a name="422" href="#422" class="lnkocn">422</a></label>
<p class="bold" id="o422"><a name="422"></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 Using an APT repository to install custom packages
</p>
</div><div class="substance">
<label class="ocn"><a name="423" href="#423" class="lnkocn">423</a></label>
<p class="i0" id="o423">
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="424" href="#424" class="lnkocn">424</a></label>
<p class="i0" id="o424">
Whilst it may seem unnecessary effort to create an APT repository to install custom packages, the infrastructure can be easily re-used at a later date to offer updates of the modified packages.
</p>
</div><div class="substance">
<label class="ocn"><a name="425" href="#425" class="lnkocn">425</a></label>
<p class="bold" id="o425"><a name="425"></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 Custom packages and APT
</p>
</div><div class="substance">
<label class="ocn"><a name="426" href="#426" class="lnkocn">426</a></label>
<p class="i0" id="o426">
<i>live-build</i> uses APT to install all packages into the live system so will therefore inherit behaviours from this program. One relevant example is that (assuming a default configuration) given a package available in two different repositories with different version numbers, APT will elect to install the package with the higher version number.
</p>
</div><div class="substance">
<label class="ocn"><a name="427" href="#427" class="lnkocn">427</a></label>
<p class="i0" id="o427">
Because of this, you may wish to increment the version number in your custom packages' <tt>debian/changelog</tt> files to ensure that your modified version is installed over one in the official Debian repositories. This may also be achieved by altering the live system's APT pinning preferences - see <a href="customizing-package-installation.html#apt-pinning">APT pinning</a> for more information.
</p>
</div><div class="substance">
<label class="ocn"><a name="428" href="#428" class="lnkocn">428</a></label>
<p class="bold" id="o428"><a name="428"></a> <a name="h8.4" id="h8.4"></a>
<a name="8.4" ></a><a name="h8.4" ></a>8.4 Configuring APT at build time
</p>
</div><div class="substance">
<label class="ocn"><a name="429" href="#429" class="lnkocn">429</a></label>
<p class="i0" id="o429">
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="430" href="#430" class="lnkocn">430</a></label>
<p class="bold" id="o430"><a name="430"></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 Choosing apt or aptitude
</p>
</div><div class="substance">
<label class="ocn"><a name="431" href="#431" class="lnkocn">431</a></label>
<p class="i0" id="o431">
You can elect to use either <tt>apt</tt> or <tt>aptitude</tt> when installing packages at build time. Which utility is used is governed by the <tt>--apt</tt> argument to <tt>lb config</tt>. Choose the method implementing the preferred behaviour for package installation, the notable difference being how missing packages are handled.
</p>
</div><div class="substance">
<label class="ocn"><a name="432" href="#432" class="lnkocn">432</a></label>
<li class="bullet" id="o432">
<tt>apt</tt>: With this method, if a missing package is specified, the package installation will fail. This is the default setting.
</li>
</div><div class="substance">
<label class="ocn"><a name="433" href="#433" class="lnkocn">433</a></label>
<li class="bullet" id="o433">
<tt>aptitude</tt>: With this method, if a missing package is specified, the package installation will succeed.
</li>
</div><div class="substance">
<label class="ocn"><a name="434" href="#434" class="lnkocn">434</a></label>
<p class="bold" id="o434"><a name="434"></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 Using a proxy with APT
</p>
</div><div class="substance">
<label class="ocn"><a name="435" href="#435" class="lnkocn">435</a></label>
<p class="i0" id="o435">
One commonly required APT configuration is to deal with building an image behind a proxy. You may specify your APT proxy with the <tt>--apt-ftp-proxy</tt> or <tt>--apt-http-proxy</tt> options as needed, e.g.
</p>
</div><div class="substance">
<label class="ocn"><a name="436" href="#436" class="lnkocn">436</a></label>
<p class="code" id="o436">
$ lb config --apt-http-proxy http://proxy/<br /> <br />
</p>
</div><div class="substance">
<label class="ocn"><a name="437" href="#437" class="lnkocn">437</a></label>
<p class="bold" id="o437"><a name="437"></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 Tweaking APT to save space
</p>
</div><div class="substance">
<label class="ocn"><a name="438" href="#438" class="lnkocn">438</a></label>
<p class="i0" id="o438">
You may find yourself needing to save some space on the image media, in which case one or the other or both of the following options may be of interest.
</p>
</div><div class="substance">
<label class="ocn"><a name="439" href="#439" class="lnkocn">439</a></label>
<p class="i0" id="o439">
If you don't want to include APT indices in the image, you can omit those with:
</p>
</div><div class="substance">
<label class="ocn"><a name="440" href="#440" class="lnkocn">440</a></label>
<p class="code" id="o440">
$ lb config --apt-indices false<br /><br />
</p>
</div><div class="substance">
<label class="ocn"><a name="441" href="#441" class="lnkocn">441</a></label>
<p class="i0" id="o441">
This will not influence the entries in /etc/apt/sources.list, but merely whether /var/lib/apt contains the indices files or not. The tradeoff is that APT needs those indices in order to operate in the live system, so before performing <tt>apt-cache search</tt> or <tt>apt-get install</tt>, for instance, the user must <tt>apt-get update</tt> first to create those indices.
</p>
</div><div class="substance">
<label class="ocn"><a name="442" href="#442" class="lnkocn">442</a></label>
<p class="i0" id="o442">
If you find the installation of recommended packages bloats your image too much, you may disable that default option of APT with:
</p>
</div><div class="substance">
<label class="ocn"><a name="443" href="#443" class="lnkocn">443</a></label>
<p class="code" id="o443">
$ lb config --apt-recommends false<br /><br />
</p>
</div><div class="substance">
<label class="ocn"><a name="444" href="#444" class="lnkocn">444</a></label>
<p class="i0" id="o444">
The tradeoff here is that if you don't install recommended packages for a given package, that is, "packages that would be found together with this one in all but unusual installations" (Debian Policy Manual, section 7.2), some packages that you actually need may be omitted. Therefore, we suggest you review the difference turning off recommends makes to your packages list (see the <tt>binary.packages</tt> file generated by <tt>lb build</tt>) and re-include in your list any missing packages that you still want installed. Alternatively, if you find you only want a small number of recommended packages left out, leave recommends enabled and set a negative APT pin priority on selected packages to prevent them from being installed, as explained in <a href="customizing-package-installation.html#apt-pinning">APT pinning</a>.
</p>
</div><div class="substance">
<label class="ocn"><a name="445" href="#445" class="lnkocn">445</a></label>
<p class="bold" id="o445"><a name="445"></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 Passing options to apt or aptitude
</p>
</div><div class="substance">
<label class="ocn"><a name="446" href="#446" class="lnkocn">446</a></label>
<p class="i0" id="o446">
If there is not an <tt>lb config</tt> option to alter APT's behaviour in the way you need, use <tt>--apt-options</tt> or <tt>--aptitude-options</tt> to pass any options through to your configured APT tool. See the man pages for <tt>apt</tt> and <tt>aptitude</tt> for details.
</p>
</div><div class="substance">
<label class="ocn"><a name="447" href="#447" class="lnkocn">447</a></label>
<p class="bold" id="o447"><a name="447"></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="448" href="#448" class="lnkocn">448</a></label>
<p class="i0" id="o448">
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="449" href="#449" class="lnkocn">449</a></label>
<p class="i0" id="o449">
Let's say you are building a <b>Wheezy</b> live system but need all the live packages that end up in the binary image to be installed from <b>Sid</b> at build time. You need to add <b>Sid</b> to your APT sources and pin it so that only the packages you want are installed from it at build time and all others are taken from the target system distribution, <b>Wheezy</b>. The following will accomplish this:
</p>
</div><div class="substance">
<label class="ocn"><a name="450" href="#450" class="lnkocn">450</a></label>
<p class="code" id="o450">
$ 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="451" href="#451" class="lnkocn">451</a></label>
<p class="i0" id="o451">
<b>Note:</b> Wildcards can be used in package names (e.g. <b>Package: live-*</b>) with Apt version 0.8.14 or higher. This means that it works with <b>Wheezy</b> using:
</p>
</div><div class="substance">
<label class="ocn"><a name="452" href="#452" class="lnkocn">452</a></label>
<p class="code" id="o452">
$ lb config --distribution wheezy<br /><br />
</p>
</div><div class="substance">
<label class="ocn"><a name="453" href="#453" class="lnkocn">453</a></label>
<p class="i0" id="o453">
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="454" href="#454" class="lnkocn">454</a></label>
<p class="code" id="o454">
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.pt_BR.html" target="_top" >
<font face="verdana, arial, georgia, tahoma, sans-serif, helvetica, times, roman" size="2">
[ document manifest ]
</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.pt_BR.html" target="_top" >
<img border="0" width="22" height="22" src="../_sisu/image_sys/arrow_prev_red.png" alt="<< previous" />
</a>
</td>
<td align="center" bgcolor="#ffffff">
<a href="toc.pt_BR.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.pt_BR.html" target="_top" >
<img border="0" width="22" height="22" src="../_sisu/image_sys/arrow_next_red.png" alt="next >>" />
</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.pt_BR.html" target="_top" >
<img border="0" width="100%" height="20" src="../_sisu/image_sys/dot_white.png" alt="<" />
</a>
</td>
<td align="center">
<a href="toc.pt_BR.html" target="_top" >
<img border="0" width="100%" height="20" src="../_sisu/image_sys/dot_white.png" alt="^" />
</a>
</td>
<td align="right">
<a href="customizing-contents.pt_BR.html" target="_top" >
<img border="0" width="100%" height="20" src="../_sisu/image_sys/dot_white.png" alt=">" />
</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>
|