rpm-guide rpm-guide-using-rpm-en.xml,1.5,1.6
by fedora-docs-commits@redhat.com
Author: elliss
Update of /cvs/docs/rpm-guide
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv24834
Modified Files:
rpm-guide-using-rpm-en.xml
Log Message:
Tagged to FDP standards.
View full diff with command:
/usr/bin/cvs -f diff -kk -u -N -r 1.5 -r 1.6 rpm-guide-using-rpm-en.xml
Index: rpm-guide-using-rpm-en.xml
===================================================================
RCS file: /cvs/docs/rpm-guide/rpm-guide-using-rpm-en.xml,v
retrieving revision 1.5
retrieving revision 1.6
diff -u -r1.5 -r1.6
--- rpm-guide-using-rpm-en.xml 14 Nov 2005 21:55:05 -0000 1.5
+++ rpm-guide-using-rpm-en.xml 20 Nov 2005 19:20:15 -0000 1.6
@@ -27,19 +27,20 @@
installing a package, but there���s a lot more you can do. For
example, you can install packages from remote sites using HTTP or
FTP to download the package to install. There are quite a few other
- rpm options you can use to get information and feedback on
- installation, for example.
+ <command>rpm</command> options you can use to get information and
+ feedback on installation, for example.
</para>
<sect1>
- <title>The rpm Command</title>
+ <title>The <command>rpm</command> Command</title>
<para>
- Just about everything you do with RPM requires the rpm command. As
- a nice added benefit, just about everything you do with RPM
- requires a single invocation of the rpm command. That means common
- tasks such as installing and removing software can be done quickly
- and efficiently. The basics of the rpm command are not very hard,
- and you can perform the basic tasks within a few minutes of
- reading this chapter.
+ Just about everything you do with RPM requires the
+ <command>rpm</command> command. As a nice added benefit, just
+ about everything you do with RPM requires a single invocation of
+ the <command>rpm</command> command. That means common tasks such
+ as installing and removing software can be done quickly and
+ efficiently. The basics of the <command>rpm</command> command are
+ not very hard, and you can perform the basic tasks within a few
+ minutes of reading this chapter.
</para>
</sect1>
<sect1>
@@ -47,19 +48,20 @@
<para>
To install software, you need something to install. Typically,
this is a file packaged as RPM, using a file-name extension of
- .rpm. Of course, this isn���t required, but just about every RPM
- package is stored in a file with a .rpm extension. For example,
- the following file holds an RPM package, ready to be installed:
+ <filename>rpm</filename>. Of course, this isn���t required, but
+ just about every RPM package is stored in a file with a
+ <filename>rpm</filename> extension. For example, the following
+ file holds an RPM package, ready to be installed:
</para>
<para>
- jikes-1.16-1.i386.rpm
+ <filename>jikes-1.16-1.i386.rpm</filename>
</para>
<para>
- This package holds an application named jikes (a Java language
- compiler application). From the discussion in the last two
- chapters, you should be able to determine the version of the
- program this RPM holds and which release of the RPM package this
- represents.
+ This package holds an application named <command>jikes</command>
+ (a Java language compiler application). From the discussion in the
+ last two chapters, you should be able to determine the version of
+ the program this RPM holds and which release of the RPM package
+ this represents.
</para>
<para>
Other RPMs hold sources, the program source codes used to create
@@ -67,194 +69,218 @@
file holds a source RPM:
</para>
<para>
- jikes-1.16-1.src.rpm
+ <filename>jikes-1.16-1.src.rpm</filename>
</para>
<para>
- The src in the package name is short for source. This file-naming
- convention is not required, but is used by just about all source
- code packages. (Following conventions helps other administrators
- know what to expect.)
- </para>
- <para>
- Cross Reference
- </para>
- <para>
- <xref linkend="ch-creating-rpms"/> and
- <xref linkend="ch-rpmbuild"/> cover building RPMs from source
- RPMs.
- </para>
- <para>
- The rpm command provides three main operations for upgrading and
- installing packages:
- </para>
- <para>
- An upgrade operation means installing a new version of a package
- and removing all previous versions of the same package. If you
- have not installed a package previously, the upgrade operation
- will install the package.
- </para>
- <para>
- A freshen operation means to install a new version of a package
- only if you have already installed another version of the package.
- </para>
- <para>
- An install operation installs a package for the first time. It
- also, through special command-line parameters, allows you to
- install multiple versions of a package, usually not what you want.
- So, in the vast majority of cases, you want to run the upgrade
- operation for all package installations.
+ The <filename>src</filename> in the package name is short for
+ source. This file-naming convention is not required, but is used
+ by just about all source code packages. (Following conventions
+ helps other administrators know what to expect.)
</para>
+ <note>
+ <title>Building Packages from Source RPMs</title>
+
+ <para>
+ Refer to <xref linkend="ch-creating-rpms"/> and
+ <xref linkend="ch-rpmbuild"/> for information on building RPMs
+ from source RPMs.
+ </para>
+ </note>
+ <para>
+ The <command>rpm</command> command provides three main operations
+ for upgrading and installing packages:
+ </para>
+ <variablelist>
+ <varlistentry>
+ <term>Upgrade</term>
+ <listitem>
+ <para>
+ An upgrade operation means installing a new version of a
+ package and removing all previous versions of the same
+ package. If you have not installed a package previously, the
+ upgrade operation will install the package.
+ </para>
+ </listitem>
+ </varlistentry>
+
+ <varlistentry>
+ <term>Freshen</term>
+ <listitem>
+ <para>
+ A freshen operation means to install a new version of a
+ package only if you have already installed another version
+ of the package.
+ </para>
+ </listitem>
+ </varlistentry>
+
+ <varlistentry>
+ <term>Install</term>
+ <listitem>
+ <para>
+ An install operation installs a package for the first time.
+ It also, through special command-line parameters, allows you
+ to install multiple versions of a package, usually not what
+ you want. So, in the vast majority of cases, you want to run
+ the upgrade operation for all package installations.
+ </para>
+ </listitem>
+ </varlistentry>
+ </variablelist>
<para>
The following sections cover the command-line options that apply
to these operations.
</para>
<sect2>
- <title>Upgrading with the rpm command</title>
+ <title>Upgrading with the <command>rpm</command> command</title>
<para/>
<para>
- Almost all installation steps use the rpm command with the ���U
- option, short for upgrade, as introduced in
- <xref linkend="ch-rpm-overview"/> . The basic syntax is:
+ Almost all installation steps use the <command>rpm</command>
+ command with the <option>���U</option> option, short for
+ upgrade, as introduced in <xref linkend="ch-rpm-overview"/> .
+ The basic syntax is:
</para>
<para>
- rpm -U package_name
+ <command>rpm</command> <option>-U</option>
+ <replaceable>package_name</replaceable>
</para>
<para>
For example:
</para>
<para>
- rpm ���i jikes-1.16-1.i386.rpm
+<screen>
+<userinput>rpm ���i jikes-1.16-1.i386.rpm</userinput>
+</screen>
</para>
<para>
- You can also use the --upgrade long option in place of -U.
+ You can also use the <option>--upgrade</option> long option in
+ place of <option>-U</option>.
[...2990 lines suppressed...]
+ <filename>rc</filename> settings.
+ </para>
+ </note>
+ <note>
+ <title>The <option>--showrc</option> Option</title>
+
+ <para>
+ See <xref linkend="ch-customizing-rpm"/> for more on the
+ <option>--showrc</option> option.
+ </para>
+ </note>
<para>
- /usr/lib/rpm/rpmrc:/usr/lib/rpm/redhat/rpmrc:/etc/rpmrc:~/.rpmrc
- </para>
- <para>
- Note
- </para>
- <para>
- The ~/.rpmrc means to look in the user's home directory for a file
- named .rpmrc.
- </para>
- <para>
- You can use the --showrc option to list all the rc settings.
- </para>
- <para>
- Cross Reference
- </para>
- <para>
- See <xref linkend="ch-customizing-rpm"/> for more on the --showrc
- option.
- </para>
- <para>
- The --version option tells the rpm command to print out the
- version number of the command and then exit. For example:
- </para>
- <para>
- rpm --version
- </para>
+ The <option>--version</option> option tells the
+ <command>rpm</command> command to print out the version number of
+ the command and then exit. For example:
+ </para>
+<screen>
+<userinput>rpm --version</userinput>
+</screen>
<para>
This command prints out a version number, like the following:
</para>
+<screen>
+<computeroutput>RPM version 4.1</computeroutput>
+</screen>
<para>
- RPM version 4.1
- </para>
- <para>
- The --dbpath option, mentioned previously, tells the rpm command
- to use a different RPM database. This is useful when testing a
- complete system install, where you want to change the RPM database
- but don't want that to affect your running Linux system. In this
- case, you can use a different RPM database and test out your
- changes. The basic syntax for this option is:
+ The <option>--dbpath</option> option, mentioned previously, tells
+ the <command>rpm</command> command to use a different RPM
+ database. This is useful when testing a complete system install,
+ where you want to change the RPM database but don't want that to
+ affect your running Linux system. In this case, you can use a
+ different RPM database and test out your changes. The basic syntax
+ for this option is:
</para>
<para>
- --dbpath directory_name
+ <option>--dbpath</option>
+ <replaceable>directory_name</replaceable>
</para>
<para>
- The --pipe option tells the rpm command to send, or pipe, its
- output to another program. The syntax for this option is:
+ The <option>--pipe</option> option tells the
+ <command>rpm</command> command to send, or pipe, its output to
+ another program. The syntax for this option is:
</para>
<para>
- --pipe command_to_send_out_to
+ <option>--pipe</option>
+ <replaceable>command_to_send_out_to</replaceable>
</para>
</sect1>
<sect1>
@@ -2035,40 +2023,38 @@
common actions of installing, removing, and upgrading software.
</para>
<para>
- The rpm ���e command removes packages. The rpm ���U command
+ The <command>rpm</command> <option>���e</option> command removes
+ packages. The <command>rpm</command> <option>���U</option> command
upgrades packages by installing new packages and removing old
versions of all the packages upgraded. RPM upgrades also work for
- installing new packages. The rpm ���F command freshens packages.
- This command only upgrades a package if an older version of the
- package has already been installed. The rpm ���i command installs
- packages.
- </para>
- <para>
- Table 4-3 summarizes the rpm command-line options for installing,
- removing, and upgrading packages.
+ installing new packages. The <command>rpm</command>
+ <option>���F</option> command freshens packages. This command only
+ upgrades a package if an older version of the package has already
+ been installed. The <command>rpm</command> <option>���i</option>
+ command installs packages.
</para>
<para>
- Table 4-3 Installing, Removing, and Upgrading with the rpm command
- </para>
- <informaltable frame="all">
+ The table below summarizes the <command>rpm</command> command-line
+ options for installing, removing, and upgrading packages.
+ </para>
+ <table id="tb-rpm-command-options">
+ <title>Installing, Removing, and Upgrading with the <command>rpm</command>
+ command</title>
+ <colspec colnum="1" colname="Command"/>
+ <colspec colnum="2" colname="Usage"/>
<tgroup cols="2">
- <tbody>
+ <thead>
<row>
- <entry>
- <para>
- Command
- </para>
- </entry>
- <entry>
- <para>
- Usage
- </para>
- </entry>
+ <entry>Command</entry>
+ <entry>Usage</entry>
</row>
+ </thead>
+ <tbody>
<row>
<entry>
<para>
- rpm ���i install_options package_files
+ <command>rpm ���i <replaceable>install_options
+ package_files</replaceable></command>
</para>
</entry>
<entry>
@@ -2080,7 +2066,8 @@
<row>
<entry>
<para>
- rpm ���e remove_options packages
+ <command>rpm ���e <replaceable>remove_options
+ packages</replaceable></command>
</para>
</entry>
<entry>
@@ -2092,7 +2079,8 @@
<row>
<entry>
<para>
- rpm ���U install_options package_files
+ <command>rpm ���U <replaceable>install_options
+ package_files</replaceable></command>
</para>
</entry>
<entry>
@@ -2105,7 +2093,8 @@
<row>
<entry>
<para>
- rpm ���Uvh install_options package_files
+ <command>rpm ���Uvh <replaceable>install_options
+ package_files</replaceable></command>
</para>
</entry>
<entry>
@@ -2118,7 +2107,8 @@
<row>
<entry>
<para>
- rpm ���F install_options package_files
+ <command>rpm ���F <replaceable>install_options
+ package_files</replaceable></command>
</para>
</entry>
<entry>
@@ -2129,7 +2119,7 @@
</row>
</tbody>
</tgroup>
- </informaltable>
+ </table>
<para>
Unfortunately, modern system management gets more complex than
that. The next chapter delves into package dependencies and the
18 years, 5 months
docs-common/common cvs-it.xml,1.1,1.2
by fedora-docs-commits@redhat.com
Author: tombo
Update of /cvs/docs/docs-common/common
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv22696/docs-common/common
Modified Files:
cvs-it.xml
Log Message:
Translation complete
Index: cvs-it.xml
===================================================================
RCS file: /cvs/docs/docs-common/common/cvs-it.xml,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- cvs-it.xml 19 Nov 2005 20:22:53 -0000 1.1
+++ cvs-it.xml 20 Nov 2005 18:29:38 -0000 1.2
@@ -293,17 +293,17 @@
<secondary>accesso anonimo</secondary>
</indexterm>
<para>
- If your goal is to download the various &FC; documents and to
- render them on your system, you only need read-only access to
- the <application>CVS</application> repository. Follow the
- instructions in this section and then skip directly to
+ Se il tuo obbiettivo �� scaricare i vari documenti &FC; e
+ renderizzarli sul tuo sistema, hai bisogno solo di un accesso read-only
+ al depositorio <application>CVS</application>. Segui le
+ instruzioni in questa sezione quindi salta direttamente a
<xref linkend="sn-cvs-cvscommands-co"/>.
</para>
<para>
- Change directories to where you want your files from
- <application>CVS</application> to be located, and execute the
- following commands:
+ Cambia directories dove vuoi che vengano collocati i files dal
+ <application>CVS</application>, ed esegui i
+ seguenti comandi:
</para>
<screen><prompt>$ </prompt><command>export CVSROOT=:pserver:cvs.fedora.redhat.com:/cvs/docs</command>
<prompt>$ </prompt><command>cvs login</command>
@@ -311,204 +311,204 @@
<prompt>$ </prompt><command>cvs checkout</command> <replaceable>module-name</replaceable>
<prompt>$ </prompt><command>cd</command> <replaceable>module-name</replaceable></screen>
<para>
- Once you have checked the module out, it doesn't matter what
- your
+ Una volta eseguito il check-out del modulo, non importa quale
<envar>CVSROOT</envar>
- is set to because it is stored in the file
- <filename>CVS/Root</filename> for each directory in your local
- repository. As long as your current working directory has a
- <filename>CVS/</filename> directory, the
- <application>CVS</application> program will automatically locate
- the &FC; repository.
+ �� impostata perch�� �� registrata nel file
+ <filename>CVS/Root</filename> per ogni directory nel tuo depositorio
+ locale. Finch�� la tua directory di lavoro ha una directory
+ <filename>CVS/</filename>, il programma
+ <application>CVS</application> localizzer�� automaticamente
+ il repositorio &FC;.
</para>
</section>
<section id="sn-cvs-config-author">
- <title>Configuring Read/Write CVS Access</title>
+ <title>Configurazione accesso CVS Read/Write</title>
<indexterm>
<primary>cvs</primary>
- <secondary>configuring read/write access</secondary>
+ <secondary>configurazione accesso read/write</secondary>
</indexterm>
<indexterm>
<primary>cvs</primary>
- <secondary>configuring access for authors</secondary>
+ <secondary>configurare gli accessi per gli autori</secondary>
</indexterm>
<para>
- To author a new document or to change an existing one, you must
- obtain full read/write access to the &FC; Docs
- <application>CVS</application> repository. For the full details
- on this process, refer to the
+ Per scrivere un nuovo documento o modificarne uno esistente, devi
+ ottenere pieno accesso read/write al repositorio
+ <application>CVS</application> della Documentazione di &FC;.
+ Per i dettagli completi su questo procedimento, fa riferimento al
+ sito web
<ulink url="http://fedoraproject.org/wiki/DocsProject/NewWriters"><filename>http://fedoraproject.org/wiki/DocsProject/NewWriters</filename>
- </ulink> web site. Below is a summary:
+ </ulink>. Segue un sommario:
</para>
<itemizedlist>
<listitem>
<para>
- Subscribe to the
+ Sotoscriviti alla
<ulink url="https://listman.redhat.com/mailman/listinfo/fedora-docs-list"><filename>fedora-docs-list</filename>
- </ulink>, which is the main forum for the project.
+ </ulink>, che �� il forum principale del progetto.
</para>
</listitem>
<listitem>
<para>
- Generate a GNU Privacy Guard (<abbrev>GPG</abbrev>) key to
- identify yourself to the project.
+ Genera una chiave GNU Privacy Guard (<abbrev>GPG</abbrev>) per
+ identificarti nel progetto.
</para>
</listitem>
<listitem>
<para>
- Register for a
+ Registrati per un account in
<ulink url="http://bugzilla.redhat.com/"><filename>Bugzilla</filename>
- </ulink> account, if you do not have one already.
- <filename>Bugzilla</filename> is how we keep track of bugs,
- changes and projects.
+ </ulink>, se non ne hai gi�� uno.
+ <filename>Bugzilla</filename> �� il modo con cui teniamo traccia degli errori,
+ cambiamenti e progetti.
</para>
</listitem>
<listitem>
<para>
- Post a
- <ulink url="http://fedoraproject.org/wiki/DocsProject_2fSelfIntroduction">self
- introduction</ulink> to the list.
+ Posta un
+ <ulink url="http://fedoraproject.org/wiki/DocsProject_2fSelfIntroduction">auto
+ introduzione</ulink> alla lista.
</para>
</listitem>
</itemizedlist>
<para>
- After your
- <ulink url="http://fedoraproject.org/wiki/DocsProject_2fSelfIntroduction">self
- introduction</ulink> has been approved your
- <application>CVS</application> access will be granted.
+ Dopo che la tua
+ <ulink url="http://fedoraproject.org/wiki/DocsProject_2fSelfIntroduction">auto
+ introduzione</ulink> �� stata approvata il tuo accesso
+ <application>CVS</application> verr�� garantito.
</para>
<para>
- Every author, and that includes you once your self introduction
- has been received, has a unique
+ Ogni autore, e questo ti include una volta che la tua auto introduzione
+ �� stat ricevuta, ha un unico
<envar>$CVSROOT</envar>
- to access the <application>CVS</application> repository:
+ per accedere al repositorio <application>CVS</application>:
</para>
<screen><prompt>$ </prompt><command>export CVSROOT=:ext:</command><replaceable>yourname</replaceable><command>@cvs.fedora.redhat.com:/cvs/docs</command>
<prompt>$ </prompt><command>export CVS_RSH=/usr/bin/ssh</command></screen>
<para>
- With the
+ Con le variabili ambiente
<envar>$CVSROOT</envar>
- and
+ e
<envar>$CVS_RSH</envar>
- environment variables in place, you can access the repository:
+ impostate, puoi accedera al repositorio:
</para>
<screen><prompt>$ </prompt><command>cvs co -c</command></screen>
<para>
- You will be asked for the passphrase for your
- <application>SSH</application> key. Press
+ Ti verr�� richiesta la passphrase per la tua chiave
+ <application>SSH</application>. Premi
<guibutton>ENTER</guibutton>
- and you should receive a list of modules already in the
- repository.
+ e riceverai la lista dei moduli presenti nel
+ repositorio.
</para>
</section>
</section>
<section id="sn-cvs-cvscommands">
- <title>Basic CVS Commands</title>
+ <title>Comandi CVS di base</title>
<indexterm>
<primary>cvs</primary>
- <secondary>commands</secondary>
+ <secondary>comandi</secondary>
</indexterm>
<para>
- After configuring your system to work with CVS, checkout the
- modules you will be working on.
+ Dopo aver configurato il sistema per funzionare con CVS, esegui il checkout
+ dei moduli su cui lavorerai.
</para>
<tip>
<title>Tip</title>
<para>
- To see if you need a correctly-set
- <envar>$CVSROOT</envar>
- variable, or the <option>-m </option>
- <replaceable>repository</replaceable> command line switch, see
- if you have a <filename>CVS/</filename> subdirectory in your
- working directory.
+ Per vedere se hai impostato correttamente la variabile
+ <envar>$CVSROOT</envar>,
+ o lo switch della linea di comando <option>-m </option>
+ <replaceable>repository</replaceable>, vedi
+ se hai una subdirectory <filename>CVS/</filename> nella tua
+ directory di lavoro.
</para>
<para>
- If you have a <filename>CVS/</filename> directory,
- <application>CVS</application> ignores any
+ Se hai una directory <filename>CVS/</filename>,
+ <application>CVS</application> ignorera qualsiasi
<envar>$CVSROOT</envar>
- or <option>-m</option> command line switch.
+ o switch della linea di comando <option>-m</option>.
</para>
</tip>
<section id="sn-cvs-cvscommands-co">
- <title>Checking Out Modules</title>
+ <title>Fare il checkout dei moduli</title>
<indexterm>
<primary>cvs</primary>
- <secondary>checking out modules</secondary>
+ <secondary>eseguire il checkout dei moduli</secondary>
</indexterm>
<para>
- You only need to checkout a module once. After a local copy of
- the module is on your system, it is on your system.
+ Devi fare il checkout di un modulo una volta. Dopo che la copia del
+ modulo �� sul tuo sistema, �� sul tuo sistema.
</para>
<para>
- To checkout a module, use the following command:
+ Per fare il checkout di un modulo, usa il seguente comando:
</para>
<screen><prompt>$ </prompt><command>cvs co</command> <replaceable><module-name></replaceable></screen>
<para>
- For example, to checkout the
- <computeroutput>example-tutorial</computeroutput> module, change
- to your work directory, and execute the following command:
+ Per esempio, per fare il checkout del modulo
+ <computeroutput>example-tutorial</computeroutput>, cambia
+ la tua directory di lavoro, ed esegui il seguente comando:
</para>
<screen><prompt>$ </prompt><command>cvs co example-tutorial</command></screen>
<para>
- A directory called <filename>example-tutorial/</filename> is
- created in the current directory.
+ Verr�� creata una directory chiamata <filename>example-tutorial/</filename>
+ nela directory corrente.
</para>
<para>
- If a branch name is not specified when checking out a module, it
- is referred to as the <firstterm>HEAD</firstterm> of the
- <application>CVS</application> module.
+ Se non viene specificato un nome del ramo durante il checking del modulo,
+ verr�� riferito al <firstterm>HEAD</firstterm> del modulo
+ <application>CVS</application>.
</para>
<section id="sn-cvs-cvscommands-co-branch">
- <title>Checking Out Branches of Modules</title>
+ <title>Fare il checkout dei rami dei moduli</title>
<indexterm>
<primary>cvs</primary>
- <secondary>check out modules</secondary>
- <tertiary>checking out branches</tertiary>
+ <secondary>eseguire il checkout dei moduli</secondary>
+ <tertiary>eseguire il checkout dei rami</tertiary>
</indexterm>
<para>
- Think of a <application>CVS</application> branch as a version
- of the files for a particular version of a manual or package.
+ Pensa ad un ramo <application>CVS</application> come una versione
+ dei files per una particolare versione del pacchetto o manuale.
</para>
<para>
- To checkout a branch of a module, use the following command:
+ Per fare il checkout di un ramo di un modulo, usa il seguente comando:
</para>
<screen><prompt>$ </prompt><command>cvs co</command> <option>-d</option> <replaceable><directory></replaceable> <option>-r</option> <replaceable><branchname></replaceable> <replaceable><module-name></replaceable></screen>
<para>
- A directory named <replaceable><directory></replaceable>
- is created, and the files for the
- <replaceable><branchname></replaceable> branch of the
- <replaceable><module-name></replaceable> module are
- copied in the directory.
+ Una directory chiamata <replaceable><directory></replaceable>
+ viene creata, ed i files per il ramo
+ <replaceable><branchname></replaceable> del modulo
+ <replaceable><module-name></replaceable> sono
+ copiati nella directory.
</para>
<para>
- For example, to checkout a branch named BRANCH-VERSION-1.2
- from the <computeroutput>mymodule</computeroutput> module, use
- the command:
+ Per esempio, per fare il checkout di un ramo denominato BRANCH-VERSION-1.2
+ dal modulo <computeroutput>mymodule</computeroutput>, usa
+ il comando:
</para>
<screen><prompt>$ </prompt><command>cvs co -d mymodule-1.2 -r BRANCH-VERSION-1.2 mymodule</command></screen>
<para>
- The BRANCH-VERSION-1.2 branch of the module is checked out in
- the <filename>mymodule-1.2</filename> directory on your
- system.
+ Verr�� eseguito il checkout del ramo BRANCH-VERSION-1.2 del modulo nella
+ directory <filename>mymodule-1.2</filename> sul tuo
+ sistema.
</para>
<para>
- To determine which branches and tags exist for a file, use the
- command:
+ Per determinare quale ramo e tags esiste per un file, usa il
+ comando:
</para>
<screen><prompt>$ </prompt><command>cvs status</command> <option>-v</option> <replaceable><filename></replaceable></screen>
<para>
- For example, the status of the file
- <filename>foo.sgml</filename> is as follows:
+ Per esempio, lo status del file
+ <filename>foo.sgml</filename> �� il seguente:
</para>
<screen>
<computeroutput>
@@ -526,207 +526,206 @@
</computeroutput>
</screen>
<para>
- Only tags marked as branches in the second column under the
- <computeroutput>Existing Tags</computeroutput> section can be
- checked out as a branch.
+ Solo dei tags marcati come rami nella seconda colonna sotto la
+ sezione <computeroutput>Existing Tags</computeroutput> si pu�� eseguire
+ il checkout come ramo.
</para>
</section>
</section>
<section id="sn-cvs-cvscommands-up">
- <title>Updating Files</title>
+ <title>Aggiornare i files</title>
<indexterm>
<primary>cvs</primary>
- <secondary>updating files</secondary>
+ <secondary>aggiornare i files</secondary>
</indexterm>
<para>
- To retrieve the latest versions of the files in a module, change
- to the directory that contains the files for the module and
- execute the command:
+ Per ricevere l'ultima versione di un file in un modulo, cambia
+ nella directory che contiene i files per il modulo ed
+ esegui il comando:
</para>
<screen><command>cvs update</command></screen>
<para>
- The latest versions of all the files in the module are
- downloaded into your local copy. If you notice a file conflict,
- refer to <xref linkend="sn-cvs-cvscommands-conflicts"></xref>.
+ Le ultime versioni di tutti i files ne modulo sono
+ scaricate nella tua copia locale. Se noti un conflitto di file,
+ fa riferimento a <xref linkend="sn-cvs-cvscommands-conflicts"></xref>.
</para>
</section>
<section id="sn-cvs-cvscommands-commit">
- <title>Committing Files</title>
+ <title>Eseguire il commit dei files</title>
<indexterm>
<primary>cvs</primary>
- <secondary>committing files</secondary>
+ <secondary>eseguire il commit dei files</secondary>
</indexterm>
<para>
- After modifying files in your local version of a module, commit
- them to save the changes on the <application>CVS</application>
+ Dopo aver modificato i files nella tua versione locale di un modulo, esegui il commit
+ per salvare i cambiamenti sul <application>CVS</application>
server:
</para>
-<screen><prompt>$ </prompt><command>cvs commit</command> <option>-m</option> "<replaceable>some log message</replaceable>" <replaceable>filename</replaceable></screen>
+<screen><prompt>$ </prompt><command>cvs commit</command> <option>-m</option> "<replaceable>alcuni messaggi di log</replaceable>" <replaceable>filename</replaceable></screen>
<note>
<para>
- If you would prefer to write your log message with your
- favorite text editor, as defined by the $VISUAL or the $EDITOR
- environment variable, just omit the <userinput>-m "some
- log message"</userinput>. The buffer will already contain
- comments describing the change; you do not need to delete them
- as you enter your own text.
+ Se preferisci scrivere il tuo messaggio di log con il tuo editor
+ di testo preferito, come definito dalla variabile ambiente $VISUAL o
+ $EDITOR, ometti semplicemente la <userinput>-m "alcuni
+ messaggi di log"</userinput>. Il buffer conterr�� gi��
+ alcuni commenti che descrivono i cambiamenti; non �� necessario cancellarli
+ quando inserirai il tuo testo.
</para>
</note>
<para>
- The log message should be as descriptive as possible so that you
- and anyone else working on the module understands what changed.
- Using a log message such as <userinput>updated some
- files</userinput> does not accurately describe what has changed
- and will not help you in the future. If you are correcting a
- bug, use the <application>Bugzilla</application> reference.
+ I messaggi di log dovranno essere pi�� descrittivi possibile affinch��
+ chiunque altro lavori al modulo capisca cos'�� stato cambiato.
+ Usare un messaggio di log tipo <userinput>aggiornati alcuni
+ files</userinput> non descrive accuratamente cosa �� stato cambiato
+ e non ti aiuter�� in futuro. Se hai corretto un
+ errore, fa riferimento a <application>Bugzilla</application>.
</para>
<para>
- The <replaceable><filename></replaceable> can be one
- filename, a series of filenames separated by spaces, or a group
- of filenames specified using wildcards such as
- <filename>*.png</filename> or <filename>foo-*.sgml</filename>.
+ Il <replaceable><filename></replaceable> pu�� essere un
+ filename, una serie si filenames separati da spazi, o un gruppo
+ di filenames specificati usando una wildcards tipo
+ <filename>*.png</filename> o <filename>foo-*.sgml</filename>.
</para>
<para>
- If no filename or group of filenames is specified in the
- <command>commit</command> command, all outstanding changes of
- any kind are committed to the server. The command is recursive
- and will include changes in any subdirectories of the module.
- Use caution when issuing the <command>commit</command> command
- without any filenames because you might not remember exactly
- what files changed.
+ Se nessun filename o gruppo di filenames �� specificato nel
+ comando <command>commit</command>, tutti i cambiamenti eccezionali
+ di qualsiasi tipo sono commessi al server. Il comando �� recursivo
+ ed includer�� i cambiamenti in ogni subdirectories del modulo.
+ Usa cautela qunado esegui il comando <command>commit</command>
+ senza nessun filenames poich�� potresti non ricordare esattamente
+ quali files sono cambiano.
</para>
<para>
- If you notice a file conflict, refer to
+ Se noti un conflitto di file, fa riferimento a
<xref linkend="sn-cvs-cvscommands-conflicts"></xref>.
</para>
</section>
<section id="sn-cvs-cvscommands-add">
- <title>Adding Files</title>
+ <title>Aggiungere files</title>
<indexterm>
<primary>cvs</primary>
- <secondary>adding files</secondary>
+ <secondary>aggiungere files</secondary>
</indexterm>
<para>
- To add a file to a module, create the file in your local copy
- then execute the following command:
+ Per aggiungere un file ad un modulo, crea il file sulla tua copia locale
+ quindi esegui il seguente comando:
</para>
<screen><prompt>$ </prompt><command>cvs add</command> <replaceable>file-to-add</replaceable></screen>
<para>
- After adding the file, you must <command>commit</command> the
- <command>add</command> to copy it to the server:
+ Dopo aver aggiunto il file, devi eseguire un <command>commit</command>
+ dell'<command>add</command> per copiarlo sul server:
</para>
-<screen><prompt>$ </prompt><command>cvs commit</command> <option>-m</option> "<replaceable>some log message</replaceable>" <replaceable>file-to-add</replaceable></screen>
+<screen><prompt>$ </prompt><command>cvs commit</command> <option>-m</option> "<replaceable>qualche messaggio di log</replaceable>" <replaceable>file-da-aggiungere</replaceable></screen>
</section>
<section id="sn-cvs-cvscommands-admin">
- <title>Managing Binary Files</title>
+ <title>Amministrare i files binari</title>
<indexterm>
<primary>cvs</primary>
- <secondary>binary files</secondary>
+ <secondary>files binari</secondary>
</indexterm>
<para>
- The most commonly-archived files are simple text files but
- sometimes binary files are also archived. The
- <application>cvs</application> program recognizes most common
- filename extentions such as <filename>.png</filename> or
- <filename>.jpg</filename>, so <application>cvs</application>
- usually "does the right thing".
+ I files comunemente pi�� archiviati sono di semplice testo ma
+ qualche volta sono archiviati anche files binari. Il programma
+ <application>cvs</application> determina le estensioni dei
+ files pi�� comuni tipo <filename>.png</filename> o
+ <filename>.jpg</filename>, cos�� di solito <application>cvs</application>
+ "fa la cosa giusta".
</para>
<para>
- When a copy of a file is checked out of the repository,
- <application>cvs</application> scans it for special keywords,
- such as "<computeroutput>$id:$</computeroutput>" and
- replaces the string with a generated value, such as the file
- version number.
+ Quando si esegue il checkout della copia di un file del repositorio,
+ il <application>cvs</application> lo scansisce per parole chiavi speciali,
+ tipo "<computeroutput>$id:$</computeroutput>" e
+ sostituisce le stringhe con un valore generato, tipo il numero di versione
+ del file.
</para>
<para>
- This keyword substitution usually corrupts binary files, so it
- must be turned off if <application>cvs</application> does not
- recognize your file as binary. To mark your file as being
- binary, and thus needing the keyword expansion turned off, use
- the command:
+ Questa sostituzione di keyword di solito corrompe i files binari, cos��
+ deve essere disattivata se <application>cvs</application> non
+ reconosce i tuoi files come binari. Per marcare il tuo file come
+ binario, e quindi disattivare l'espansione dell keyword, usa
+ il comando:
</para>
<screen width="60"><prompt>$ </prompt><command>cvs</command> <option>admin</option> <option>-kk</option> <replaceable>filename</replaceable></screen>
<para>
- Note that the file must already be checked in to the
- <abbrev>CVS</abbrev> repository before the
- <option>admin</option> command can be used. This is OK, since
- the keyword expansion is done as the file is checked out and
- copied to the local directory, not when the file is committed to
- the repository.
+ Nota che il file deve gi�� essere nel repositorio
+ <abbrev>CVS</abbrev> prima di poter usare il comando
+ <option>admin</option>. Questo �� OK, fino a che
+ l'espansione delle keyword �� fatta appena il file viene sottoposto a checkout e
+ copiato nella directory locale, non quando il file viene commesso al
+ repositorio.
</para>
<tip>
- <title>Recovering a binary file</title>
+ <title>Ripristinare un file binario</title>
<para>
- If you check a binary file into the repository and then find
- it corrupted when it is checked out, do not panic. Simply use
- the <option>admin</option> command as described above, delete
- your local file copy, and check it out again.
+ Se esegui il check di un file binario nel repositorio e trovi
+ che sia corrotto durante il checkout, non aver paura. Usa semplicemente
+ il comando <option>admin</option> come descritto sopra, cancella
+ la tua copia locale del file, ed esegui nuovamente il checkout.
</para>
</tip>
</section>
<section id="sn-cvs-cvscommands-rm">
- <title>Removing Files</title>
+ <title>Rimuovere i files</title>
<indexterm>
<primary>cvs</primary>
- <secondary>removing files</secondary>
+ <secondary>rimuovere i files</secondary>
</indexterm>
<para>
- If a file is no longer needed in the module, use the
- <command>remove</command> command to remove it from your local
- copy and then <command>commit</command> the removal to the
- server. Even though the file is removed from current version of
- the module, an archived copy is still kept on the server and can
- be retrieved at any time with the <command>add</command>
- command.
+ Se un file non �� pi�� necessario nel modulo, usa il
+ comando <command>remove</command> per rimuoverlo dalla tua copia
+ locale poi esegui il <command>commit</command> per rimuoverlo dal
+ server. Anche se il file �� rimosso dalla versione corrente del
+ modulo, una copia archiviata �� ancora lasciata sul server e pu��
+ essere recuperato in qualsiasi momento con il comando <command>add</command>.
</para>
<screen><prompt>$ </prompt><command>cvs rm -f</command> <replaceable>file-to-remove</replaceable></screen>
<para>
- After removing the file, you must <command>commit</command> the
- removal:
+ Dopo la rimozione del file, devi eseguire il <command>commit</command> della
+ rimozione:
</para>
-<screen><prompt>$ </prompt><command>cvs commit</command> <option>-m</option>"<replaceable>some log message</replaceable>" <replaceable>file-to-remove</replaceable></screen>
+<screen><prompt>$ </prompt><command>cvs commit</command> <option>-m</option>"<replaceable>qualche messagiio di log</replaceable>" <replaceable>file-da-rimuovere</replaceable></screen>
<para>
- You can not use wildcards in the <command>commit</command>
- command to identify removed files. They must be specified with a
- exact filename.
+ Non puoi usare wildcards nel eseguire il <command>commit</command>
+ per identificare files rimossi. Essi devono essere specificati con il nome
+ di file esatto.
</para>
<para>
- If you need to rename a file, it is best to rename the file on
- the <application>CVS</application> server so that the history of
- the file is preserved. If you need to rename a file, send an
- email to
+ Se necessiti di rinominare un file, �� meglio rinominarlo sul
+ <application>CVS</application> server affinch�� la storia del
+ file possa essere preservata. Se hai bisogno di rinominare un file, manda un
+ email a
<ulink url="mailto:cvsdocs-administrator@fedora.redhat.com"><filename>cvsdocs-administrator(a)fedora.redhat.com</filename>
- </ulink> asking to have the file renamed.
+ </ulink> chiedendo di voler rinominare un file.
</para>
</section>
<section id="sn-cvs-cvscommands-status">
- <title>Status of Files</title>
+ <title>Status dei files</title>
<indexterm>
<primary>cvs</primary>
- <secondary>status of files</secondary>
+ <secondary>status dei files</secondary>
</indexterm>
<para>
- Sometimes it is necessary to view the
- <firstterm>status</firstterm> of a file in a
- <application>CVS</application> module. To view the status of a
- file, use the command:
+ Qualche volta �� necessario vedere lo
+ <firstterm>status</firstterm> di un file in un
+ modulo <application>CVS</application>. Per vedere lo status di un
+ file, usa il comando:
</para>
<screen><prompt>$ </prompt><command>cvs status</command> <replaceable>filename</replaceable></screen>
<para>
- The status report of a repository file is as follows:
+ Il rapporto dello status di un file nel repositorio �� come segue:
</para>
<variablelist>
@@ -734,8 +733,8 @@
<term><computeroutput>Up-to-date</computeroutput></term>
<listitem>
<para>
- Your revision of the file is identical to the latest
- revision on the <application>CVS</application> server.
+ La tua revisione del file �� identica all'ultima
+ revisione sul <application>CVS</application> server.
</para>
</listitem>
</varlistentry>
@@ -744,8 +743,8 @@
<term><computeroutput>Locally Modified</computeroutput></term>
<listitem>
<para>
- You have updated to the latest revision from the server,
- but then you modified the file on your system.
+ Hai aggiornato il file all'ultima versione dal server,
+ ma poi hai modificatio il file sul tuo sistema.
</para>
</listitem>
</varlistentry>
@@ -754,8 +753,8 @@
<term><computeroutput>Locally Added</computeroutput></term>
<listitem>
<para>
- You added the file with the <command>cvs add</command>
- command but have not yet committed the addition of the
+ Hai aggiunto il file con il comando <command>cvs add</command>
+ ma non hai ancora eseguito il commit per l'aggiunta del
file.
</para>
</listitem>
@@ -765,9 +764,9 @@
<term><computeroutput>Locally Removed</computeroutput></term>
<listitem>
<para>
- You removed the file with the <command>cvs
- remove</command> command but have not yet committed the
- removal.
+ Hai rimosso il file con il comando <command>cvs
+ remove</command> ma non hai ancora eseguito il commit per la
+ rimozione.
</para>
</listitem>
</varlistentry>
@@ -776,10 +775,10 @@
<term><computeroutput>Needs Checkout</computeroutput></term>
<listitem>
<para>
- A newer version of the file is on the server and needs to
- be retrieved. Even though the status includes the word
- checkout, it really means that you need to update your
- files with the <command>cvs update</command> command.
+ Sul server c'�� una nuova versione del file ed necessita di
+ essere recuperata. Anche se lo status include la parola
+ checkout, vuoldire che hai bisogno di aggiornare
+ i files con il comando <command>cvs update</command>.
</para>
</listitem>
</varlistentry>
@@ -788,9 +787,9 @@
<term><computeroutput>Needs Patch</computeroutput></term>
<listitem>
<para>
- The revision in your local checkout needs a patch to be
- the latest revision from the server. Issue the
- <command>cvs update</command> command to resolve.
+ La revisione del tuo checkout locale necessita di una patch per
+ essere l'ultima versione dal server. Esegui il
+ comando <command>cvs update</command> per risolvere.
</para>
</listitem>
</varlistentry>
@@ -799,10 +798,10 @@
<term><computeroutput>Needs Merge</computeroutput></term>
<listitem>
<para>
- A newer revision exists on the server and your local
- version contains modification not yet committed. This
- status usually occurs if you don't have the latest
- revision of the file and edit it anyway.
+ Esiste una nuova revisione sul server e la tua versione di copia
+ locale contiene modifiche di cui non hai fatto ancora il commit. Questo
+ status di solito avviene se non hai l'ultima revisione
+ del file ed lo editi lo stesso.
</para>
</listitem>
</varlistentry>
@@ -811,12 +810,12 @@
<term><computeroutput>File had conflicts on merge</computeroutput></term>
<listitem>
<para>
- Similar to <computeroutput>Needs Merge</computeroutput>,
- except when you tried to issue the <command>cvs
- update</command> command, the differences could not be
- resolved automatically. Refer to
- <xref linkend="sn-cvs-cvscommands-conflicts"></xref> for
- more information on resolving conflicts.
+ Simile a <computeroutput>Needs Merge</computeroutput>,
+ eccetto che quando hai provato ad eseguire il comando <command>cvs
+ update</command>, le differenze non potevano essere
+ risolte automaticamente. Fa riferimento a
+ <xref linkend="sn-cvs-cvscommands-conflicts"></xref> per
+ maggiori informazioni sulla risoluzione dei conflitti.
</para>
</listitem>
</varlistentry>
@@ -825,14 +824,14 @@
<term><computeroutput>Unknown</computeroutput></term>
<listitem>
<para>
- The <application>CVS</application> server does not know
- anything about this file. It has neither been added nor
- removed locally and has never been committed to the
- server. This status usually occurs for files you should
- not commit to <application>CVS</application> such as
- <filename>generated-index.sgml</filename> or for files
- that you want to add to the repository but have not yet
- issued the <command>cvs add</command> command.
+ Il <application>CVS</application> server non sa nulla
+ su questo file. Il file non �� stato aggiunto ne
+ rimosso loclamente e non �� mai stato commesso al
+ server. Questo status di solito sussiste per i files che di cui non
+ vorresti fare il commit al <application>CVS</application> tipo
+ i <filename>generated-index.sgml</filename> o per quei files
+ che vorresti aggiungere al repositorio ma dei quali non hai
+ ancora impartito il comando <command>cvs add</command>.
</para>
</listitem>
</varlistentry>
@@ -840,16 +839,16 @@
</section>
<section id="sn-cvs-cvscommands-conflicts">
- <title>Resolving Conflicts</title>
+ <title>Risoluzione dei conflitti</title>
<indexterm>
<primary>cvs</primary>
- <secondary>resolving conflicts</secondary>
+ <secondary>risoluzione dei conflitti</secondary>
</indexterm>
<para>
- If you modify a file and the same region is modified by someone
- else and committed first, you will probably see a message
- similar to the following when committing the file or updating
- your local copy of the module:
+ Se modifichi un file e la stessa regione �� modificata da qualcun'altro
+ che esegue il commitprima di te, probabilmente vedrai un messaggio
+ simile al seguente quando eseguirai il commit o l'aggiornamento
+ della tua copia locale del modulo:
</para>
<screen>
<computeroutput>
@@ -863,10 +862,10 @@
</computeroutput>
</screen>
<para>
- To resolve the conflict, open the file, search for
+ Per risolvere il conflitto, apri il file, cerca
<computeroutput><<<<<<<</computeroutput>
- and determine which version of the content is correct. For
- example:
+ e determina quale versione del contenuto �� corretta. Per
+ esempio:
</para>
<screen>
<computeroutput>
@@ -881,40 +880,40 @@
</computeroutput>
</screen>
<para>
- The content between the
+ Il contenuto fra le
<computeroutput><<<<<<<</computeroutput>,
- and the <computeroutput>=======</computeroutput> is the content
- from your working copy. The content between the
- <computeroutput>=======</computeroutput> and the
- <computeroutput>>>>>>>></computeroutput> is
- the content from the server.
+ e le <computeroutput>=======</computeroutput> �� il contenuto
+ della tua copia di lavoro. Il contenuto fra le
+ <computeroutput>=======</computeroutput> e le
+ <computeroutput>>>>>>>></computeroutput> ��
+ il contenuto dal server.
</para>
<para>
- Resolve the conflict by editing your copy, and commit the file.
+ Resolvi il conflitto editando la tua copia, ed esegui il commit del file.
</para>
</section>
<section id="sn-cvs-cvscommands-summary">
- <title>Summary</title>
+ <title>Sommario</title>
<indexterm>
<primary>cvs</primary>
- <secondary>commands</secondary>
- <tertiary>summary of</tertiary>
+ <secondary>comandi</secondary>
+ <tertiary>sommario di</tertiary>
</indexterm>
<para>
- All commands assume you are in the proper directory for the
- <application>CVS</application> module.
+ Tutti i comandi assumono che tu sia nella directory appropriata per
+ il modulo <application>CVS</application>.
</para>
<table frame="all" id="tb-cvs-basic-commands">
- <title>Basic CVS Commands</title>
+ <title>Comandi CVS di base</title>
<tgroup cols="2">
<colspec colnum="1" colname="shortcut" colwidth="30"/>
<colspec colnum="2" colname="description" colwidth="60"/>
<thead>
<row>
- <entry>Command</entry>
- <entry>Description</entry>
+ <entry>Commando</entry>
+ <entry>Descrizione</entry>
</row>
</thead>
<tbody>
@@ -923,87 +922,87 @@
<replaceable><module-name></replaceable></command>
or <command>cvs co <replaceable><module-name></replaceable></command>
</entry>
- <entry>Creates a directory called
- <replaceable><module-name></replaceable> with the contents of the
- module in the directory</entry>
+ <entry>Crea una directory chiamata
+ <replaceable><module-name></replaceable> con il contenuto del
+ modulo nella directory</entry>
</row>
<row>
<entry><command>cvs co -d <replaceable><directory></replaceable> -r <replaceable><branchname></replaceable><replaceable><module-name></replaceable></command>
</entry>
- <entry>Creates the <replaceable><directory></replaceable> directory
- with the contents of the <replaceable><branchname></replaceable>
- branch of the <replaceable><module-name></replaceable> module</entry>
+ <entry>Crea la directory <replaceable><directory></replaceable>
+ con i contenuti del ramo <replaceable><branchname></replaceable>
+ del modulo <replaceable><module-name></replaceable></entry>
</row>
<row>
<entry><command>cvs update</command> or <command>cvs up</command>
</entry>
- <entry>Update your files with the latest files from the CVS server</entry>
+ <entry>Aggiorna i tuoi files con gli ultimi files dal CVS server</entry>
</row>
<row>
<entry><command>cvs add <replaceable><filename></replaceable></command>
</entry>
- <entry>Add a new file "filename" to the CVS server</entry>
+ <entry>Aggiunge un nuovo file "filename" al CVS server</entry>
</row>
<row>
<entry><command>cvs commit -m "My message"
<replaceable><filename></replaceable></command>
</entry>
- <entry>Update file <replaceable><filename></replaceable> with the
- latest copy from your computer</entry>
+ <entry>Aggiorna il file <replaceable><filename></replaceable> con
+ l'ultima copia proveniente dal tuo computer</entry>
</row>
<row>
<entry><command>cvs log <replaceable><filename></replaceable></command>
</entry>
- <entry>View the commit messages for the file <replaceable><filename></replaceable>
+ <entry>Mostra i messaggi di commit per il file <replaceable><filename></replaceable>
</entry>
</row>
<row>
<entry><command>cvs status <replaceable><filename></replaceable></command>
</entry>
- <entry>View status of the file, such as <computeroutput>Locally
+ <entry>Mostra lo status del file, tipo <computeroutput>Locally
Modified</computeroutput>
</entry>
</row>
<row>
<entry><command>cvs status -v <replaceable><filename></replaceable></command>
</entry>
- <entry>View existing tags and branches for file</entry>
+ <entry>Mostra i tags esistenti ed i rami per il file</entry>
</row>
<row>
<entry><command>cvs diff <replaceable><filename></replaceable></command>
</entry>
- <entry>Show diff of the working copy of the file and the latest
- version of the file for the branch</entry>
+ <entry>Mostra la differenza della copia di lavoro del file e l'ultima
+ versione del file per il ramo</entry>
</row>
<row>
<entry><command>cvs diff -r1.1 -r1.2 <replaceable><filename></replaceable></command>
</entry>
- <entry>Show diff of version 1.1 and 1.2 for file</entry>
+ <entry>Mostra la differenza fra le versioni 1.1 e 1.2 per il file</entry>
</row>
</tbody>
</tgroup>
</table>
<para>
- For more information, read the CVS manual available on your
- system at
+ Per maggiori informazioni, leggi il manuale CVS disponibile sul tuo
+ sistema in
<filename>/usr/share/doc/cvs-<replaceable><version-number></replaceable>/cvs.ps</filename>
- (the CVS version might vary) and visit the CVS webpage available
- at
+ (la versione CVS pu�� cambiare) e visita la pagian web di CVS disponibile
+ su
<ulink url="http://www.cvshome.org/">http://www.cvshome.org/</ulink>.
</para>
<tip>
<title>Tip</title>
<para>
- Since <application>CVS</application> is using
- <application>ssh</application> to connect to the
- <application>CVS</application> server, you will be prompted
- your password before performing your
- <application>CVS</application> request. If you want to
- configure your machine so that you do not have to enter a
- password, refer to the
+ Poich�� <application>CVS</application> usa
+ <application>ssh</application> per connettersi al
+ <application>CVS</application> server, ti verr�� richiesta
+ la password prima di eseguire una richiesta
+ <application>CVS</application>. Se vuoi configurare
+ la tua macchina affinch�� tu non abbia pi�� bisogno di
+ inserire la password, fa riferimento a
<ulink url="http://redhat.com/docs/manuals/linux/RHL-9-Manual/custom-guide/s1-openssh..."><citetitle>&RH;
- Linux 9 Customization Guide</citetitle> </ulink> for details
- about using <command>ssh-agent</command>.
+ Linux 9 Customization Guide</citetitle> </ulink> per i dettagli
+ sull'uso di <command>ssh-agent</command>.
</para>
</tip>
</section>
18 years, 5 months
example-tutorial example-tutorial-it.xml,NONE,1.1
by fedora-docs-commits@redhat.com
Author: pfrields
Update of /cvs/docs/example-tutorial
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv17171
Added Files:
example-tutorial-it.xml
Log Message:
Created bogus new i18n file for testing; don\'t waste time translating this.
--- NEW FILE example-tutorial-it.xml ---
<!-- $Id: -->
<!DOCTYPE article PUBLIC "-//OASIS//DTD DocBook XML V4.2//EN"
"http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd" [
<!ENTITY % FEDORA-ENTITIES-EN SYSTEM "../docs-common/common/fedora-entities-en.ent">
%FEDORA-ENTITIES-EN;
<!ENTITY BOOKNAME "example-tutorial">
<!ENTITY BOOKVERSION "0.14"> <!-- change version here -->
<!ENTITY BOOKDATE "2005-09-18"> <!-- change revision date here -->
<!ENTITY BOOKID "&BOOKNAME;-&BOOKVERSION; (&BOOKDATE;)">
<!ENTITY BUG-NUM "000000"> <!-- use this only while in draft stage -->
]>
<!-- This file is just a copy of the English version, only here for testing -->
<!-- Makefile locale capabilities. Nobody really needs to translate this -->
<!-- yet. -->
<article id="example-tutorial" lang="it">
<articleinfo>
<title>Example Tutorial</title>
<copyright>
<year>2003, 2005</year>
<holder>&FORMAL-RHI;</holder>
<holder>Tammy Fox</holder>
</copyright>
<authorgroup>
<author>
<surname>Fox</surname>
<firstname>Tammy</firstname>
</author>
<editor>
<surname>Frields</surname>
<firstname>Paul</firstname>
<othername role="mi">W.</othername>
</editor>
</authorgroup>
&LEGALNOTICE;
<revhistory>
<revision>
<revnumber>0.13</revnumber>
<date>2005-09-18</date>
<authorinitials>PaulWFrields</authorinitials>
<revdescription>
<para>
Add revision history.
</para>
</revdescription>
</revision>
</revhistory>
</articleinfo>
<section id="sn-some-section">
<title>Some Section</title>
<indexterm>
<primary>Index term</primary>
</indexterm>
<para>
This is an example section. You should not use sect1, sect2, etc., since
those tags will make sections less modular — that is, harder to
relocate without changing a lot of other markup.
</para>
<para>
Keep text within the <command>title</command> tags on the same line as the
tags. Nesting the title on a separate line from the enclosing tags results
in extra spaces in HTML rendering.
</para>
<warning>
<title>Warning</title>
<para>
Example of an admonition.
</para>
</warning>
<para>
This paragraph illustrates the use of command syntax to accomplish a
task. Note that specific filenames denoting versions should be
avoided. To install any RPM package, use the following syntax:
</para>
<screen>
<userinput><command>rpm -ivh <replaceable>pkgname</replaceable>-<replaceable>version</replaceable>.<replaceable>arch</replaceable>.rpm</command></userinput>
</screen>
<para>
Notice that the <command>screen</command> section is entirely
left-justified with no preceding indent. This is necessary to ensure
proper rendering in PDFs. Also notice that the entire
<command>command</command> has been surrounded by
<command>userinput</command> since the user types this
command. Computer output would be enclosed in
<command>computeroutput</command> tags, as in the following
sample.
</para>
<screen>
<userinput><command>grep snmptrap /etc/services</command></userinput>
<computeroutput>snmptrap 162/udp snmp-trap # Traps for SNMP</computeroutput>
</screen>
<para>
Lines should be broken <emphasis>exactly</emphasis> as they are
on-screen. Also, note that spaces inside <command>screen</command> tags
are automatically treated as non-breaking.
</para>
<tip>
<title>Fill modes and <command>screen</command> tags</title>
<para>
Using automatic or manual fill commands in Emacs/PSGML will sometimes
mangle <command>screen</command> sections. Use care when performing fill
operations, and check the results.
</para>
</tip>
</section>
<section>
<title>Callout Example</title>
<programlisting id="pl-callout">
Line 1 <co id="pl-callout-L1"/>
Line 2
Line 3
Line 4 <co id="pl-callout-L4"/>
</programlisting>
<calloutlist>
<callout arearefs="pl-callout-L1">
<para>
Here is a callout.
</para>
</callout>
<callout arearefs="pl-callout-L4">
<para>
The second callout.
</para>
</callout>
</calloutlist>
</section>
<index id="generated-index"></index>
</article>
<!--
Local variables:
mode: xml
End:
-->
18 years, 5 months
selinux-faq selinux-faq-it.xml,1.1,1.2
by fedora-docs-commits@redhat.com
Author: tombo
Update of /cvs/docs/selinux-faq
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv15128/selinux-faq
Modified Files:
selinux-faq-it.xml
Log Message:
Index: selinux-faq-it.xml
===================================================================
RCS file: /cvs/docs/selinux-faq/selinux-faq-it.xml,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- selinux-faq-it.xml 19 Nov 2005 09:42:45 -0000 1.1
+++ selinux-faq-it.xml 19 Nov 2005 21:56:49 -0000 1.2
@@ -3,7 +3,7 @@
"http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd" [
<!-- *************** Bring in Fedora entities *************** -->
-<!ENTITY % FEDORA-ENTITIES-EN SYSTEM "../docs-common/common/fedora-entities-en.ent">
+<!ENTITY % FEDORA-ENTITIES-EN SYSTEM "../docs-common/common/fedora-entities-it.ent">
%FEDORA-ENTITIES-EN;
<!ENTITY BOOKID "selinux-faq-1.3-8 (2005-01-20-T16:20-0800)"> <!-- version of manual and date -->
18 years, 5 months
release-notes RELEASE-NOTES-it.xml,1.2,1.3
by fedora-docs-commits@redhat.com
Author: tombo
Update of /cvs/docs/release-notes
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv14965/release-notes
Modified Files:
RELEASE-NOTES-it.xml
Log Message:
Index: RELEASE-NOTES-it.xml
===================================================================
RCS file: /cvs/docs/release-notes/RELEASE-NOTES-it.xml,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- RELEASE-NOTES-it.xml 5 Nov 2005 15:02:18 -0000 1.2
+++ RELEASE-NOTES-it.xml 19 Nov 2005 21:05:38 -0000 1.3
@@ -34,9 +34,9 @@
<!-- *************** COMMON FDP entities *************** -->
-<!ENTITY % FEDORA-ENTITIES-EN SYSTEM "../docs-common/common/fedora-entities-en.ent">
+<!ENTITY % FEDORA-ENTITIES-EN SYSTEM "../docs-common/common/fedora-entities-it.ent">
%FEDORA-ENTITIES-EN;
- <!ENTITY LEGALNOTICE SYSTEM "../docs-common/common/legalnotice-en.xml">
+ <!ENTITY LEGALNOTICE SYSTEM "../docs-common/common/legalnotice-it.xml">
<!-- *************** Local entities *************** -->
18 years, 5 months
docs-common/common fedora-entities-it.ent,NONE,1.1
by fedora-docs-commits@redhat.com
Author: tombo
Update of /cvs/docs/docs-common/common
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv13383/docs-common/common
Added Files:
fedora-entities-it.ent
Log Message:
***** Error reading new file: [Errno 2] No such file or directory: 'fedora-entities-it.ent'
18 years, 5 months
docs-common/common obsoletenotice-it.xml,NONE,1.1
by fedora-docs-commits@redhat.com
Author: tombo
Update of /cvs/docs/docs-common/common
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv13344/docs-common/common
Added Files:
obsoletenotice-it.xml
Log Message:
--- NEW FILE obsoletenotice-it.xml ---
<note>
<title>DOCUMENTO OBSOLETO</title>
<para>
Questo documento �� relativo a una versione di &FC; che non �� pi��
supportata. Cambiamenti nelle ultime versioni di &FC; possono aver reso questo
documento inaccurato. Sei pregato di controllare il sito web di &FDP; su
&FDPDOCS-URL; per la versione attuale prima di continuare a leggere questo
documento.
</para>
<para>
Questa versione del documento non sar�� cambiato o emendato.
</para>
</note>
18 years, 5 months
docs-common/common legalnotice-section-it.xml,NONE,1.1
by fedora-docs-commits@redhat.com
Author: tombo
Update of /cvs/docs/docs-common/common
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv13322/docs-common/common
Added Files:
legalnotice-section-it.xml
Log Message:
--- NEW FILE legalnotice-section-it.xml ---
<!--
Use this legalnotice for no-chunks/single-page HTML output. It is an optional
usage to move the bulk of the legalnotice to another location in the document.
If you use this legalnotice, you must include a call to the
LEGALNOTICE-NOCHUNKS or LEGALNOTICE-RELNOTES. This gets the legal material in
the proper <legalnotice /> container.SECTION entity, or include a similar <section> in your document.
The call to LEGALNOTICE-SECTION must happen where a <section> is otherwise
allowed. One good location is immediately following an introduction.
-->
<section id="sn-legalnotice">
<title>Note legali</title>
&LEGALNOTICE-CONTENT;
</section>
18 years, 5 months
docs-common/common legalnotice-relnotes-it.xml,NONE,1.1
by fedora-docs-commits@redhat.com
Author: tombo
Update of /cvs/docs/docs-common/common
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv13300/docs-common/common
Added Files:
legalnotice-relnotes-it.xml
Log Message:
--- NEW FILE legalnotice-relnotes-it.xml ---
<!-- $Id: -->
<!--
<!DOCTYPE legalnotice PUBLIC "-//OASIS//DTD DocBook V4.2//EN"
"http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd" [
<!ENTITY BOILERPLATE "This header makes editing XML easier" >
]>
-->
<!--
Use this legalnotice for no-chunks/single-page HTML output. It is an optional
usage to move the bulk of the legalnotice to another location in the document.
If you use this legalnotice, you must include a call to the
LEGALNOTICE-SECTION entity, or include a similar <section> in your document.
The call to LEGALNOTICE-SECTION must happen where a <section> is otherwise
allowed. One good location is immediately following an introduction.
-->
<legalnotice id="legalnotice">
<para>
Questo documento �� rilasciato sotto i termini della GNU Free Documentation
License. Per maggiori dettagli, leggi le note legali complete su <xref
linkend="sn-legalnotice" />.
</para>
<tip>
<title>Le ultime note di rilascio sul Web</title>
<para>
Queste note di rilascio possono essere aggiornate. Visita <ulink
url="http://fedora.redhat.com/docs/release-notes/">http://fedora.redhat.com/docs/release-notes/</ulink>
per vedere le ultime note di rilascio per &DISTRO; &DISTROVER;.
</para>
</tip>
</legalnotice>
18 years, 5 months
docs-common/common legalnotice-it.xml,NONE,1.1
by fedora-docs-commits@redhat.com
Author: tombo
Update of /cvs/docs/docs-common/common
In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv13278/docs-common/common
Added Files:
legalnotice-it.xml
Log Message:
--- NEW FILE legalnotice-it.xml ---
<!-- $Id: -->
<!--
<!DOCTYPE legalnotice PUBLIC "-//OASIS//DTD DocBook V4.2//EN"
"http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd" [
<!ENTITY BOILERPLATE "This header makes editing XML easier" >
]>
-->
<legalnotice id="legalnotice">
&LEGALNOTICE-CONTENT;
</legalnotice>
18 years, 5 months