Mailinglist Archive: zypp-devel (102 mails)
| < Previous | Next > |
Re: [zypp-devel] New solver call : resolveQueue
- From: Michael Schroeder <mls@xxxxxxx>
- Date: Wed, 11 Mar 2009 14:59:30 +0100
- Message-id: <20090311135930.GA17763@xxxxxxx>
On Wed, Mar 11, 2009 at 01:54:34PM +0100, Michael Matz wrote:
I don't know why the repo_* functions can't live in libsatsolver.
They were always meant to be in there.
I think they were excluded because they add dependencies to
external libraries, but we now have repo_helix (yuck!) in libsatsolver
so that reason is moot.
Cheers,
Michael.
--
Michael Schroeder mls@xxxxxxx
SUSE LINUX Products GmbH, GF Markus Rex, HRB 16746 AG Nuernberg
main(_){while(_=~getchar())putchar(~_-1/(~(_|32)/13*2-11)*13);}
--
To unsubscribe, e-mail: zypp-devel+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: zypp-devel+help@xxxxxxxxxxxx
I sometimes thought about splitting the common code of tools/*.c (there's
much, in particular the several XML parsing constructs) into a new
libsattools library, which would also contain the repo_write stuff.
Eventually I get to that when I do the static->shared lib transition.
I would hope it's acceptable for you to have to link against an additional
lib.
I don't know why the repo_* functions can't live in libsatsolver.
They were always meant to be in there.
I think they were excluded because they add dependencies to
external libraries, but we now have repo_helix (yuck!) in libsatsolver
so that reason is moot.
Cheers,
Michael.
--
Michael Schroeder mls@xxxxxxx
SUSE LINUX Products GmbH, GF Markus Rex, HRB 16746 AG Nuernberg
main(_){while(_=~getchar())putchar(~_-1/(~(_|32)/13*2-11)*13);}
--
To unsubscribe, e-mail: zypp-devel+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: zypp-devel+help@xxxxxxxxxxxx
| < Previous | Next > |