[meego-packaging] package changes for EDS + SyncEvolution in MeeGo
Zhu, Peter J
peter.j.zhu at intel.com
Fri Jun 10 08:46:27 PDT 2011
> -----Original Message-----
> From: Ohly, Patrick
> Sent: Friday, June 10, 2011 4:01 AM
> To: Zhu, Peter J
> Cc: Dumez, Christophe; Srinivasa Ragavan; meego-packaging at meego.com
> Subject: RE: [meego-packaging] package changes for EDS + SyncEvolution in
> On Do, 2011-06-09 at 19:03 +0100, Zhu, Peter J wrote:
> > 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?
> I had already requested a devel project for EDS
> (https://bugs.meego.com/show_bug.cgi?id=17355) and Anas created the
> "eds" project for us in response. The intention was to use that for
> anything related to the EDS migration and potentially future
> maintenance/testing of related packages.
> It got a bit confusing during my vacation when we were asked to also put
> these packages into devel:meego-ux. I'm not sure whether we really want
> them there.
> Regarding SyncEvolution, it is now maintained in "eds".
> Does this answer your question? I'm not entirely sure what you were
> proposing and whether it differs from what we are doing already ;-}
Yes, absolutely. I noticed them all from eds. I just want to setup metadata so once branch 1.2 T:T then they would branch from eds.
More information about the MeeGo-packaging