MeeGo wiki - User contributions [en]

OBS source services

2012-07-27T14:33:25Z

Vrubiolo: /* set_version - Update package version in .spec and .dsc files */

OBS provides '''source services''' which can download/compress/extract/verify files before actually building a package. There is only small documentation [http://doc.opensuse.org/products/draft/OBS/obs-reference-guide_draft/cha.obs.source_service.html here]. You can find two interesting blog posts [http://informatiq.org/content/obs-source-service-git-master-build here] and [http://saigkill.homelinux.net/entry/2011/07/15/how-to-use-three-open-build-service-source-services-to-simplify-the-packaging there].

To use source services in your project, simply create a file with name '''<tt>_service</tt>''', and insert service definitions in it surrounded by a global '''<code><services>...</services></code>''' tag.

Notice that all sources services are not installed on all OBS servers (''pub.meego.com'' OBS seems to have only 2 while ''opensuse.org'' OBS has 14 services).

= Available services =
== ''tar_scm'' - Create an archive from your source code repository ==
A service called '''tar_scm''' is available to create a ''.tar'' archive from Subversion, Git, Mercurial and Bazaar source code management systems.
Here is a configuration example:
<code>
<service name="tar_scm">
<param name="scm">git</param>
<param name="url">git://gitorious.org/meego-developer-tools/obs-light.git</param>
<param name="subdir">src</param>
<param name="filename">obslight</param>
<param name="versionprefix">0.4.git</param>
</service>
</code>
Tag significations:
* '''scm''' (''required''): the type of source code management system you want to get source from. Available values are ''svn, git, hg, bzr''.
* '''url''' (''required''): the checkout URL of your repository.
* '''subdir''' (''optional''): the name of the sub-directory of your repository you want to checkout.
* '''filename''' (''optional''): the name of the tar file which will be created. If not specified, the last part of the URL will be used (without ''.git'' for Git repositories).
* '''versionprefix''' (''optional''): the base version string that will be appended to the file name.
* '''version''' (''optional''): the version string that will be appended to the file name. If not specified, the timestamp of the last commit is used (number of seconds since the epoch) for Git or the revision number for Subversion.
* '''exclude''' (''optional''): name of a file to exclude when creating the archive. Can be used multiple times.
* '''revision''' (''optional''): the revision number (Subversion, Mercurial, Bazaar), the commit hash, tag or branch (Git) to checkout.

== ''extract_file'' - Extract files from an archive ==
After having created an archive with the '''tar_scm''' service, you may want to extract some files, for example the spec file of your package. The '''extract_file''' service is what you need.
Here is an example:
<code>
<service name="extract_file">
<param name="archive">*.tar</param>
<param name="files">*/deb/* */rpm/obslight.changes */rpm/obslight.spec */rpm/obslight.yaml</param>
</service>
</code>
Tag meaning:
* '''archive''' (''required''): name of the archive to extract files from. Bash regular expressions authorized.
* '''files''' (''required''): name(s) of file(s) to be extracted.
* '''outfilename''' (''optional''): name the extracted file will be renamed to. To be used only if you extract a single file.

Notice that there is a top directory with a name that you don't know, so file names should start with "*/"

== ''recompress'' - Change archive compression ==
The '''recompress''' service allows you to compress or recompress an archive. Two reasons to use it: save space, and make an archive compatible with your spec file (which probably expects ''.tar.gz'' or ''.tar.bz2''). Here is an example:
<code>
<service name="recompress">
<param name="compression">gz</param>
<param name="file">*git*.tar</param>
</service>
</code>
Tag significations:
* '''compression''' (''required''): the compression format to be used. Allowed values are ''none, gz, bz2, xz''.
* '''file''' (''required''): the name of the file to be recompressed. Bash regular expressions authorized.

== ''set_version'' - Update package version in ''.spec'' and ''.dsc'' files ==
You have just configured the '''tar_scm''' service, but the archive name is different from the one in your spec file, because the version part of the name has been incremented.
The '''set_version''' service allows you to update your ''.spec'' and ''.dsc'' files with the new version of your archive.
Here is a simple example:
<code>
<service name="set_version"/>
</code>
The version will be automatically guessed from ''*.tar.*'', ''*.tgz'', ''*.tbz2'' or ''*.zip'' files. Note, however that the associated script is picky on what version fields it accepts. In particular, the version string must begin with a numeric value as can be seen in the [https://build.opensuse.org/package/view_file?file=set_version&package=obs-service-set_version&project=openSUSE%3ATools&rev=c5cb320228dfabee71e6a4df48798830 script source itself]. Failure to comply with this scheme will lead to an 'ERROR: no version is given and can't get detected automatically' error.

Provided your spec 'Source' tag contains the %{version} string, it will pick up the updated string as well. Also note that although the OBS server web UI presents the generated tarball with a leading prefix corresponding to the source services applied, the actual archive on which the spec works has its name unchanged.

However there are optional parameters (syntax <code>''<param name="'''parameter_name'''">'''value'''</param>''</code>):
* '''version''': specify the version, if you do not want auto-detection.
* '''basename''': the prefix of files to use for version auto-detection.
* '''file''': the name of the file to update. If not specified, all ''*.spec'' and ''*.dsc'' files will be updated.

== many others ==
''To be continued...''

= Complete example =
<code>
<services>

<service name="tar_scm">
<param name="scm">git</param>
<param name="subdir">src</param>
<param name="url">git://gitorious.org/meego-developer-tools/obs-light.git</param>
<param name="versionprefix">0.4.git</param>
<param name="filename">obslight</param>
</service>

<service name="extract_file">
<param name="archive">*.tar</param>
<param name="files">*/deb/* */rpm/obslight.changes */rpm/obslight.spec */rpm/obslight.yaml</param>
</service>

<service name="recompress">
<param name="file">*git*.tar</param>
<param name="compression">gz</param>
</service>

<service name="set_version"/>
</services>
</code>

OBS source services

2012-07-27T13:47:53Z

Vrubiolo: /* extract_file - Extract files from an archive */

OBS provides '''source services''' which can download/compress/extract/verify files before actually building a package. There is only small documentation [http://doc.opensuse.org/products/draft/OBS/obs-reference-guide_draft/cha.obs.source_service.html here]. You can find two interesting blog posts [http://informatiq.org/content/obs-source-service-git-master-build here] and [http://saigkill.homelinux.net/entry/2011/07/15/how-to-use-three-open-build-service-source-services-to-simplify-the-packaging there].

To use source services in your project, simply create a file with name '''<tt>_service</tt>''', and insert service definitions in it surrounded by a global '''<code><services>...</services></code>''' tag.

Notice that all sources services are not installed on all OBS servers (''pub.meego.com'' OBS seems to have only 2 while ''opensuse.org'' OBS has 14 services).

= Available services =
== ''tar_scm'' - Create an archive from your source code repository ==
A service called '''tar_scm''' is available to create a ''.tar'' archive from Subversion, Git, Mercurial and Bazaar source code management systems.
Here is a configuration example:
<code>
<service name="tar_scm">
<param name="scm">git</param>
<param name="url">git://gitorious.org/meego-developer-tools/obs-light.git</param>
<param name="subdir">src</param>
<param name="filename">obslight</param>
<param name="versionprefix">0.4.git</param>
</service>
</code>
Tag significations:
* '''scm''' (''required''): the type of source code management system you want to get source from. Available values are ''svn, git, hg, bzr''.
* '''url''' (''required''): the checkout URL of your repository.
* '''subdir''' (''optional''): the name of the sub-directory of your repository you want to checkout.
* '''filename''' (''optional''): the name of the tar file which will be created. If not specified, the last part of the URL will be used (without ''.git'' for Git repositories).
* '''versionprefix''' (''optional''): the base version string that will be appended to the file name.
* '''version''' (''optional''): the version string that will be appended to the file name. If not specified, the timestamp of the last commit is used (number of seconds since the epoch) for Git or the revision number for Subversion.
* '''exclude''' (''optional''): name of a file to exclude when creating the archive. Can be used multiple times.
* '''revision''' (''optional''): the revision number (Subversion, Mercurial, Bazaar), the commit hash, tag or branch (Git) to checkout.

== ''extract_file'' - Extract files from an archive ==
After having created an archive with the '''tar_scm''' service, you may want to extract some files, for example the spec file of your package. The '''extract_file''' service is what you need.
Here is an example:
<code>
<service name="extract_file">
<param name="archive">*.tar</param>
<param name="files">*/deb/* */rpm/obslight.changes */rpm/obslight.spec */rpm/obslight.yaml</param>
</service>
</code>
Tag meaning:
* '''archive''' (''required''): name of the archive to extract files from. Bash regular expressions authorized.
* '''files''' (''required''): name(s) of file(s) to be extracted.
* '''outfilename''' (''optional''): name the extracted file will be renamed to. To be used only if you extract a single file.

Notice that there is a top directory with a name that you don't know, so file names should start with "*/"

== ''recompress'' - Change archive compression ==
The '''recompress''' service allows you to compress or recompress an archive. Two reasons to use it: save space, and make an archive compatible with your spec file (which probably expects ''.tar.gz'' or ''.tar.bz2''). Here is an example:
<code>
<service name="recompress">
<param name="compression">gz</param>
<param name="file">*git*.tar</param>
</service>
</code>
Tag significations:
* '''compression''' (''required''): the compression format to be used. Allowed values are ''none, gz, bz2, xz''.
* '''file''' (''required''): the name of the file to be recompressed. Bash regular expressions authorized.

== ''set_version'' - Update package version in ''.spec'' and ''.dsc'' files ==
You have just configured the '''tar_scm''' service, but the archive name is different from the one in your spec file, because the version part of the name has been incremented.
The '''set_version''' service allows you to update your ''.spec'' and ''.dsc'' files with the new version of your archive.
Here is a simple example:
<code>
<service name="set_version"/>
</code>
The version will be automatically guessed from ''*.tar.*'', ''*.tgz'', ''*.tbz2'' or ''*.zip'' files. Note, however that the associated script is picky on what version fields it accepts. In particular, the version string must begin with a numeric value as can be seen in the [https://build.opensuse.org/package/view_file?file=set_version&package=obs-service-set_version&project=openSUSE%3ATools&rev=c5cb320228dfabee71e6a4df48798830 script source itself]. Failure to comply with this scheme will lead to an 'ERROR: no version is given and can't get detected automatically' error.

Provided your spec 'Source' tag contains the %{version} string, it will pick up the updated string as well.

However there are optional parameters (syntax <code>''<param name="'''parameter_name'''">'''value'''</param>''</code>):
* '''version''': specify the version, if you do not want auto-detection.
* '''basename''': the prefix of files to use for version auto-detection.
* '''file''': the name of the file to update. If not specified, all ''*.spec'' and ''*.dsc'' files will be updated.

== many others ==
''To be continued...''

= Complete example =
<code>
<services>

<service name="tar_scm">
<param name="scm">git</param>
<param name="subdir">src</param>
<param name="url">git://gitorious.org/meego-developer-tools/obs-light.git</param>
<param name="versionprefix">0.4.git</param>
<param name="filename">obslight</param>
</service>

<service name="extract_file">
<param name="archive">*.tar</param>
<param name="files">*/deb/* */rpm/obslight.changes */rpm/obslight.spec */rpm/obslight.yaml</param>
</service>

<service name="recompress">
<param name="file">*git*.tar</param>
<param name="compression">gz</param>
</service>

<service name="set_version"/>
</services>
</code>

OBS source services

2012-07-26T13:13:17Z

Vrubiolo: /* set_version - Update package version in .spec and .dsc files */

OBS provides '''source services''' which can download/compress/extract/verify files before actually building a package. There is only small documentation [http://doc.opensuse.org/products/draft/OBS/obs-reference-guide_draft/cha.obs.source_service.html here]. You can find two interesting blog posts [http://informatiq.org/content/obs-source-service-git-master-build here] and [http://saigkill.homelinux.net/entry/2011/07/15/how-to-use-three-open-build-service-source-services-to-simplify-the-packaging there].

To use source services in your project, simply create a file with name '''<tt>_service</tt>''', and insert service definitions in it surrounded by a global '''<code><services>...</services></code>''' tag.

Notice that all sources services are not installed on all OBS servers (''pub.meego.com'' OBS seems to have only 2 while ''opensuse.org'' OBS has 14 services).

= Available services =
== ''tar_scm'' - Create an archive from your source code repository ==
A service called '''tar_scm''' is available to create a ''.tar'' archive from Subversion, Git, Mercurial and Bazaar source code management systems.
Here is a configuration example:
<code>
<service name="tar_scm">
<param name="scm">git</param>
<param name="url">git://gitorious.org/meego-developer-tools/obs-light.git</param>
<param name="subdir">src</param>
<param name="filename">obslight</param>
<param name="versionprefix">0.4.git</param>
</service>
</code>
Tag significations:
* '''scm''' (''required''): the type of source code management system you want to get source from. Available values are ''svn, git, hg, bzr''.
* '''url''' (''required''): the checkout URL of your repository.
* '''subdir''' (''optional''): the name of the sub-directory of your repository you want to checkout.
* '''filename''' (''optional''): the name of the tar file which will be created. If not specified, the last part of the URL will be used (without ''.git'' for Git repositories).
* '''versionprefix''' (''optional''): the base version string that will be appended to the file name.
* '''version''' (''optional''): the version string that will be appended to the file name. If not specified, the timestamp of the last commit is used (number of seconds since the epoch) for Git or the revision number for Subversion.
* '''exclude''' (''optional''): name of a file to exclude when creating the archive. Can be used multiple times.
* '''revision''' (''optional''): the revision number (Subversion, Mercurial, Bazaar), the commit hash, tag or branch (Git) to checkout.

== ''extract_file'' - Extract files from an archive ==
After having created an archive with the '''tar_scm''' service, you may want to extract some files, for example the spec file of your package. The '''extract_file''' service is what you need.
Here is an example:
<code>
<service name="extract_file">
<param name="archive">*.tar</param>
<param name="files">*/deb/* */rpm/obslight.changes */rpm/obslight.spec */rpm/obslight.yaml</param>
</service>
</code>
Tag significations:
* '''archive''' (''required''): name of the archive to extract files from. Bash regular expressions authorized.
* '''files''' (''required''): name(s) of file(s) to be extracted.
* '''outfilename''' (''optional''): name the extracted file will be renamed to. To be used only if you extract a single file.

== ''recompress'' - Change archive compression ==
The '''recompress''' service allows you to compress or recompress an archive. Two reasons to use it: save space, and make an archive compatible with your spec file (which probably expects ''.tar.gz'' or ''.tar.bz2''). Here is an example:
<code>
<service name="recompress">
<param name="compression">gz</param>
<param name="file">*git*.tar</param>
</service>
</code>
Tag significations:
* '''compression''' (''required''): the compression format to be used. Allowed values are ''none, gz, bz2, xz''.
* '''file''' (''required''): the name of the file to be recompressed. Bash regular expressions authorized.

== ''set_version'' - Update package version in ''.spec'' and ''.dsc'' files ==
You have just configured the '''tar_scm''' service, but the archive name is different from the one in your spec file, because the version part of the name has been incremented.
The '''set_version''' service allows you to update your ''.spec'' and ''.dsc'' files with the new version of your archive.
Here is a simple example:
<code>
<service name="set_version"/>
</code>
The version will be automatically guessed from ''*.tar.*'', ''*.tgz'', ''*.tbz2'' or ''*.zip'' files. Note, however that the associated script is picky on what version fields it accepts. In particular, the version string must begin with a numeric value as can be seen in the [https://build.opensuse.org/package/view_file?file=set_version&package=obs-service-set_version&project=openSUSE%3ATools&rev=c5cb320228dfabee71e6a4df48798830 script source itself]. Failure to comply with this scheme will lead to an 'ERROR: no version is given and can't get detected automatically' error.

Provided your spec 'Source' tag contains the %{version} string, it will pick up the updated string as well.

However there are optional parameters (syntax <code>''<param name="'''parameter_name'''">'''value'''</param>''</code>):
* '''version''': specify the version, if you do not want auto-detection.
* '''basename''': the prefix of files to use for version auto-detection.
* '''file''': the name of the file to update. If not specified, all ''*.spec'' and ''*.dsc'' files will be updated.

== many others ==
''To be continued...''

= Complete example =
<code>
<services>

<service name="tar_scm">
<param name="scm">git</param>
<param name="subdir">src</param>
<param name="url">git://gitorious.org/meego-developer-tools/obs-light.git</param>
<param name="versionprefix">0.4.git</param>
<param name="filename">obslight</param>
</service>

<service name="extract_file">
<param name="archive">*.tar</param>
<param name="files">*/deb/* */rpm/obslight.changes */rpm/obslight.spec */rpm/obslight.yaml</param>
</service>

<service name="recompress">
<param name="file">*git*.tar</param>
<param name="compression">gz</param>
</service>

<service name="set_version"/>
</services>
</code>

OBS source services

2012-07-26T10:02:37Z

Vrubiolo: /* set_version - Update package version in .spec and .dsc files */

OBS provides '''source services''' which can download/compress/extract/verify files before actually building a package. There is only small documentation [http://doc.opensuse.org/products/draft/OBS/obs-reference-guide_draft/cha.obs.source_service.html here]. You can find two interesting blog posts [http://informatiq.org/content/obs-source-service-git-master-build here] and [http://saigkill.homelinux.net/entry/2011/07/15/how-to-use-three-open-build-service-source-services-to-simplify-the-packaging there].

To use source services in your project, simply create a file with name '''<tt>_service</tt>''', and insert service definitions in it surrounded by a global '''<code><services>...</services></code>''' tag.

Notice that all sources services are not installed on all OBS servers (''pub.meego.com'' OBS seems to have only 2 while ''opensuse.org'' OBS has 14 services).

= Available services =
== ''tar_scm'' - Create an archive from your source code repository ==
A service called '''tar_scm''' is available to create a ''.tar'' archive from Subversion, Git, Mercurial and Bazaar source code management systems.
Here is a configuration example:
<code>
<service name="tar_scm">
<param name="scm">git</param>
<param name="url">git://gitorious.org/meego-developer-tools/obs-light.git</param>
<param name="subdir">src</param>
<param name="filename">obslight</param>
<param name="versionprefix">0.4.git</param>
</service>
</code>
Tag significations:
* '''scm''' (''required''): the type of source code management system you want to get source from. Available values are ''svn, git, hg, bzr''.
* '''url''' (''required''): the checkout URL of your repository.
* '''subdir''' (''optional''): the name of the sub-directory of your repository you want to checkout.
* '''filename''' (''optional''): the name of the tar file which will be created. If not specified, the last part of the URL will be used (without ''.git'' for Git repositories).
* '''versionprefix''' (''optional''): the base version string that will be appended to the file name.
* '''version''' (''optional''): the version string that will be appended to the file name. If not specified, the timestamp of the last commit is used (number of seconds since the epoch) for Git or the revision number for Subversion.
* '''exclude''' (''optional''): name of a file to exclude when creating the archive. Can be used multiple times.
* '''revision''' (''optional''): the revision number (Subversion, Mercurial, Bazaar), the commit hash, tag or branch (Git) to checkout.

== ''extract_file'' - Extract files from an archive ==
After having created an archive with the '''tar_scm''' service, you may want to extract some files, for example the spec file of your package. The '''extract_file''' service is what you need.
Here is an example:
<code>
<service name="extract_file">
<param name="archive">*.tar</param>
<param name="files">*/deb/* */rpm/obslight.changes */rpm/obslight.spec */rpm/obslight.yaml</param>
</service>
</code>
Tag significations:
* '''archive''' (''required''): name of the archive to extract files from. Bash regular expressions authorized.
* '''files''' (''required''): name(s) of file(s) to be extracted.
* '''outfilename''' (''optional''): name the extracted file will be renamed to. To be used only if you extract a single file.

== ''recompress'' - Change archive compression ==
The '''recompress''' service allows you to compress or recompress an archive. Two reasons to use it: save space, and make an archive compatible with your spec file (which probably expects ''.tar.gz'' or ''.tar.bz2''). Here is an example:
<code>
<service name="recompress">
<param name="compression">gz</param>
<param name="file">*git*.tar</param>
</service>
</code>
Tag significations:
* '''compression''' (''required''): the compression format to be used. Allowed values are ''none, gz, bz2, xz''.
* '''file''' (''required''): the name of the file to be recompressed. Bash regular expressions authorized.

== ''set_version'' - Update package version in ''.spec'' and ''.dsc'' files ==
You have just configured the '''tar_scm''' service, but the archive name is different from the one in your spec file, because the version part of the name has been incremented.
The '''set_version''' service allows you to update your ''.spec'' and ''.dsc'' files with the new version of your archive.
Here is a simple example:
<code>
<service name="set_version"/>
</code>
The version will be automatically guessed from ''*.tar.*'', ''*.tgz'', ''*.tbz2'' or ''*.zip'' files. Note, however that the associated script is picky on what version fields it accepts. In particular, the version string must begin with a numeric value as can be seen in the [https://build.opensuse.org/package/view_file?file=set_version&package=obs-service-set_version&project=openSUSE%3ATools&rev=c5cb320228dfabee71e6a4df48798830 script source itself]. Failure to comply with this scheme will lead to an 'ERROR: no version is given and can't get detected automatically' error.

However there are optional parameters (syntax <code>''<param name="'''parameter_name'''">'''value'''</param>''</code>):
* '''version''': specify the version, if you do not want auto-detection.
* '''basename''': the prefix of files to use for version auto-detection.
* '''file''': the name of the file to update. If not specified, all ''*.spec'' and ''*.dsc'' files will be updated.

== many others ==
''To be continued...''

= Complete example =
<code>
<services>

<service name="tar_scm">
<param name="scm">git</param>
<param name="subdir">src</param>
<param name="url">git://gitorious.org/meego-developer-tools/obs-light.git</param>
<param name="versionprefix">0.4.git</param>
<param name="filename">obslight</param>
</service>

<service name="extract_file">
<param name="archive">*.tar</param>
<param name="files">*/deb/* */rpm/obslight.changes */rpm/obslight.spec */rpm/obslight.yaml</param>
</service>

<service name="recompress">
<param name="file">*git*.tar</param>
<param name="compression">gz</param>
</service>

<service name="set_version"/>
</services>
</code>

OBS Light

2012-02-23T18:04:03Z

Vrubiolo:

If you have (or are thinking about) selecting MeeGo but you cannot put all the code you want to build on OBS, the public, cloud-based MeeGo building tool, or if you are more comfortable with the tradition of local build tools based on a chroot than with a full cloud-based system like OBS, you might find the learning curve a bit steep.

While OBS will provide you with a very powerful and adapted tool for your long-term needs, the entry cost can be perceived to be too high.
This issue is particularly strongly perceived in the TV or IVI segments where recompilation of the Linux kernel and adding drivers is required even during the very early phases of a project and compiling in the public domain is out of the question.

* Videos [http://www.dailymotion.com/playlist/x1t5ll_dominigarfoll_obs-light-training Starting with OBS Light]
* Current progress an deliveries can be found in [[ObsLightDeliverable]] page.
* [[OBS_Light_Manual | OBS Light manual]]
* [[OBS_Light_FAQ | Frequently Asked Questions]]
* You can file bugs on [https://bugs.meego.com/buglist.cgi?product=Development%20Tools&component=OBS%20Light MeeGo's bugzilla]. The bug list for the project can be reached [https://bugs.meego.com/buglist.cgi?product=Development%20Tools&component=OBS%20Light here]. To easily file a new bug, use [https://bugs.meego.com/enter_bug.cgi?product=Development%20Tools this link]

You can find a OBS Light appliance, build in suse studio:
http://susestudio.com/a/e0uuBG/meego-obs-light

You can find a OBS appliance, build in suse studio:
http://susegallery.com/a/e0uuBG/meego-obs

The project proposed is called 'OBS Light' (or also obslight) and creates an encapsulation of OBS which presents a lighter face of OBS that we have called OBS light which could be delivered (if desired) with a pre-packaged MeeGo TV stack (or any other MeeGo vertical) released on a DVD image.

You can Download the boot strap of Meego 1.2.0 here (saveOBS.tar.aa -> saveOBS.tar.ba).
http://www.cc-e.co.uk/Meego/MeeGo-1.2.0/
reassembled the file
cat saveOBS.tar.?? >> saveOBS.tar.gz
Thanks to Julien Snell and Cocom for the ftp server.
http://www.cc-e.co.uk

Note that under the hood, OBS light still is 100% OBS code and the building process is the same as what you could achieve by running your own private OBS.
OBS Light mainly pre-configures an OBS with a few osc plugins to ease the learning curve. Note that some OBS feature are hidden to simplify the learning phase. As the service is run locally, you can mix Open Source and private code should you need to do so.

OBS light provides a image builder too, called Imager.
You can find an Imager appliance, built in suse studio:
http://susegallery.com/a/e0uuBG/meego-imager
IMG (Image Me Give) is a project initiated by Nokia. It is a small python
client/server application suite which manages the supervision of the MIC2 image
creation following the submission of a ks file by the user.
http://wiki.meego.com/Release_Infrastructure/IMG_Installation_for_OpenSuse_11.4#Start_IMG

In a second phase we hope to add a simple UI to it. It reuses the osc command line tools delivered with OBS to which a set of extra plugins have been added, including an extension of mic2. All this remains compatible with a full implementation of OBS. It will be published under License: GPLv2.

The osc plugin for automatic patch creation are designed to be reusable in a full OBS environment.

The coding is under work and changes are likely to occur during the development process.

{|
| || '''OBS Light''' || '''Full OBS'''
|-
| Cross compilation || Yes || Yes
|-
| Local and remote reference || Yes || Yes
|-
| Automatic creation of patch || Yes || Not Yet (will if the same osc plugin is loaded)
|-
| Bootable Image creation || Yes || Add on
|-
| Integrated version control || Hidden || Yes
|-
| Multi-user || Hidden || Yes
|-
| Multi-target by project || Hidden || Yes
|-
| Auto built || Hidden || Yes
|-
| Signing service || Hidden || Yes
|}

GIT: https://meego.gitorious.org/meego-developer-tools/obs-light

OBS: https://build.pub.meego.com/project/show?project=Project%3AOBS_Light

Initial Specifications (final implementation are likely differ from the initial concept) :[[https://meego.gitorious.org/meego-developer-tools/obs-light/blobs/master/Doc/SpecOBSLight-1_V-0-6.pdf SpecOBSLight-1_V-0-6]]

All discussions are run on the MeeGo-distribution-tools mailing list.
http://lists.meego.com/listinfo/meego-distribution-tools