Mailinglist Archive: zypp-devel (149 mails)

< Previous Next >
Re: [zypp-devel] Comments/ideas for libzypp-bindings-python
  • From: Jano Kupec <jkupec@xxxxxxx>
  • Date: Fri, 05 Sep 2008 09:37:33 +0200
  • Message-id: <48C0E1BD.4010802@xxxxxxx>
Jan-Simon Möller wrote:
Moin moin!
Just some observations/ideas and random stuff.

RepoManager:
* I miss iterators like knownRepos() and knownServices() returning the
respective RepoInfo
** Reason: I can easily add repositories, but its hard to find the already
known repos from RepoManager
to query/refresh/whatever

knownRepositories() should be there, but is deprecated anyway. Use repoBegin(), repoEnd() iterators (plus repoSize(), repoEmpty()). I don't know how that is translated into python though. (BTW, we should name the methods at least reposBegin, not repoBegin).

* If I use the nice feature addService("alias", URL("pathtorepofile")) i'm
stuck refreshing the repos
as >>> myrepomanager.refreshServices() fails with RuntimeError: Parse error

Please, forget services for now (there are no working services out there to test them yet). Use just the repository staff in the RepoManager (addRepository, etc).

* I've no chance to iterate and/or get repoinfos for handling.
* i've an url and an alias, but no serviceinfo up to now, but TypeError: in method 'RepoManager_refreshService', argument 2 of type 'zypp::ServiceInfo const &'
requires a ServiceInfo :/

You can create one (or get an existing one, just like you did below)

* ok, getService(alias) works ... but syntax is bad imho... myrepomanager.refreshService(myrepomanager.getService("alias")) or ?
If i can addService("alias", URL) why not refreshService("alias")

Yeah we can add such method...

** btw refreshService fails here with "RuntimeError: Parse error" (same repos
work done with repoinfo)

Yes, that's because you don't have _service_, you have an ordinary repository, i guess.

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

< Previous Next >
Follow Ups
References