I tried this and got the errors:  http://pastebin.com/WQr7eu14


On 12/07/2010 05:01 PM, ext Zhu, Peter J wrote:
Hi

-----Original Message-----
From: [email protected]
[mailto:[email protected]] On Behalf Of Maitrey Mishra
Sent: Tuesday, December 07, 2010 8:44 PM
To: [email protected]
Subject: [meego-packaging] Vala Packages in OBS

Hi,

I am one of the maintainers in devel:contentfw.
Tracker-0.29 depends on vala-0.11.2.
I packaged vala in my home:maimishr
(http://build.meego.com/package/show?package=vala&project=home:maimis
hr)

Branch it


But I find that the .pc files and the .so names have changed in the
upstream.
To my understanding it is an ABI break.

In such a situation how do we handle it?
I checked the packaging guidelines and did not find any documentation
for such cases.
Check both build dependency and run time dependency generally . For vala, it's 
much more easy actually. At first packages dependent on vala is not 
many(several) Secondly vala is a language and not used in any vertical yet 
AFAIK.

For build dependency check, you could use localcheckbuild tool to check if the 
packages dependent on it could build with new vala. If vala pc file names 
changes, very possibly break. Then you should send changes required to the 
owners to fix them.

For runtime dependency check, for general stuff(not for vala), then we could 
upgrade existing system with new vala to see if any things break.

Peter

This is very important for us, considering the
fact that Meego1.2 freeze is a month away.

Regards,
Maitrey


_______________________________________________
MeeGo-packaging mailing list
[email protected]
http://lists.meego.com/listinfo/meego-packaging

_______________________________________________
MeeGo-packaging mailing list
[email protected]
http://lists.meego.com/listinfo/meego-packaging

Reply via email to