On Mon, Jul 27, 2009 at 1:01 PM, Michael Schroeder <mls@xxxxxxx> wrote:
BTW, if you want a wider audience for your project, outside the narrow
circle of people involved in rpm development :=) for example, so that it can be
considered for inclusion in different distributions from OpenSUSE, you should, as
usual, publish it as a separate and autonomous project. This is what do
yum and smart for example, both in Fedora repository.
Hi folks,
I'm the author of the "libsatsolver" library, a library solves
package dependencies with a SAT algorithm.
This library is currently used in SUSE by YaST/zypp. I'm currently
trying to make it less SUSE specific like adding support for package
coloring and different repo handling, but I'm pretty sure I didn't
catch all things where Fedora is different from SUSE.
To test things I've written a small application called "solv" that
works like a very tiny package manager. It's available via:
http://software.opensuse.org/search?baseproject=Fedora:11&q=libsatsolver-demo
(To get the src rpm search for "libsatsolver")
The package contains just a single file, "/usr/bin/solv". It can
be run as normal user, but then the transaction can't be commited.
Also, the repository metadata caching mechanism needs write access
to /var/cache/solv. If it can't write there, it still works but
downloads the metadata again every time it is called.
So, if you have some spare time, could you give it a try and tell
me where it works well/ does stupid things/ doesn't work at all?
Thanks,
Michael.
Regards
(aside)
in a (perhaps old but not i cannot check now the latest release) RHEL5 release glibc don't have qsort_r (http://sourceware.org/bugzilla/show_bug.cgi?id=173) so the code don't compile. http://sourceware.org/ml/glibc-cvs/2007-q4/msg00436.html
-- fedora-devel-list mailing list fedora-devel-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/fedora-devel-list
