> > It may make a month or so until updated eina and evas will pass NEW. > > > > I think it is better to have your package at pkg-fso than have broken > > system during all that time. > > There is another possibility: Get a new python-evas package in shape and > put it in NEW. Until it is through there, we put all the libe* and > python-e* package that are waiting in NEW in the pkg-fso repository. I’d > prefer this, as it would allow me to go ahead with the packaging of SHR.
All packages that I've built for sponsoring pkg-e uploads, are in my local repo at deb http://yoush.homelinux.org:8079.denian not-yet-in-debian main Currently there are not-yet-in-debian|main|source: ecore 0.9.9.050+svn20081201-1 not-yet-in-debian|main|source: edbus 0.5.0.050+svn20081126-1 not-yet-in-debian|main|source: edje 0.9.9.050+svn20081206-1 not-yet-in-debian|main|source: efreet 0.5.0.050+svn20081114-1 not-yet-in-debian|main|source: eina 0.0.1~svn20081120-1 not-yet-in-debian|main|source: evas 0.9.9.050+svn20081206-1 Source and binary-i386 packages are there. bibnary-armel are still not there, because I still can't make qemubuilder working :(
signature.asc
Description: This is a digitally signed message part.
_______________________________________________ Smartphones-userland mailing list Smartphones-userland@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/smartphones-userland
