Mailinglist Archive: zypp-devel (148 mails)

["Dominique Leuenberger" <Dominique.Leuenberger@xxxxxxxxxxxxx>]

duncan,

> > > On 3/21/2008 at 16:29, "Duncan Mac-Vicar P." <dmacvicar@xxxxxxx> wrote:
> > 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 :-)

Not quiet.. only libsatsolver was there.. libzypp (as stated above by me being 
built in my home: was not compiling successful..)


> > 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.

Ok, anyhow it's a small rpm being added as build dependency at probably not 
worth to find out if it's really needed or not.

> 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.

as you might have seen, zypper, libzypp and all the tools in zypp:backport are 
now succesfully compiled ;) (on Fedora 8, openSUSE 10.2 and 10.3; for SLE it's 
an issue with ruby vendor directory.. on SLE, it seems to install in site 
directory... I'll add a patch on the weekend for this).
I'm already playing in yast:backport, some more progress is going on (slowly, 
as not to many workers are alive.. most seem to be on holiday).
One thing we will have to adjust in the project configfile is to ignore 
yast2-devel and use yast2-devel-doc instead (or patch the spec to not make this 
difference for openSUSE < 1030. as it's set now)

Dominique


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