Update manpage to give some repo URI examples (bnc#680630)

diff --git a/doc/zypper.8 b/doc/zypper.8
index 31bbca5..d9d6417 100644 (file)
--- a/doc/zypper.8
+++ b/doc/zypper.8
@@ -109,8 +109,7 @@ messages to be run or shown during installation of the update.
 \- group of packages which are necessary to install a product.
 .br
 .B srcpackage
-\- source code package (.src.rpm). This type works in \fBsearch\fR and
-   \fBinstall\fR commands.
+\- source code package (.src.rpm). This type works in \fBsearch\fR and \fBinstall\fR commands.
 .LP
 Throughout this manual we will refer to resolvables simply as \fIpackages\fR
 and to resolvable types as \fIpackage types\fR. These type names can be used
@@ -908,7 +907,6 @@ List all packages providing the specified capability. See also the \fBinstall\fR
 
 
 .SS Repository Management
-
 .PP
 Zypper is able to work with YaST, RPM-MD (yum) software repositories, and
 plain directories containing .rpm files.
@@ -923,7 +921,73 @@ uniquely identifies the repository on the system.
 The \fIalias\fR, \fIname\fR, \fIURI\fR, or the \fInumber\fR from \fBzypper repos\fR list can be used to
 specify a repository as an argument of various zypper commands and
 options like \fBrefresh\fR, \fB--repo\fR, or \fB--from\fR.
+.TP ============================================================================
+Supported URI formats:
+.TP ============================================================================
+CD or DVD drive
+Optionally with \fIdevices\fR list for probing.
+
+.B cd:///
+.br
+.B dvd:/subdir\fI?devices=/dev/sr0,/dev/sr1
+.TP ============================================================================
+FTP/HTTP/HTTPS directory tree
+The ftp URL scheme supports absolute and relative paths to the default ftp server directory (RFC1738, Section 3.2.2). To use an absolute path, you have to prepend the path with an additional slash, what results in a "/%2f" combination (second "/" encoded to "%2f") at the begin of the URL path. This is important, especially in user authenticated ftp, where the users home is usually the default directory of the server (except when the server chroots into the users home directory).
+
+Explicit proxy settings may be passed via optional parameters \fIproxy\fR, \fIproxyport\fR, \fIproxyuser\fR and \fIproxypass\fR.
+
+HTTP authentication methods to use can be defined as comma separated list via optional parameter \fIauth\fR. Valid methods are e.g. 'basic', 'digest', 'ntlm', 'negotiate'. Note, that this list depends on the list of methods supported by the curl library.
+
+.br
+.B ftp://user:pass@server/path/to/media/dir
+.br
+.B ftp://user:pass@server/%2fhome/user/path/to/media/dir
+.br
+.B http://user:pass@server/path
+.br
+.B https://user:pass@server/path\fI?proxy=foo&proxyuser=me&proxypass=pw
+
+.TP ============================================================================
+Disk volume (partition)
+Mandatory \fBdevice\fR parameter specifying the name of the block device to mount. The name of the optional \fIfilesystem\fR defaults to "auto".
+
+.B hd:/subdir?device=/dev/sda1\fI&filesystem=reiserfs
+.TP ============================================================================
+Local directory tree
+
+.B dir:/directory/name
+.TP ============================================================================
+Media in an ISO image (loopback mounted)
+Mandatory \fBiso\fR parameter specifying the name of the iso file. Optional \fIurl\fR parameter specifying the URL to the directory containing the iso file. Optional \fImnt\fR parameter specifying the preferred attach point for the source media url. Optional \fIfilesystem\fR name of the filesystem used in the iso file. Defaults to "auto".
 
+.B iso:/?iso=CD1.iso\fI&url=nfs://server/path/to/media
+.br
+.B iso:/?iso=CD1.iso\fI&url=hd:/?device=/dev/hda
+.br
+.B iso:/subdir?iso=DVD1.iso\fI&url=nfs://nfs-server/directory&mnt=/nfs/attach/point&filesystem=udf
+.TP ============================================================================
+NFS exported directory tree
+To use NFSv4 either use schema \fItnfsv4://\fR or pass an optional parameter \fItype=nfs4\fR. Additional \fImountoptions\fR can be passed as comma separated list. Defaults to "ro".
+
+.B nfs://nfs-server/exported/path
+.br
+.B nfs://nfs-server/exported/path\fI?mountoptions=ro&type=nfs4
+.br
+.B nfs4://nfs-server/exported/path\fI?mountoptions=ro
+.TP ============================================================================
+CIFS/SMB directory tree
+There is no difference between cifs and smb scheme (any more). In both cases the \fIcifs\fR filesystem is used. Additional \fImountoptions\fR can be passed as comma separated list. Defaults to "ro,guest". Specify "noguest" to turn off "guest". This is necessary if Samba is configured to reject guest connections.
+
+Optional \fIworkgroup\fR or \fIdomain\fR parameter set the name of the workgroup. As alternative to passing \fIusername:password\fR in the URI authority the parameters \fIuser\fR and \fIpass\fR can be used.
+
+.B smb://servername/share/path/on/the/share
+.br
+.B cifs://usenr:passw@servername/share/path/on/the/share\fI?mountoptions=ro,noguest
+.br
+.B cifs://usern:passw@servername/share/path/on/the/share\fI?workgroup=mygroup
+.br
+.B cifs://servername/share/path/on/the/share\fI?user=usern&pass=passw
+.PP
 Apart from the above, repositories have several other properties which can be
 set using the commands described in this section below, or by manually
 editing the repository definition files (.repo files, see section FILES).
@@ -989,15 +1053,14 @@ Add repositories from a repo file:
 .br
 .B $ zypper ar myreposbackup.repo
 
-
 .TP
 .B removerepo (rr) [options] <alias|name|#|URI> ...
 Delete repositories specified by aliases, names, numbers or URIs.
 .TP
-\fI    --loose-auth\fR
+.I --loose-auth
 Ignore user authentication data in the URI
 .TP
-\fI    --loose-query\fR
+.I --loose-query
 Ignore query string in the URI
 
 .TP