Build Service/Concepts/AppDirectory

From openSUSE

Revision as of 12:50, 20 July 2009

Application Directory Integration Interface

To attract projects to build in the Build Service we implement an interface that returns pathes to binary packages according to one project name and a list of package names.

The usecase is to invite application directory systems such as http://kde-apps.org to offer their user (in this case, the users are the people who maintain the directory entries upstream) the following service: If they build binary packages in the OBS, the directory app takes an OBS project- and package name. On the fly, the directory app uses the integration interface of the OBS with these two parameters and gets a list of the available binary packages for the package, see example structure below. The directory app can render a nice download box for the users to pick rpms from the OBS for their system.

To make it really convenient for the directory application, additionally there is detailed info about the available distros. It contains some descriptions, names and images the directory application may make use of. It goes completely independent of the package information to be reuseable.

Example communication:

GET /distributions

returns an XML document like

 <distributions>
   <distribution id="opensuse-11.0">
     <name>openSUSE 11.0</name>
     <icon width="16" height="16">"/>
     <link>http://www.opensuse.org</link>
   </distribution>
   <distribution id="fedora-9">
     <name>Fedora 9</name>
     <icon width="16" height="16">"/>
     <link>http://www.fedoraproject.org</link>
   </distribution>
 </distributions>