JD Zheng wrote: > Hi, > > A few questions: > 1) Is this community OBS used for "community" app only? Or it can be > used for testing/patching "official" MeeGo packages?
Good question. I would expect a similar policy to the openSuse service which is "anything OSS". I have no idea if we'll have any other constraints. Common sense will, of course, play a part. > 2) If community app only and I don't have enough "MERIT" to access core > OBS, but I still want to fix bugs in "official" pkg, what is the > procedure? Does it mean I will have to install OBS locally, then > build/test and submit patch separately? And this is one reason I'd expect it to support 'anything' - and eventually I expect it will be tied to the live MeeGo trunk. > -- OBS is a VCS so that it tracks changes. This is open to interpretation. OBS has vcs-like features. How they are used is process specific. There are moves in the OBS to tie to DVCS repos. http://en.opensuse.org/Build_Service/Concepts > Unlike kernel has a MeeGo git > so that changes can be tracked and submitted through git, how patches to > other pkg, for example, glibc/Qt are managed under VCS? Originally, I > think it is OBS, but as we will have different OBS and different repo, > seems I was wrong. In general MeeGo doesn't accept patches - they should go upstream and this will often be to a git/dvcs repo and may go via a pull. However, when there are patches which you want to send to Meego then they should be sent to the mailing list. > 3) Does MeeGo already support local OBS? if it is, I'd suggest we have a > document/wiki for developers so that everyone can build using local OBS, > therefore the public OBS isn't the road-blocker since repository is > opened for a lot of pkgs. Actually when I did something with Mer, I used > local OBS most of time, simply because it is faster :-) I think you mean local build, ie "osc build" - and the answer is "no" - this is a big problem (IMHO) at the moment. It is another reason for providing a community OBS to allow a *massively* easier core code development processes: * install/setup osc/build for Debian/Suse/Ubuntu/Redhat/MeeGo/... * "osc co Trunk package && cd Trunk/package" * "osc build" * get rpm (after a few minutes) right now you have the rather old-fashioned "use the image and set your own environment up" approach. HTH David -- "Don't worry, you'll be fine; I saw it work in a cartoon once..." _______________________________________________ MeeGo-dev mailing list [email protected] http://lists.meego.com/listinfo/meego-dev
