software-management-guide/devel/en_US concepts.xml, 1.1, 1.2 doc-entities.ent, 1.1, NONE doc-entities.ent~, 1.1, NONE fdp-entities.ent, 1.1, NONE
Bart Couvreur (couf)
fedora-docs-commits at redhat.com
Wed Apr 30 19:47:00 UTC 2008
Author: couf
Update of /cvs/docs/software-management-guide/devel/en_US
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv14854
Modified Files:
concepts.xml
Removed Files:
doc-entities.ent doc-entities.ent~ fdp-entities.ent
Log Message:
Removing unneeded files + small update to accomodate new combined repositories
Index: concepts.xml
===================================================================
RCS file: /cvs/docs/software-management-guide/devel/en_US/concepts.xml,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- concepts.xml 5 Mar 2008 22:32:57 -0000 1.1
+++ concepts.xml 30 Apr 2008 19:46:57 -0000 1.2
@@ -1,5 +1,7 @@
<?xml version="1.0" encoding="utf-8"?>
+
<!-- $Id: -->
+
<!DOCTYPE section PUBLIC "-//OASIS//DTD DocBook XML V4.4//EN"
"http://www.oasis-open.org/docbook/xml/4.4/docbookx.dtd"
[
@@ -8,165 +10,226 @@
<!ENTITY % FDP-ENTITIES SYSTEM "fdp-entities.ent">
%FDP-ENTITIES;
]>
+
<section id="sn-Concepts">
<title>Software Management Concepts</title>
+
<section id="sn-AboutPackages">
<title>About Packages</title>
- <para>Fedora software and documentation is supplied in the form of
- files called RPM
- <firstterm>packages</firstterm>. Each package is a compressed
- archive containing product information, program files, icons,
- documentation and management scripts. Management applications use
- these files to safely locate, install, update and remove software.
- For example, the Fedora installation process uses the packages
- supplied with Fedora to build or upgrade a system to your
- requirements.</para>
- <para>Packages also include a digital signature to prove their
- source. Software management utilities verify this digital signature
- by using a GPG
- <firstterm>public key</firstterm>. The
- <command>yum</command> and
- <command>rpm</command> utilities share a common
- <firstterm>keyring</firstterm> that stores all of the public keys
- for approved package sources. The system administrator configures
- these approved package sources.</para>
+
+ <para>
+ Fedora software and documentation is supplied in the form of files
+ called RPM <firstterm>packages</firstterm>. Each package is a
+ compressed archive containing product information, program files,
+ icons, documentation and management scripts. Management
+ applications use these files to safely locate, install, update and
+ remove software. For example, the Fedora installation process uses
+ the packages supplied with Fedora to build or upgrade a system to
+ your requirements.
+ </para>
+
+ <para>
+ Packages also include a digital signature to prove their source.
+ Software management utilities verify this digital signature by
+ using a GPG <firstterm>public key</firstterm>. The
+ <command>yum</command> and <command>rpm</command> utilities share
+ a common <firstterm>keyring</firstterm> that stores all of the
+ public keys for approved package sources. The system administrator
+ configures these approved package sources.
+ </para>
+
<note>
- <title>All Fedora Packages are Free and Open Source
- Software</title>
- <para>All of the software provided by the Fedora Project is Free
- and open source software. You may download and install Fedora
- packages on as many systems as desired.</para>
+ <title>All Fedora Packages are Free and Open Source Software</title>
+
+ <para>
+ All of the software provided by the Fedora Project is Free and
+ open source software. You may download and install Fedora
+ packages on as many systems as desired.
+ </para>
</note>
</section>
+
<section id="sn-AboutRepositories">
<title>About Repositories</title>
- <para>A
- <firstterm>repository</firstterm> is a prepared directory or Web
- site that contains software packages and index files. Software
- management utilities such as
- <package>yum</package> automatically locate and obtain the correct
- RPM packages from these repositories. This method frees you from
- having to manually find and install new applications or updates.
- You may use a single command to update all system software, or
- search for new software by specifying criteria.</para>
- <para>A network of servers provide several repositories for each
- version of Fedora. The package management utilities in Fedora are
- already configured to use three of these repositories:</para>
- <para>Base</para>
- <itemizedlist>
- <listitem>
- <para>The packages that make up a Fedora release, as it is on
- disc</para>
- </listitem>
- </itemizedlist>
- <para>Updates</para>
+
+ <para>
+ A <firstterm>repository</firstterm> is a prepared directory or Web
+ site that contains software packages and index files. Software
+ management utilities such as
+ <package>yum</package>
+ automatically locate and obtain the correct RPM packages from
+ these repositories. This method frees you from having to manually
+ find and install new applications or updates. You may use a single
+ command to update all system software, or search for new software
+ by specifying criteria.
+ </para>
+
+ <para>
+ A network of servers provide several repositories for each version
+ of Fedora. The package management utilities in Fedora are already
+ configured to use three of these repositories:
+ </para>
+
+ <para>
+ Fedora
+ </para>
+
<itemizedlist>
<listitem>
- <para>Updated versions of packages that are provided in
- Base</para>
+ <para>
+ The packages that make up a Fedora release. This includes all
+ packages included on disc.
+ </para>
</listitem>
</itemizedlist>
- <para>Extras</para>
+
+ <para>
+ Updates
+ </para>
+
<itemizedlist>
<listitem>
- <para>Packages for a large selection of additional
- software</para>
+ <para>
+ Updated versions of packages that are provided in Fedora
+ </para>
</listitem>
</itemizedlist>
+
<warning>
<title>Fedora Development Repositories</title>
- <para>Fedora also includes settings for several alternative
- repositories. These provide packages for various types of test
- system, and replace one or more of the standard repositories.
- Only enable support for one of the following repositories if you
- test or develop Fedora software:
- <systemitem>fedora-devel</systemitem> (Rawhide),
- <systemitem>fedora-extras-devel</systemitem>, and
- <systemitem>updates-testing</systemitem>.</para>
+
+ <para>
+ Fedora also includes settings for several alternative
+ repositories. These provide packages for various types of test
+ system, and replace one or more of the standard repositories.
+ Only enable support for one of the following repositories if you
+ test or develop Fedora software:
+ <systemitem>development</systemitem> (Rawhide)
+ and <systemitem>updates-testing</systemitem>.
+ </para>
</warning>
- <para>Third-party software developers also provide repositories for
- their Fedora compatible packages. To learn how to configure your
- Fedora system to use third-party repositories, read
- <xref linkend="sn-ConfiguringRepositories" />.</para>
- <para>You may also use the
- <firstterm>package groups</firstterm> provided by the Fedora
- repositories to manage related packages as sets. Some third-party
- repositories add packages to these groups, or provide their
- packages as additional groups.</para>
+
+ <para>
+ Third-party software developers also provide repositories for
+ their Fedora compatible packages. To learn how to configure your
+ Fedora system to use third-party repositories, read
+ <xref linkend="sn-ConfiguringRepositories" />.
+ </para>
+
+ <para>
+ You may also use the <firstterm>package groups</firstterm>
+ provided by the Fedora repositories to manage related packages as
+ sets. Some third-party repositories add packages to these groups,
+ or provide their packages as additional groups.
+ </para>
<tip>
<title>Available Package Groups</title>
- <para>To view a list of all of the available package groups for
- your Fedora system, run the command
- <command>su -c 'yum grouplist'</command>.</para>
+ <para>
+ To view a list of all of the available package groups for your
+ Fedora system, run the command <command>su -c 'yum
+ grouplist'</command>.
+ </para>
</tip>
- <para>Use repositories to ensure that you always receive current
- versions of software. If several versions of the same package are
- available, your management utility automatically selects the latest
- version.</para>
+ <para>
+ Use repositories to ensure that you always receive current
+ versions of software. If several versions of the same package are
+ available, your management utility automatically selects the
+ latest version.
+ </para>
+
<warning>
<title>Manually Installing Software</title>
- <para>Install software using manual methods only when you are
- confident there is no repository which can currently provide it.
- You may have to manage that software with manual methods, instead
- of with Fedora software management utilities.</para>
+
+ <para>
+ Install software using manual methods only when you are
+ confident there is no repository which can currently provide it.
+ You may have to manage that software with manual methods,
+ instead of with Fedora software management utilities.
+ </para>
</warning>
- <para>The
- <command>yum</command> commands shown in this document use
- repositories as package sources. Refer to
- <xref linkend="sn-IsolatedInstall" />for details of using
- <command>yum</command> to install software from a package
- file.</para>
+
+ <para>
+ The <command>yum</command> commands shown in this document use
+ repositories as package sources. Refer to
+ <xref linkend="sn-IsolatedInstall" />for details of using
+ <command>yum</command> to install software from a package file.
+ </para>
+
<para />
</section>
+
<section id="sn-AboutDependencies">
<title>About Dependencies</title>
- <para>Some of the files installed on a Fedora distribution are
- <firstterm>libraries</firstterm> which may provide functions to
- multiple applications. When an application requires a specific
- library, the package which contains that library is a
- <firstterm>dependency</firstterm>. To properly install a package,
- Fedora must first satisfy its dependencies. The dependency
- information for a RPM package is stored within the RPM file.</para>
- <para>The
- <application>yum</application> utility uses package dependency data
- to ensure that all of requirements for an application are met
- during installation. It automatically installs the packages for any
- dependencies not already present on your system. If a new
- application has requirements that conflict with existing software,
- <application>yum</application> aborts without making any changes to
- your system.</para>
+
+ <para>
+ Some of the files installed on a Fedora distribution are
+ <firstterm>libraries</firstterm> which may provide functions to
+ multiple applications. When an application requires a specific
+ library, the package which contains that library is a
+ <firstterm>dependency</firstterm>. To properly install a package,
+ Fedora must first satisfy its dependencies. The dependency
+ information for a RPM package is stored within the RPM file.
+ </para>
+
+ <para>
+ The <application>yum</application> utility uses package dependency
+ data to ensure that all of requirements for an application are met
+ during installation. It automatically installs the packages for
+ any dependencies not already present on your system. If a new
+ application has requirements that conflict with existing software,
+ <application>yum</application> aborts without making any changes
+ to your system.
+ </para>
</section>
+
<section id="sn-UnderstandingPackageNames">
<title>Understanding Package Names</title>
- <para>Each package file has a long name that indicates several key
- pieces of information. For example, this is the full name of a
- <package>tsclient</package> package:</para>
+
+ <para>
+ Each package file has a long name that indicates several key
+ pieces of information. For example, this is the full name of a
+ <package>tsclient</package>
+ package:
+ </para>
+
<para>
<filename>tsclient-0.132-6.i386.rpm</filename>
</para>
- <para>Management utilities commonly refer to packages with one of
- three formats:</para>
+
+ <para>
+ Management utilities commonly refer to packages with one of three
+ formats:
+ </para>
+
<itemizedlist>
<listitem>
- <para>Package name:
- <literal>tsclient</literal></para>
+ <para>
+ Package name: <literal>tsclient</literal>
+ </para>
</listitem>
<listitem>
- <para>Package name with version and release numbers:
- <literal>tsclient-0.132-6</literal></para>
+ <para>
+ Package name with version and release numbers:
+ <literal>tsclient-0.132-6</literal>
+ </para>
</listitem>
<listitem>
- <para>Package name with hardware architecture:
- <literal>tsclient.i386</literal></para>
+ <para>
+ Package name with hardware architecture:
+ <literal>tsclient.i386</literal>
+ </para>
</listitem>
</itemizedlist>
- <para>For clarity,
- <command>yum</command> lists packages in the format
- <package>name.architecture</package>. Repositories also commonly
- store packages in separate directories by architecture. In each
- case, the hardware architecture specified for the package is the
- <emphasis>minimum</emphasis> type of machine required to use the
- package.</para>
+
+ <para>
+ For clarity, <command>yum</command> lists packages in the format
+ <package>name.architecture</package>
+ . Repositories also commonly store packages in separate
+ directories by architecture. In each case, the hardware
+ architecture specified for the package is the
+ <emphasis>minimum</emphasis> type of machine required to use the
+ package.
+ </para>
<segmentedlist>
<segtitle>Architecture</segtitle>
<segtitle>Compatibility</segtitle>
@@ -189,49 +252,56 @@
Opterons</seg>
</seglistitem>
</segmentedlist>
- <para>Some software may be optimized for particular types of
- Intel-compatible machine. Separate packages may be provided for
- <systemitem>i386</systemitem>,
- <systemitem>i586</systemitem>,
- <systemitem>i686</systemitem> and
- <systemitem>x86_64</systemitem> computers. A machine with at least
- an Intel Pentium, VIA C3 or compatible CPU may use
- <systemitem>i586</systemitem> packages. Computers with an Intel
- Pentium Pro and above, or a current model of AMD chip, may use
- <systemitem>i686</systemitem> packages.</para>
- <para>Use the short name of the package for
- <command>yum</command> commands. This causes
- <command>yum</command> to automatically select the most recent
- package in the repositories that matches the hardware architecture
- of your computer.</para>
- <para>Specify a package with other name formats to override the
- default behavior and force
- <command>yum</command> to use the package that matches that version
- or architecture. Only override
- <command>yum</command> when you know that the default package
- selection has a bug or other fault that makes it unsuitable for
- installation.</para>
+ <para>
+ Some software may be optimized for particular types of
+ Intel-compatible machine. Separate packages may be provided for
+ <systemitem>i386</systemitem>, <systemitem>i586</systemitem>,
+ <systemitem>i686</systemitem> and <systemitem>x86_64</systemitem>
+ computers. A machine with at least an Intel Pentium, VIA C3 or
+ compatible CPU may use <systemitem>i586</systemitem> packages.
+ Computers with an Intel Pentium Pro and above, or a current model
+ of AMD chip, may use <systemitem>i686</systemitem> packages.
+ </para>
+
+ <para>
+ Use the short name of the package for <command>yum</command>
+ commands. This causes <command>yum</command> to automatically
+ select the most recent package in the repositories that matches
+ the hardware architecture of your computer.
+ </para>
+
+ <para>
+ Specify a package with other name formats to override the default
+ behavior and force <command>yum</command> to use the package that
+ matches that version or architecture. Only override
+ <command>yum</command> when you know that the default package
+ selection has a bug or other fault that makes it unsuitable for
+ installation.
+ </para>
+
<important>
<title>Package Names</title>
- <para>You may use any of the following formats to specify a
- package in a
- <application>yum</application> operation:
- <literal>name</literal>,
- <literal>name.architecture</literal>,
- <literal>name-version</literal>,
- <literal>name-version-release</literal>,
- <literal>name-version-release.architecture</literal>, and
- <literal>
- epoch:name-version-release.architecture</literal>.</para>
+
+ <para>
+ You may use any of the following formats to specify a package in
+ a <application>yum</application> operation:
+ <literal>name</literal>, <literal>name.architecture</literal>,
+ <literal>name-version</literal>,
+ <literal>name-version-release</literal>,
+ <literal>name-version-release.architecture</literal>, and
+ <literal>epoch:name-version-release.architecture</literal>.
+ </para>
</important>
</section>
</section>
+
<!--
Local variables:
mode: xml
fill-column: 72
End:
-->
+
<!--
vim: softtabstop=2:shiftwidth=2:expandtab:textwidth=72
-->
--- doc-entities.ent DELETED ---
--- doc-entities.ent~ DELETED ---
--- fdp-entities.ent DELETED ---
More information about the Fedora-docs-commits
mailing list