OK, but I leave the benchmark for you;-) Note: Long "dependency paths" like in smoke001.py may cause notable slowdown. I made a quick "hack", so probably I made some mistakes...
Bye
Well, resolvedeps is also quite hard to read (but seems OK). Imho we should share some code between alpm_sync_addtarget and resolvedeps: I mean they could use common search_for_literal(), search_for_satisfier() functions. By doing this alpm_resolvedeps would be much clearer and '-S provision' would be more general, user could do -S 'depend>=2.0' if he wants to do so (he got an unsatisfied dependency error after -A) and we can slowly kill whatprovides... (foo provides bar is a special case of foo satisfies bar) Bye ---------------------------------------------------- SZTE Egyetemi Könyvtár - http://www.bibl.u-szeged.hu This mail sent through IMP: http://horde.org/imp/