Mailinglist Archive: zypp-devel (12 mails)
| < Previous | Next > |
Re: [zypp-devel] RFC zypper addlock --repo
- From: Klaus Kaempf <kkaempf@xxxxxxx>
- Date: Thu, 24 Nov 2011 12:04:47 +0100
- Message-id: <20111124110447.GA20481@heron.suse.de>
* Michael Schroeder <mls@xxxxxxx> [Nov 24. 2011 12:01]:
I wonder how this is different from "disable repo" ?
Agreed, there's no way to find the originating repo from the
information in the rpm database.
zypper could do it by itself from the information stored in the
history log.
Klaus
---
SUSE LINUX Products GmbH, GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer, HRB
16746 (AG Nürnberg)
Maxfeldstraße 5, 90409 Nürnberg, Germany
--
To unsubscribe, e-mail: zypp-devel+unsubscribe@xxxxxxxxxxxx
To contact the owner, e-mail: zypp-devel+owner@xxxxxxxxxxxx
On Thu, Nov 24, 2011 at 09:49:52AM +0100, Michael Andres wrote:
Bnc#732027 reveals a flaw in
zypper addlock --repo <repo> ...
This command will lock all matching packages in <repo>, i.e. prevent them
from
being installed.
I wonder how this is different from "disable repo" ?
But in addition to this (or instead of) you may want to lock already
installed
packages originating from this repo as well. I suppose this is the more
interesting usecase, and I'm think this should be the default for --repo.
So what about adding 2 new addlock options:
addlock --repo locks in repo and installed from repo
++ addlock --from-repo locks installed from repo
++ addlock --repo-only locks in repo
I don't see a sane way to implement "--from-repo".
Agreed, there's no way to find the originating repo from the
information in the rpm database.
zypper could do it by itself from the information stored in the
history log.
Klaus
---
SUSE LINUX Products GmbH, GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer, HRB
16746 (AG Nürnberg)
Maxfeldstraße 5, 90409 Nürnberg, Germany
--
To unsubscribe, e-mail: zypp-devel+unsubscribe@xxxxxxxxxxxx
To contact the owner, e-mail: zypp-devel+owner@xxxxxxxxxxxx
| < Previous | Next > |