Mailinglist Archive: zypp-devel (70 mails)
| < Previous | Next > |
[zypp-devel] Re: sat solver enhancements and questions
- From: Klaus Kaempf <kkaempf@xxxxxxx>
- Date: Fri, 26 Oct 2007 13:44:35 +0200
- Message-id: <20071026114435.GB18809@xxxxxxxxxxxxx>
* Duncan Mac-Vicar Prett <dmacvicar@xxxxxxx> [Oct 26. 2007 13:32]:
Cool ! Thanks !
And a nice API. A couple of extensions/enhancements here and there and
its going to be beautiful ;-)
What does 'select' mean ? This looks more like a 'find' or 'get' to me.
[...]
Since in 99.9% of all cases, one operates with a single pool (its just
a collection of repos anyway), the pool should be made implicit.
Just go ahead and do the fixes, I'd say !
+1 vote from me !
Go ahead ! I added autocrap just because it was easy (for me) and my
cmake experience is next to zero.
Klaus
--
To unsubscribe, e-mail: zypp-devel+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: zypp-devel+help@xxxxxxxxxxxx
Hi guys,
I have been playing with the sat solver motivated by being able to use it
from
ruby scripts or rails apps, and also to familiarize myself with the internals
I have in my local git a patch that adds the following:
(~dmacvicar/sat-ruby-cmake.diff)
- beatiful ruby bindings (and 99% of the stuff needed to have perl, python,
java, etc)
- cmake build support
Cool ! Thanks !
And a nice API. A couple of extensions/enhancements here and there and
its going to be beautiful ;-)
q = Queue.new
puts q.empty?
r = pool.select_solvable(s, 'gnome-desktop')
What does 'select' mean ? This looks more like a 'find' or 'get' to me.
[...]
What is missing in the bindings part:
- translation of attributes like name from Id to string in a transparent way
(the fact that the conversion function needs a pool is my limiting factor
right now)
Since in 99.9% of all cases, one operates with a single pool (its just
a collection of repos anyway), the pool should be made implicit.
- fixing of attributes names to follow ruby conventions.;-)
What can be enhanced in the C api:
- choose conventions. Come on, this is not something technical, just some
discipline that helps people. I dont think having one method called
pool_something and then other called queuesomething makes sense except to
annoy.. The convention class_action( class*, args ) is pretty standard in C
OO code. Use it, but don't mix or you make people have to read the code to
guess method names.
Just go ahead and do the fixes, I'd say !
- Source name. It was very difficult to standarze the name in libzypp,
product
management and other products to repositories. Calling it Source is going
back to 10.2 and introduce more confusion. The official word is repo now, why
not use it?
+1 vote from me !
- there is a bug when you add a empty system repo to the solver, it segfaults.[...]
- I had some trouble wth the bool stuff (typedef _Bool bool) and swig
I have no problem to maintain the cmake part (even in paralell), unless
everyone loves it and it can be made the default. it is ok to commit it?
Go ahead ! I added autocrap just because it was easy (for me) and my
cmake experience is next to zero.
Klaus
--
To unsubscribe, e-mail: zypp-devel+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: zypp-devel+help@xxxxxxxxxxxx
| < Previous | Next > |