Mailinglist Archive: zypp-devel (102 mails)

[Michael Matz <matz@xxxxxxx>]

Hi,

On Wed, 11 Mar 2009, Matt Barringer wrote:

> On Wed, 11 Mar 2009, Klaus Kaempf wrote:
>
> > What would be the use case for such a call ?
> >
> > And, more important, how would such a repo come into existance ?
> > I currently know of three ways to create a repo in satsolver
> > - load from .solv file
> > - load from rpm database
> > - manual creation (add empty repo, add solvables to this repo)
> >
> > Only the first two are of practical use, the last one is more for
> > development and testing.
>
> We manually create repos as part of SUSE Studio.  The use case would be us not
> needing to copy repo_write.c into our source tree whenever we update our copy
> of libsatsolver.

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.


Ciao,
Michael.
-- 
To unsubscribe, e-mail: zypp-devel+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: zypp-devel+help@xxxxxxxxxxxx