From: Martin Vidner <mvidner@suse.cz>
Date: Mon, 3 Sep 2007 14:05:38 +0000 (+0000)
Subject: Documented /etc/zypp/locks
X-Git-Tag: BASE-SuSE-Linux-10_3-Branch~62
X-Git-Url: http://review.tizen.org/git/?a=commitdiff_plain;h=953b8e77fce04b20460f99848bb3ef23ca30ab74;p=platform%2Fupstream%2Fzypper.git

Documented /etc/zypp/locks
---

diff --git a/doc/zypper.8 b/doc/zypper.8
index d9e0ef3..ac79087 100644
--- a/doc/zypper.8
+++ b/doc/zypper.8
@@ -346,11 +346,38 @@ Ignore GPG check failures and continue. If a GPG issue occurs when using this op
 .I \-R, \-\-root <dir>
 Operates on a different root directory.
 
+.SH "LOCKS"
+.LP
+The file
+.B /etc/zypp/locks
+can contain a list of packages to be locked. These will not be updated
+or removed by the solver.
+
+Empty lines and lines beginning with \fB#\fR are ignored. Each line is of the form
+"\fIPATTERN \fR[ \fIOP EDITION \fR]"
+where
+.I PATTERN
+is a name with shell wildcards \fB?\fR and \fB*\fR,
+.I OP
+is one of \fB< <=  = >=  >\fR,  and 
+.I EDITION
+is \fI VERSION\fR[\fB-\fIRELEASE\fR].
+
+.TP
+Example:
+# Don't update the old KDE
+.br
+kde* < 3.5
+
+
 .SH "FILES"
 .TP
 .B /etc/zypp/repos.d
 Directory containing repository configuration (*.repo) files. You can use the \fBrepo\fR commands to manipulate these files, or you can edit them yourself. In either case, after doing the modifications, executing \fBzypper refresh\fR is strongly recommended.
 .TP
+.B /etc/zypp/locks
+File with package lock definitions, see the section LOCKS.
+.TP
 .B /var/cache/zypp/raw
 Directory for storing raw metadata contained in repositories.
 .TP