Hello,

this was posted on the development tool mailing list that mainly of you
likely do not follow, but that specific post should interest any one who
need/want his own OBS to mix private and public code.

Discussion will occurs in the Meego-distribution-tools mailing list

-- 
Dominig ar Foll
MeeGo TV / IVI
Open Source Technology Centre
Intel SSG




-------- Message original --------
Sujet:  [Meego-distribution-tools] An OBS appliance ready to work for meego
Date :  Thu, 29 Sep 2011 09:17:40 +0200
De :    ronan <[email protected]>
Pour :  [email protected]



Hello,

as part of the delivery of the OBS Light project which aims at 
simplifying access to OBS for people who needs to run project with mixed 
private and public repositories, we are happy to release the first 
version a OBS for MeeGO appliance.

Our prepackaged version is delivered as a OpenSUSE appliance and is 
available from Suse Studio.
You will find it here :
http://susegallery.com/a/e0uuBG/meego-obs

-You have 2 Remote OBS projects (meego.com, public.meego.com).
-you have 3 repository targets (meego:1.2.0, MeeGo:Trunk, MeeGo:1.2).
-OBS setup is already done for you.
-Architectures (i586, armv8el) are configured.
-You can use, obstag - obs2obscopy - obsextractgroups, to work with an 
other OBS.
http://wiki.meego.com/Obstag

The appliance is available under various native and ready to run virtual 
machines.
We assume that you know how to run a VM on your system.

The User manual for a private OBS appliance is hosted on the MeeGo Wiki 
here :
http://en.opensuse.org/openSUSE:Build_Service_private_instance

For more information about OBS :
http://en.opensuse.org//openSUSE:Build_Service_Appliance

Your feedback is welcome.

Ronan.

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

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

Reply via email to