Bonjour, Quelques petits changements dans la section sur l'étiquettage des paquets plus un changement de licence du document. La branche 1.9.x est aussi concerné par ce changement de licence avec le meme texte je ne passerai donc pas par une RFR pour l'autre. Je joins le diff de la version anglaise. -- Tout est mystère dans l'amour. -+- Jean de La Fontaine (1621-1695), L'Amour et la Folie (Fables XII.14) -+-
Index: apt-howto/branches/1.x/apt-howto.en.sgml =================================================================== --- apt-howto/branches/1.x/apt-howto.en.sgml (revision 22) +++ apt-howto/branches/1.x/apt-howto.en.sgml (revision 43) @@ -9,7 +9,7 @@ <name>Gustavo Noronha Silva</name> <email>kov@debian.org</email> </author> -<version>1.8.8 - September 2004</version> +<version>1.8.10 - November 2004</version> <abstract> This document intends to provide the user with a good understanding @@ -25,9 +25,26 @@ Copyright © 2001, 2002, 2003, 2004 Gustavo Noronha Silva </copyrightsummary> <p> -This manual is licensed under the terms of the GNU FDL (Free Documentation -License). It has been written in the hope that it will be useful to the -community but it comes with no warranty; use it at your own risk. +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. +</p> + +<p> +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. +</p> + +<p> +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 General Public Licence. You can also +obtain it by writing to the Free Software Foundation, Inc., 59 Temple +Place - Suite 330, Boston, MA 02111-1307, USA. +</p> </copyright> <toc> @@ -834,7 +851,7 @@ <em>not</em> be used by inexperienced users or by those who need proven stability. <p> -The `testing' distribution is not necessarily best than `unstable', +The `testing' distribution is not necessarily better than `unstable', because it does not receive security updates quickly. For servers and other production systems stable should always be used. </sect> @@ -888,27 +905,54 @@ soon as they are made available. Note that if you modified the package you won't want to do things this way. <p> -The <tt>Pin-Priority</tt> field is optional; if not specified, it -defaults to 989. +The pin priority helps determine whether a package matching the "Packages:" +and "Pin:" lines will be installed, with higher priorities making it more +likely that a matching package will be installed. You can read +<manref name="apt_preferences" section="7"> for a thorough discussion of +priorities, but a few examples should give the basic idea. The following +describes the effect of setting the priority field to different values in +the sylpheed example above. +</p> +<taglist> +<tag>1001</tag> +<item> + Sylpheed version 0.4.99 will never be replaced by apt. If available, +apt will install version 0.4.99 even if it would replace an installed +package with a higher version. Only packages of priority greater than +1000 will ever downgrade an existing package. +</item> +<tag>1000</tag> +<item> +The effect is the same as priority 1001, except that apt will refuse +to downgrade an installed version to 0.4.99 +</item> +<tag>990</tag> +<item> +Version 0.4.99 will be replaced only by a higher version available +from a release designated as preferred using the +"APT::Default-Release" variable (see <ref id="default-version">, +above). +</item> +<tag>500</tag> +<item> +Any version higher than 0.4.99 of sylpheed which is available from any +release will take preference over version 0.4.99, but 0.4.99 will +still be preferred to a lower version. +</item> +<tag>100</tag> +<item> +Higher versions of sylpheed available from any release will take +preference over version 0.4.99, as will any installed higher version +of slypheed; so 0.4.99 will be installed only if no version is +installed already. This is the priority of installed packages. +</item> +<tag>-1</tag> +<item> +Negative priorities are allowed as well, and prevent 0.4.99 from ever +being installed. +</item> +</taglist> <p> -Let's take a look at how pin priorities work. A priority lower than 0 -indicates that the package should never be installed. Priorities 0 to -100 denote packages that are not installed and that have no available -versions. These won't come into the version-choosing process. Priority -100 is the priority assigned to an installed package - for the installed -version of a package to be replaced by a different version, the -replacement must have a priority greater than 100. -<p> -Priorities above 100 indicate that a package should be installed. -Typically, the installed version of a package is changed only to upgrade -it to a newer version. Any priority between 100 and 1000 (inclusive) -indicates this typical behavior. A package with such a priority will -not downgrade to an available version with a lower version number. For -instance, if I have sylpheed 0.5.3 installed and define a pin on -sylpheed 0.4.99 with priority 999, package 0.4.99 will <em>not</em> be -installed to satisfy the pin. To make a package "downgradable", to -satisfy the pin, it needs possess a priority greater than 1000. -<p> A pin can be specified on a package's <tt>version</tt>, <tt>release</tt> or <tt>origin</tt>. <p>
Attachment:
apt-howto.fr.sgml.gz
Description: GNU Zip compressed data