2010/9/10 <[email protected]>: > Hi all, > > > > I’ve now spent some more time creating content to the MeeGo Porting Guide > (http://wiki.meego.com/MeeGo_Porting_Guide). All that it now needs is > readers :-). Please take a look and give your comments/suggestions etc. on > the associated discussion page. The content should be least roughly accurate > but mistakes are always possible. If you find such, please let me know. >
Some discussion (CC'ing Alexander and Anas) We are referring to OBS links to MeeGo OBS [1] [2] but these were at least initially frowned upon due to 1) needing a build.meego.com OBS login (I believe), I believe but most importantly 2) there was a bug in OBS that caused slowdowns on both sides Community OBS imports weekly through a rsync from kernel.org mirror. The question is, how do we want vendors to be using MeeGo in their daily work? There's two typical uses of a vendor OBS: 1) Compiling your own product bits on top of MeeGo releases. 2) A way for your employees to work on MeeGo bits, submitting patches without needing a build.meego.com login A OBS link would be a direct link to the development state of MeeGo, let's say, I would be able to linkpac against any given state of Trunk, Trunk:Testing and submit patches fairly directly. With a weekly sync this is slightly more difficult and I'm not sure if you can linkpac against rpm import? So, what's the future plans for OBS links to meego.com OBS? Best regards, Carsten Munk [1] http://wiki.meego.com/Release_Engineering/Process#Making_a_product_out_of_MeeGo_Release [2] http://wiki.meego.com/MeeGo_Porting_Guide#Vendor.27s_own_OBS _______________________________________________ MeeGo-dev mailing list [email protected] http://lists.meego.com/listinfo/meego-dev
