Mailinglist Archive: zypp-devel (148 mails)

["Duncan Mac-Vicar P." <dmacvicar@xxxxxxx>]

Dominique Leuenberger wrote:
> > > > On 3/20/2008 at 14:59, Duncan Mac-Vicar Prett <dmacvicar@xxxxxxx> wrote:
> > > >         
> > Dominique, I am trying to backport libzypp for older distros in 
> > zypp:Backport.
> >
> > You can help me there!. For that error, the problem is 10.2 has a old 
> > swig, in OBS I solve this by backporting swig only for building.Actually 
> > there is a 10.2 satsolver there. But libzypp is another story ;-)
> >
> >     
>
> Duncan,
>
> in my own playground (home:dimstar) I just compiled (so far only for openSUSE 
> 10.2) libsatsolver (works indeed with a later swig) and libzypp compiled fine 
> too.
>   
Well, it was already compiling in zypp:Backport :-)
> There is just a very awkward thing in the spec file, which I fail to 
> understand:
>
> # %if 0%{?suse_version}  
> # BuildRequires:  hicolor-icon-theme rpm-devel update-desktop-files  
> # %endif  
>
> On what ground should any package require hicolor-icon-theme as a 
> BuildRequires? Maybe somebody has an idea.. I did not find anything useful in 
> this file rpm.
>   
I think the package manager .desktop file.
> anyhow, at the moment zypper for 10.2/x86_64 is being built and I should soon 
> see the result of that... for i586 it's still scheduled... and if this works, 
> I can soon start to fire up a VM and make some tests... for sure I will kill 
> yast with it (as yast depends on libzypp.so.215 on a 10.2 installation... but 
> as I wrote in my first mail, this is not a big issue (yet) for me...
>
> but of course if we want to offer it publically, this should be solved 
> somehow to... so we'd need to update the whole yast stack on such a machine.
>
> Dominique
>
>   
Thats why I have YaST:Backport as a repo that builds Factory packages on
top of zypp:Backport. Once zypp:Backport compiles on 10.2, we can try to
get YaST:Backport to compile too.

Duncan

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