Hi > -----Original Message----- > From: Dumez, Christophe [mailto:[email protected]] > Sent: Wednesday, June 08, 2011 10:47 PM > To: Ohly, Patrick > Cc: Zhu, Peter J; Srinivasa Ragavan; [email protected] > Subject: Re: [meego-packaging] package changes for EDS + SyncEvolution in > MeeGo > > Hi, > > > I need Chris' time for development of KCal-EDS and as he's new to this > > whole OBS thing, getting all these packages right is slow and tedious > > for him (my interpretation, he hasn't complained yet). > I think I understand OBS just fine now. The thing is that I was not > aware about this BMC# requirement before though. Now that I know this, > it should go fine. > Note that the packaging problems were not for *my* packages but in > gdbus-binding-tool and python-argparse which I SR'ed without change. > > I fixed the packages in eds repo last night, according to Peter Zhu's comment. Thank you for quick response, it's really appreciated. The only last comments from packaging point is for gdbus-binding-tools, that might should go to Srinivasa. Srinivasa,
It uses yaml but update spec file directly for somethings like below # >> install pre # << install pre make DESTDIR=$RPM_BUILD_ROOT LIBTOOL=/usr/bin/libtool install rm $RPM_BUILD_ROOT/usr/lib/libgdbus-codegen.la # >> install post %post devel /sbin/ldconfig So in this case, if you are not familiar yaml, just drop it and use spec file directly. You could fix it next time Patrick Seem we should set a devel project for all these packages as eds since all the new stuff including eds/syncevolution are now submitted directly from there. I do see some guys have submissions for the packages, you don't want them to clob your changes :-). Are you ok? Peter > We should be fine now. I did not SR yet because there is still the > licensing problem for gdbus-binding-tool and the possible dependency > on Python problem. > What should we do about that? I personally don't what > gdbus-binding-tool and python-argparse are needed for and if they can > be avoided. I guess Srini can > shade some light on this. > According to Srinivasa, we are fine sine gdbus-binding-tools are used only in build time Peter > Kr, > Chris. > > On Thu, Jun 9, 2011 at 12:02 AM, Patrick Ohly <[email protected]> wrote: > > On Mi, 2011-06-08 at 20:49 +0100, Zhu, Peter J wrote: > >> > On Mi, 2011-06-08 at 11:19 +0200, Patrick Ohly wrote: > >> > > EDS Contacts > >> > > ============ > >> > [...] > >> > > * AR Chris Dumez: EDS needs to be updated, in Trunk and 1.2. > We > >> > > decided to package the latest source from the gnome-2-32 > >> > > maintenance branch instead of carrying distro packages > which > >> > > were already reviewed and accepted upstream. > >> > > >> > This updated EDS package also contains Srini's new Camel daemon code, > >> > needed for the migration of mail to EDS. I'll let Srini say more about > >> > this. > >> > > >> > Because the Camel code depends on some additional build tools, we also > >> > need to get the following added: > >> > * AR Chris: gdbus-binding-tool libffi python-argparse > >> > > >> All these three are only needed in build time, right? > > > > Srini, can you confirm that? > > > > -- > > Best Regards > > > > Patrick Ohly > > Senior Software Engineer > > > > Intel GmbH > > Open Source Technology Center > > Pützstr. 5 Phone: +49-228-2493652 > > 53129 Bonn > > Germany > > > > > > > > -- > Dr. Christophe Dumez > Linux Software Engineer > Intel Finland Oy - Open Source Technology Center _______________________________________________ MeeGo-packaging mailing list [email protected] http://lists.meego.com/listinfo/meego-packaging
