Mailinglist Archive: zypp-devel (50 mails)
| < Previous | Next > |
[zypp-devel] lock docs
- From: Martin Vidner <mvidner@xxxxxxx>
- Date: Mon, 3 Sep 2007 11:31:58 +0200
- Message-id: <20070903093158.GA5498@xxxxxxxxxxxxxxxx>
On Mon, Sep 03, 2007 at 09:48:23AM +0200, Stanislav Višňovský wrote:
> Hi!
>
> Maybe it's time to introduce 'man zypp.conf' or at least a fully commented
> zypp.conf example. Without this, the configuration features will get lost.
>
> Stano
Yes. In a related news, I documented the locks for the zypper man
page.
Can someone (Duncan?) explain the sematics better?
In particular I am concerned with the lock "kde* < 3.5" being
misinterpreted as "keep all KDE packages below 3.5".
--
Martin Vidner, YaST developer
http://en.opensuse.org/User:Mvidner
Kuracke oddeleni v restauraci je jako fekalni oddeleni v bazenu
Index: zypper.8
===================================================================
--- zypper.8 (revision 7072)
+++ zypper.8 (working copy)
@@ -346,11 +346,38 @@
.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
> Hi!
>
> Maybe it's time to introduce 'man zypp.conf' or at least a fully commented
> zypp.conf example. Without this, the configuration features will get lost.
>
> Stano
Yes. In a related news, I documented the locks for the zypper man
page.
Can someone (Duncan?) explain the sematics better?
In particular I am concerned with the lock "kde* < 3.5" being
misinterpreted as "keep all KDE packages below 3.5".
--
Martin Vidner, YaST developer
http://en.opensuse.org/User:Mvidner
Kuracke oddeleni v restauraci je jako fekalni oddeleni v bazenu
Index: zypper.8
===================================================================
--- zypper.8 (revision 7072)
+++ zypper.8 (working copy)
@@ -346,11 +346,38 @@
.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
| < Previous | Next > |