Debian Developer's Reference

Total Page:16

File Type:pdf, Size:1020Kb

Debian Developer's Reference Debian Developer’s Reference Developer’s Reference Team <[email protected]> Andreas Barth Adam Di Carlo Raphaël Hertzog Christian Schwarz Ian Jackson ver. 3.3.9, 04 August, 2007 Copyright Notice copyright © 2004—2007 Andreas Barth copyright © 1998—2003 Adam Di Carlo copyright © 2002—2003 Raphaël Hertzog copyright © 1997, 1998 Christian Schwarz This manual is free software; you may redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation; either version 2, or (at your option) any later version. This 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. A copy of the GNU General Public License is available as /usr/share/common-licenses /GPL in the Debian GNU/Linux distribution or on the World Wide Web at the GNU web site (http://www.gnu.org/copyleft/gpl.html). You can also obtain it by writing to the Free Software Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301, USA. i Contents 1 Scope of This Document 1 2 Applying to Become a Maintainer 3 2.1 Getting started ....................................... 3 2.2 Debian mentors and sponsors .............................. 4 2.3 Registering as a Debian developer ........................... 4 3 Debian Developer’s Duties 7 3.1 Maintaining your Debian information ......................... 7 3.2 Maintaining your public key ............................... 7 3.3 Voting ............................................ 8 3.4 Going on vacation gracefully .............................. 8 3.5 Coordination with upstream developers ........................ 9 3.6 Managing release-critical bugs ............................. 9 3.7 Retiring ........................................... 9 4 Resources for Debian Developers 11 4.1 Mailing lists ........................................ 11 4.1.1 Basic rules for use ................................. 11 4.1.2 Core development mailing lists ......................... 12 4.1.3 Special lists .................................... 12 4.1.4 Requesting new development-related lists .................. 12 4.2 IRC channels ........................................ 13 4.3 Documentation ...................................... 13 4.4 Debian machines ..................................... 14 CONTENTS ii 4.4.1 The bugs server .................................. 14 4.4.2 The ftp-master server .............................. 15 4.4.3 The www-master server ............................. 15 4.4.4 The people web server .............................. 15 4.4.5 The VCS servers ................................. 15 4.4.6 chroots to different distributions ........................ 16 4.5 The Developers Database ................................ 16 4.6 The Debian archive .................................... 17 4.6.1 Sections ...................................... 18 4.6.2 Architectures ................................... 19 4.6.3 Packages ...................................... 20 4.6.4 Distributions ................................... 20 4.6.5 Release code names ............................... 22 4.7 Debian mirrors ...................................... 23 4.8 The Incoming system ................................... 23 4.9 Package information ................................... 24 4.9.1 On the web .................................... 24 4.9.2 The madison utility ............................... 24 4.10 The Package Tracking System .............................. 25 4.10.1 The PTS email interface ............................. 26 4.10.2 Filtering PTS mails ................................ 27 4.10.3 Forwarding VCS commits in the PTS ..................... 27 4.10.4 The PTS web interface .............................. 27 4.11 Developer’s packages overview ............................. 29 4.12 Debian’s GForge installation: Alioth .......................... 29 4.13 Goodies for Developers ................................. 30 4.13.1 LWN Subscriptions ................................ 30 5 Managing Packages 31 5.1 New packages ....................................... 31 5.2 Recording changes in the package ........................... 32 CONTENTS iii 5.3 Testing the package .................................... 32 5.4 Layout of the source package .............................. 33 5.5 Picking a distribution ................................... 34 5.5.1 Special case: uploads to the stable distribution ................ 34 5.5.2 Special case: uploads to testing/testing-proposed-updates ........... 35 5.6 Uploading a package ................................... 35 5.6.1 Uploading to ftp-master ........................... 35 5.6.2 Delayed uploads ................................. 35 5.6.3 Security uploads ................................. 36 5.6.4 Other upload queues ............................... 36 5.6.5 Notification that a new package has been installed .............. 36 5.7 Specifying the package section, subsection and priority ............... 37 5.8 Handling bugs ....................................... 37 5.8.1 Monitoring bugs ................................. 38 5.8.2 Responding to bugs ............................... 38 5.8.3 Bug housekeeping ................................ 39 5.8.4 When bugs are closed by new uploads .................... 40 5.8.5 Handling security-related bugs ......................... 41 5.9 Moving, removing, renaming, adopting, and orphaning packages ......... 45 5.9.1 Moving packages ................................. 45 5.9.2 Removing packages ............................... 46 5.9.3 Replacing or renaming packages ........................ 47 5.9.4 Orphaning a package .............................. 47 5.9.5 Adopting a package ............................... 48 5.10 Porting and being ported ................................. 48 5.10.1 Being kind to porters ............................... 48 5.10.2 Guidelines for porter uploads .......................... 50 5.10.3 Porting infrastructure and automation ..................... 51 5.10.4 When your package is not portable ....................... 52 5.11 Non-Maintainer Uploads (NMUs) ........................... 53 5.11.1 How to do a NMU ................................ 54 CONTENTS iv 5.11.2 NMU version numbering ............................ 55 5.11.3 Source NMUs must have a new changelog entry ............... 55 5.11.4 Source NMUs and the Bug Tracking System ................. 56 5.11.5 Building source NMUs .............................. 56 5.11.6 Acknowledging an NMU ............................ 56 5.11.7 NMU vs QA uploads ............................... 57 5.11.8 Who can do an NMU ............................... 57 5.11.9 Terminology .................................... 57 5.12 Collaborative maintenance ................................ 58 5.13 The testing distribution .................................. 59 5.13.1 Basics ........................................ 59 5.13.2 Updates from unstable .............................. 59 5.13.3 Direct updates to testing ............................. 62 5.13.4 Frequently asked questions ........................... 63 6 Best Packaging Practices 65 6.1 Best practices for debian/rules ........................... 65 6.1.1 Helper scripts ................................... 65 6.1.2 Separating your patches into multiple files .................. 66 6.1.3 Multiple binary packages ............................ 67 6.2 Best practices for debian/control .......................... 67 6.2.1 General guidelines for package descriptions ................. 67 6.2.2 The package synopsis, or short description .................. 68 6.2.3 The long description ............................... 69 6.2.4 Upstream home page ............................... 69 6.2.5 Version Control System location ........................ 70 6.3 Best practices for debian/changelog ........................ 71 6.3.1 Writing useful changelog entries ........................ 71 6.3.2 Common misconceptions about changelog entries .............. 71 6.3.3 Common errors in changelog entries ...................... 72 6.3.4 Supplementing changelogs with NEWS.Debian files ............. 73 CONTENTS v 6.4 Best practices for maintainer scripts .......................... 74 6.5 Configuration management with debconf ...................... 75 6.5.1 Do not abuse debconf .............................. 75 6.5.2 General recommendations for authors and translators ............ 75 6.5.3 Templates fields definition ............................ 78 6.5.4 Templates fields specific style guide ...................... 79 6.6 Internationalization .................................... 82 6.6.1 Handling debconf translations ......................... 82 6.6.2 Internationalized documentation ........................ 82 6.7 Common packaging situations ............................. 83 6.7.1 Packages using autoconf/automake .................... 83 6.7.2 Libraries ...................................... 83 6.7.3 Documentation .................................. 83 6.7.4 Specific types of packages ............................ 83 6.7.5 Architecture-independent data ......................... 84 6.7.6 Needing a certain locale during build ..................... 84 6.7.7 Make transition packages deborphan compliant ............... 85 6.7.8 Best practices for orig.tar.gz files ..................... 85 6.7.9 Best practices for debug packages ....................... 88 7 Beyond Packaging 89 7.1 Bug reporting ......................................
Recommended publications
  • Debian Developer's Reference Version 12.0, Released on 2021-09-01
    Debian Developer’s Reference Release 12.0 Developer’s Reference Team 2021-09-01 CONTENTS 1 Scope of This Document 3 2 Applying to Become a Member5 2.1 Getting started..............................................5 2.2 Debian mentors and sponsors......................................6 2.3 Registering as a Debian member.....................................6 3 Debian Developer's Duties 9 3.1 Package Maintainer's Duties.......................................9 3.1.1 Work towards the next stable release............................9 3.1.2 Maintain packages in stable .................................9 3.1.3 Manage release-critical bugs.................................. 10 3.1.4 Coordination with upstream developers............................ 10 3.2 Administrative Duties.......................................... 10 3.2.1 Maintaining your Debian information............................. 11 3.2.2 Maintaining your public key.................................. 11 3.2.3 Voting.............................................. 11 3.2.4 Going on vacation gracefully.................................. 12 3.2.5 Retiring............................................. 12 3.2.6 Returning after retirement................................... 13 4 Resources for Debian Members 15 4.1 Mailing lists............................................... 15 4.1.1 Basic rules for use....................................... 15 4.1.2 Core development mailing lists................................. 15 4.1.3 Special lists........................................... 16 4.1.4 Requesting new
    [Show full text]
  • Application of Ultimate Debian Database in Debian Pure Blends Harvesting Information About Packages for Specific Work fields
    Application of Ultimate Debian Database in Debian Pure Blends Harvesting information about packages for specific work fields Andreas Tille Debian Conference 9 Cáceres, July 26, 2009 Overview 1 Debian Pure Blends Short introduction Blends features Web tools 2 Ultimate Debian Database Short introduction Advantages of using UDD for Blends 3 Future Planned features for Blends TODO 2 / 22 Rename: CDD § Debian Pure Blends Term Custom Debian Distributions was always misunderstood Main misunderstanding: CDD was regarded as “something else than Debian” even if people were told that it is a concept inside Debian explicitly Dropped the misleading name in favour of a name where you just have to read the docs § Debian Pure Blend (in short Blend): a subset of Debian that is configured to support a particular target group out-of-the-box. 3 / 22 Reminder: Basic goal of Blends Debian > 22.000 packages Users interested in subset Groups of specialised users Easy installation and configuration While Debian stays general support specialists as well No derivative from Debian Basic idea: Do not make a separate distribution but make Debian fit for special purpose instead 4 / 22 Upstream - Debian Developer - User Tie a solid network of Debian developers, upstream developers (“developing experts”) and users Rationale: Experts in this field need help in build system / packaging Upstream anticipates enhancements of build system and security audit Finally support upstream developers to become Debian maintainers Penetrating specific work fields with Linux makes it even more
    [Show full text]
  • Debian's Perl Team from an End-User Perspective
    Getting Perl modules into Debian Debian's Perl team from an end-user perspective Tim Retout 11th September 2010 HantsLUG @ IBM Hursley Tim Retout pkg-perl for users What is the Debian Perl team? Maintain about 2000 Perl packages within Debian Both official Debian Developers and sponsees Around 70-80 committers,1 but most activity from a small core team Also indirectly contributes most of the Perl packages in Debian's derivatives (e.g. Ubuntu). 1http://www.ohloh.net/p/pkg-perl Tim Retout pkg-perl for users Using Perl on Debian How do you install Perl modules? apt-get install libfoo-perl Backports for older releases CPAN for unpackaged modules CPAN (the tool) is configured to play nicely with Debian packages, but does not install packages when satisfying dependencies. Tim Retout pkg-perl for users When a module isn't packaged If the Perl module you need is not available, you have several options: 1 Install it with CPAN, and handle future upgrades yourself. 2 File an RFP (Request for package) bug in Debian.2 3 Build yourself a private Debian package with dh-make-perl, and handle future upgrades yourself. 4 Get involved and contribute it back to Debian! Getting involved is easier than you think. 2http://pkg-perl.alioth.debian.org/howto/RFP.html Tim Retout pkg-perl for users Getting involved - tools The Perl team uses tools to speed up packaging. alioth.debian.org for team management git for most packages http://bugs.debian.org/ Package Entropy Tracker (PET) IRC (#debian-perl on OFTC) Two mailing lists - one for discussion, one to receive automated messages http://pkg-perl.alioth.debian.org/ links to all of these.
    [Show full text]
  • Debian 1 Debian
    Debian 1 Debian Debian Part of the Unix-like family Debian 7.0 (Wheezy) with GNOME 3 Company / developer Debian Project Working state Current Source model Open-source Initial release September 15, 1993 [1] Latest release 7.5 (Wheezy) (April 26, 2014) [±] [2] Latest preview 8.0 (Jessie) (perpetual beta) [±] Available in 73 languages Update method APT (several front-ends available) Package manager dpkg Supported platforms IA-32, x86-64, PowerPC, SPARC, ARM, MIPS, S390 Kernel type Monolithic: Linux, kFreeBSD Micro: Hurd (unofficial) Userland GNU Default user interface GNOME License Free software (mainly GPL). Proprietary software in a non-default area. [3] Official website www.debian.org Debian (/ˈdɛbiən/) is an operating system composed of free software mostly carrying the GNU General Public License, and developed by an Internet collaboration of volunteers aligned with the Debian Project. It is one of the most popular Linux distributions for personal computers and network servers, and has been used as a base for other Linux distributions. Debian 2 Debian was announced in 1993 by Ian Murdock, and the first stable release was made in 1996. The development is carried out by a team of volunteers guided by a project leader and three foundational documents. New distributions are updated continually and the next candidate is released after a time-based freeze. As one of the earliest distributions in Linux's history, Debian was envisioned to be developed openly in the spirit of Linux and GNU. This vision drew the attention and support of the Free Software Foundation, who sponsored the project for the first part of its life.
    [Show full text]
  • Debian Packaging Tutorial
    Debian Packaging Tutorial Lucas Nussbaum [email protected] version 0.27 – 2021-01-08 Debian Packaging Tutorial 1 / 89 About this tutorial I Goal: tell you what you really need to know about Debian packaging I Modify existing packages I Create your own packages I Interact with the Debian community I Become a Debian power-user I Covers the most important points, but is not complete I You will need to read more documentation I Most of the content also applies to Debian derivative distributions I That includes Ubuntu Debian Packaging Tutorial 2 / 89 Outline 1 Introduction 2 Creating source packages 3 Building and testing packages 4 Practical session 1: modifying the grep package 5 Advanced packaging topics 6 Maintaining packages in Debian 7 Conclusions 8 Additional practical sessions 9 Answers to practical sessions Debian Packaging Tutorial 3 / 89 Outline 1 Introduction 2 Creating source packages 3 Building and testing packages 4 Practical session 1: modifying the grep package 5 Advanced packaging topics 6 Maintaining packages in Debian 7 Conclusions 8 Additional practical sessions 9 Answers to practical sessions Debian Packaging Tutorial 4 / 89 Debian I GNU/Linux distribution I 1st major distro developed “openly in the spirit of GNU” I Non-commercial, built collaboratively by over 1,000 volunteers I 3 main features: I Quality – culture of technical excellence We release when it’s ready I Freedom – devs and users bound by the Social Contract Promoting the culture of Free Software since 1993 I Independence – no (single)
    [Show full text]
  • A Debian Pure Blend for Astronomy and Astrophysics
    The Debian Astro project A Debian Pure Blend for astronomy and astrophysics Ole Streicher [email protected] Zeuthen, 2018-02-13 Ole Streicher (AIP Potsdam) The Debian Astro project Zeuthen, 2018-02-13 1 / 23 Debian GNU/Linux Free Linux based operating system One of the oldest distributions (founded 1993) Free as in \Free Speech" Base: Social Contract; Debian Free Software Guidelines > 50:000 software packages > 1:000 official developers Base for many derivatives: Ubuntu, Mint, ... Current stable version: Debian 9 (Stretch), since June 2017 Ole Streicher (AIP Potsdam) The Debian Astro project Zeuthen, 2018-02-13 2 / 23 The Debian Astro Pure Blend Blended tea: a combination of different kinds of teas to guarantee consistent quality (Wikipedia) Method to organize Debian astronomy packages currently 294 packages, (more in preparation) 19 metapackages Web page, \tasks" pages Handle citations, ASCL entries Completely integrated into Debian (Pure) First release with Debian Stretch (June 2017) Ole Streicher (AIP Potsdam) The Debian Astro project Zeuthen, 2018-02-13 3 / 23 Debian Pure Blends Debian Astro - Astronomy and astrophysics Debian GIS - Geographical Information Systems DebiChem - Chemistry Debian Med - Strong focus on Microbiology NeuroDebian - Neuroscience Debian Science - \Umbrella" blend for sciences Debian Edu - Education of all kind Debian Games, Debian Junior, Debian Multimedia, Hamradio, ... Ole Streicher (AIP Potsdam) The Debian Astro project Zeuthen, 2018-02-13 4 / 23 History of Debian Astro First packages: saoimage (1999), cfitsio
    [Show full text]
  • Debian Secrets Power Tools for Power Users
    About this talk Changing system behaviour Searching Fooling the package system Anticipating and correcting problems Debian menu Debian Secrets Power tools for Power users Wouter Verhelst FOSDEM 2010 Wouter Verhelst Debian Secrets Idea: compare Debian-specic features against other distributions' features Help! About this talk Changing system behaviour Searching Fooling the package system Anticipating and correcting problems Debian menu About this talk Recycled from DebConf8 DebianDay Wouter Verhelst Debian Secrets Help! About this talk Changing system behaviour Searching Fooling the package system Anticipating and correcting problems Debian menu About this talk Recycled from DebConf8 DebianDay Idea: compare Debian-specic features against other distributions' features Wouter Verhelst Debian Secrets About this talk Changing system behaviour Searching Fooling the package system Anticipating and correcting problems Debian menu About this talk Recycled from DebConf8 DebianDay Idea: compare Debian-specic features against other distributions' features Help! Wouter Verhelst Debian Secrets update-alternatives −−config x-terminal-emulator more info: man update-alternatives About this talk Changing system behaviour Searching update-alternatives Fooling the package system dpkg-statoverride Anticipating and correcting problems Debian menu update-alternatives multiple packages providing a particular command Wouter Verhelst Debian Secrets more info: man update-alternatives About this talk Changing system behaviour Searching update-alternatives Fooling
    [Show full text]
  • Apt-Get Install Cran Bioc: on Automated Builds of 1700 R Packages for Debian
    apt-get install cran bioc: On automated builds of 1700 R packages for Debian Dirk Eddelbuettel1 David Vernazobres2 Albrecht Gebhard 3 Steffen Möller 4 1Debian Project 2Universität Münster 3Universität Klagenfurt 4Universität Lübeck UseR! 2007 – Iowa State University, August 8 - 10, 2007 Eddelbuettel, Vernazobres et al (Debian etc) apt-get install cran bioc UseR 2007 1 / 15 Outline 1 Background and Motivation 2 Bringing both worlds together 3 What is behind it? 4 Debian Pkg-BioC Team 5 Where to go from here? 6 Conclusion Eddelbuettel, Vernazobres et al (Debian etc) apt-get install cran bioc UseR 2007 2 / 15 R – and its repos An open statistical language / environment – with lots of excellent code contributions To restate a what is well known at useR! 2007: R has become a standard for statistical applications and research As “success has many fathers”, several key drivers can be identified as to whyR has done so remarkably well However, we would like to stress repos here CRAN has been one of the drivers: an open yet rigourously QA’ed repostory which has experienced tremendous growth BioConductor has become a key technology enabler in bioinformatics, and provides a repo for that community Omegahat was meant to be a driver for the ’next R’ and is still an excellent experimental area Eddelbuettel, Vernazobres et al (Debian etc) apt-get install cran bioc UseR 2007 3 / 15 CRAN Packages Exponential Growth Number of distinct CRAN packages through time 1200 1000 800 600 400 200 0 1998 2000 2002 2004 2006 The count is based on files found at CRAN/src/contrib
    [Show full text]
  • A Brief History of Debian I
    A Brief History of Debian i A Brief History of Debian A Brief History of Debian ii 1999-2020Debian Documentation Team [email protected] Debian Documentation Team This document may be freely redistributed or modified in any form provided your changes are clearly documented. This document may be redistributed for fee or free, and may be modified (including translation from one type of media or file format to another or from one spoken language to another) provided that all changes from the original are clearly marked as such. Significant contributions were made to this document by • Javier Fernández-Sanguino [email protected] • Bdale Garbee [email protected] • Hartmut Koptein [email protected] • Nils Lohner [email protected] • Will Lowe [email protected] • Bill Mitchell [email protected] • Ian Murdock • Martin Schulze [email protected] • Craig Small [email protected] This document is primarily maintained by Bdale Garbee [email protected]. A Brief History of Debian iii COLLABORATORS TITLE : A Brief History of Debian ACTION NAME DATE SIGNATURE WRITTEN BY September 14, 2020 REVISION HISTORY NUMBER DATE DESCRIPTION NAME A Brief History of Debian iv Contents 1 Introduction -- What is the Debian Project? 1 1.1 In the Beginning ................................................... 1 1.2 Pronouncing Debian ................................................. 1 2 Leadership 2 3 Debian Releases 3 4 A Detailed History 6 4.1 The 0.x Releases ................................................... 6 4.1.1 The Early Debian Packaging System ..................................... 7 4.2 The 1.x Releases ................................................... 7 4.3 The 2.x Releases ................................................... 8 4.4 The 3.x Releases ................................................... 8 4.5 The 4.x Releases ..................................................
    [Show full text]
  • Pbuilder Documentation Release 0.213
    pbuilder Documentation Release 0.213 PBuilder Team May 24, 2017 Contents 1 Table Of Contents 3 2 Indices and tables 23 i ii pbuilder Documentation, Release 0.213 Note: This is not official documentation: it’s just an attempt to format it for sphinx so ReadTheDocs service could be used. The official documentation can be browsed at http://pbuilder.alioth.debian.org/ This particular document is also available as: • EPub • PDF Last built: May 24, 2017 Contents 1 pbuilder Documentation, Release 0.213 2 Contents CHAPTER 1 Table Of Contents Introducing pbuilder Aims of pbuilder pbuilder stands for Personal Builder, and it is an automatic Debian Package Building system for personal develop- ment workstation environments. pbuilder aims to be an easy-to-setup system for auto-building Debian packages inside a clean-room environment, so that it is possible to verify that a package can be built on most Debian installa- tions. The clean-room environment is achieved through the use of a base chroot image, so that only minimal packages will be installed inside the chroot. The Debian distribution consists of free software accompanied with source. The source code within Debian’s “main” section must build within Debian “main”, with only the explicitly specified build-dependencies installed. The primary aim of pbuilder is different from other auto-building systems in Debian in that its aim is not to try to build as many packages as possible. It does not try to guess what a package needs, and in most cases it tries the worst choice of all if there is a choice to be made.
    [Show full text]
  • The Debian Administrator's Handbook
    The Debian Administrator's Handbook "The Debian Administrator's Handbook" is the title of the translation of the French best- seller known as Cahier de l'Admin Debian. Written by two Debian developers — Raphaël Hertzog and Roland Mas — it's a fantastic resource for all users of a Debian-based distribution. Given that traditional editors did not want to take the risk to make this translation, we decided to do the translation ourselves and to self-publish the result. But we want to go further than this, we want the result to be freely available (that is under the terms of a license compatible with the Debian Free Software Guidelines of course). However it's very difficult to spend several months of work without income. That's why we're running a fundraising campaign. Thanks to the first 380 supporters, we reached our first goal and we're now sure that the translation will happen. But your support is still very important to reach the second goal: the liberation of the book. It's easier to support a project that has already achieved something, instead of having only promised it. That's why we're releasing this sample chapter of the book. We hope that you'll enjoy it and that you'll join the hundreds of people who pledged some money towards the liberation of the book. Click here and contribute to the liberation fund Raphaël Hertzog & Roland Mas, Free Sample of The Debian Administrator's Handbook — http://debian-handbook.info Chapter 6. Maintenance and Updates: The APT Tools What makes Debian so popular with administrators is how easily software can be installed and how easily the whole system can be updated.
    [Show full text]
  • Infraestructura Distribuida Para La Construcción De Paquetes Debian
    INFRAESTRUCTURA DISTRIBUIDA PARA LA CONSTRUCCIÓN DE PAQUETES DEBIAN UNIVERSIDAD DE CASTILLA-LA MANCHA ESCUELA SUPERIOR DE INFORMÁTICA INGENIERÍA EN INFORMÁTICA PROYECTO FIN DE CARRERA Infraestructura distribuida para la construcción de paquetes Debian José Luis Sanroma Tato Septiembre, 2014 UNIVERSIDAD DE CASTILLA-LA MANCHA ESCUELA SUPERIOR DE INFORMÁTICA Departamento de Tecnologías y Sistemas de Información PROYECTO FIN DE CARRERA Infraestructura distribuida para la construcción de paquetes Debian Autor: José Luis Sanroma Tato Director: Dr. Francisco Moya Fernández Septiembre, 2014 José Luis Sanroma Tato Ciudad Real – Spain E-mail: [email protected] Web site: http://www.icebuilder.org c 2014 José Luis Sanroma Tato Permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation License, Version 1.3 or any later version published by the Free Software Foundation; with no Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A copy of the license is included in the section entitled "GNU Free Documentation License". Se permite la copia, distribución y/o modificación de este documento bajo los términos de la Licencia de Documentación Libre GNU, versión 1.3 o cualquier versión posterior publicada por la Free Software Foundation; sin secciones invariantes. Una copia de esta licencia esta incluida en el apéndice titulado «GNU Free Documentation License». Muchos de los nombres usados por las compañías para diferenciar sus productos y servicios son reclamados como marcas registradas. Allí donde estos nombres aparezcan en este documento, y cuando el autor haya sido informado de esas marcas registradas, los nombres estarán escritos en mayúsculas o como nombres propios.
    [Show full text]