Mailinglist Archive: zypp-devel (149 mails)

< Previous Next >
Re: [zypp-devel] services in zypper
  • From: Jan Kupec <jkupec@xxxxxxx>
  • Date: Wed, 03 Sep 2008 13:47:51 +0200
  • Message-id: <48BE7967.10000@xxxxxxx>
Martin Vidner wrote:
On Wed, Sep 03, 2008 at 01:08:40PM +0200, Jan Kupec wrote:
Michael Schroeder wrote:
On Tue, Sep 02, 2008 at 06:08:19PM +0200, Jan Kupec wrote:
Hi there, i'm finally back :O) The situation goes like this:

- rug's service-* command were just aliases for the *repo commands of
zypper until 11.0
- now that zypper is getting support for services, new *service commands
have been added, and the rug's service-* commands are now aliases for
these new commands.
Why's there a different interface? Can't zypper just use the repo
command set and use type "service" for a service?
Because it's quite different thing - it's a repository index, which serves for auto-managing repositories on your machine - it's one level higher in the repo management.

You can't e.g. specify a service as the --repo (well, that could be transformed into individual repos), you still need two different command for listing services and listing repos (standalone and the ones from services), and you still need to manipulate both the services, and the repos they contain, which you can't do using one command set (how would you e.g. disable a repository within a service?).


You can treat ordinary repositories as trivial services with a
single repo that is always subscribed. That way, "service" commands
will keep working on repos.

Agreed, that's how we want it (should already be working like that). But this is a different topic from what Michael asked.

To unsubscribe, e-mail: zypp-devel+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: zypp-devel+help@xxxxxxxxxxxx

< Previous Next >