Hi there, I was coding a python test case for this, but I can't seem to be able to initialize zypp with the local RPM database. import zypp _zypp = zypp.ZYppFactory_instance().getZYpp() _target = _zypp.initializeTarget(zypp.Pathname(" ? ")) (...) _pool = _zypp.pool() print "pool size:", _pool.size() # zero :-( What string should I pass to _zypp.initializeTarget() ? I have tried to dig up yast2 code on this, but couldn't pin down where initialization of the local database gets done, and other sources weren't more successful. Thanks, Ricardo Quoting "Ricardo Cruz" <rpmcruz@alunos.dcc.fc.up.pt>:

Hi there,

So, another approach would be to manually do something like:

l = [] for p in pool: if p.installedBySolver(): needed = False for q in pool: if q.requires (p): needed = True break if not needed: l.append (p)

Is there some p.installedBySolver() method though?

If not, is there a cheaper way to implement then, than digging up the respective log in parser::HistoryLogReader.

Thanks, Ricardo

---------------------------------------------------------------- This message was sent using IMP, the Internet Messaging Program. -- To unsubscribe, e-mail: zypp-devel+unsubscribe@opensuse.org For additional commands, e-mail: zypp-devel+help@opensuse.org

Quoting "Michael Andres" <ma@suse.de>:

On Wednesday 08 September 2010 16:01:36 Ricardo Cruz wrote:

...

  What string should I pass to _zypp.initializeTarget() ?

The root of your system. Usually '/', unless you use --root.

That was one of my first tries, but it's of no use. pool.size() still returns 0, and I know I have packages installed in my system. :) Anyhow, digging up some of mountain zypp, it seems I may have to also issue a: zyppPtr->target()->load(); But I still have to give it a try.

...

  I have tried to dig up yast2 code on this, but couldn't

Yast is too confuising ;). Try zypper or some of the tests/examples in the libzypp git.

I've looked at libzypp's test directory, and they seemed to make use of temporary databases.

Beware, the examples are pretty outdated but at least list_resolvables works.

There aren't many of them either. rick2@andor:~/Documentos/yast/libzypp/examples$ ls CMakeLists.txt COW_debug.cc EditionCompare.cc README whatprovides.cc

(patches/suggestions are wellcome ;) I added an onSystemByUser call as you asked for some 'p.installedBySolver' in the previous mail. Since libzypp-7.5.0: + /** Whether this is known to be installed on behalf of a user request. + * \note This is a hint guessed by evaluating an available install history. + * Returns \c false for non-system (uninstalled) solvables, or if no history + * is available. + */ + bool onSystemByUser() const;

Very nice, thanks. Please just add there a comment on the performance of the function, otherwise people may unnecessarily abuse it. I assume it's O(N): you iterate through the logs every time the function is called. Much appreciated, Ricardo ---------------------------------------------------------------- This message was sent using IMP, the Internet Messaging Program. -- To unsubscribe, e-mail: zypp-devel+unsubscribe@opensuse.org For additional commands, e-mail: zypp-devel+help@opensuse.org

Quoting "Michael Andres" <ma@suse.de>:

On Thursday 09 September 2010 17:06:18 Ricardo Cruz wrote:

...

Very nice, thanks. Please just add there a comment on the performance of the function, otherwise people may unnecessarily abuse it. I assume it's O(N): you iterate through the logs every time the function is called.

No, the history file is parsed once on demand, and the cache (hash<int>) is invalidated after a commit. So it should not perform that bad.

Very cool. But it's not obvious from the comment, so I'd append to the comment something like "(cached after first run)". Cheers, Ricardo ---------------------------------------------------------------- This message was sent using IMP, the Internet Messaging Program. -- To unsubscribe, e-mail: zypp-devel+unsubscribe@opensuse.org For additional commands, e-mail: zypp-devel+help@opensuse.org