On Thu, 2013-10-03 at 14:06 +0200, Karol Lewandowski wrote: > On 10/03/2013 01:05 PM, Artem Bityutskiy wrote: > > On Thu, 2013-10-03 at 12:54 +0200, Karol Lewandowski wrote: > >> On 09/26/2013 02:32 PM, Jian-feng Ding wrote: > >>> Hi, Ravi > >>> > >>> As I know, currently build.tizen.org will only support read-only access > >>> for > >>> most of the developers. For build verifications, please use the tool gbs > >>> to do > >>> it in local machines. > >> > >> gbs done locally will allow one to test if package builds properly > >> or not. This won't be enough for proper integration testing, though. > >> > >> Say I would like to to test if new version of some core component > >> (be it libudev) doesn't break the whole system. This is where > >> OBS project would come handy. > > > > Or you say that you need to make sure the dependencies are rebuilt? > > Yes, that's the point. We had exactly this problem before - libudev > SONAME was bumped from 0 to 1 - and this does require complete rebuild, > unfortunately.
OK, let's see what the tools team answers, I am also interested to hear how this class of problems can be solved. I guess few people would need OBS access, and few people would actually want to deal with OBS directly. So at very least some people could get a playground OBS project for things like this. Or may be the tools team will offer a way to solve the problem without direct OBS access... Let's see. -- Best Regards, Artem Bityutskiy _______________________________________________ General mailing list [email protected] https://lists.tizen.org/listinfo/general
