Groups can be defined by maintainer of any project using

osc meta pattern <prj>


No need to get access to servers or additional scripts.

Anas

On Fri, Jul 29, 2011 at 5:18 PM, Dominig ar Foll (Intel OTC) <
[email protected]> wrote:

> Hi,
>
> one of the problem for developer, as soon as they create full branches
> of complete OS (for example a MeeGo:1.2:TV) in either a public or a
> private OBS, is the need to get a login on the supporting OBS host to
> run the createrepo tools to add packages groups definitions.
>
> In general normal developers (like me) do not have such login bit It is
> not uncommon that packages groups are included in reference kick start
> files (.ks) making difficult the reuse of .ks on alternative repo.
>
> Furthermore, the groups definitions in a given repo can change over the
> time which means that, if you want to recreate the same image at a later
> time, you might actually change your image definition whithout having
> any control on these changes.
>
> Context
> =======
> In the OBS Light team, our goal is to make our live (and may be yours by
> side effect) easier. If you cannot rely at 100% on the public
> repositories and plays with full OS image you might have similar issues.
> So we happy to share with you our new tool : obsextractgroups.
>
> obsextractgroups as it name tells, simply extract packages groups from a
> published repo and provides them as files ready for used by mic2 as an
> include file in a .ks via the macro %include.
>
> Usage
> =====
> Usage is very simple here is a printout of the integrated help.
>
> obsextractgroups --help
> HELP
> Function :  Parse the group.xml file (even if it's a .gz file), in a
> Meego's repos,
>           And save the lists of rpm for each group into files.
>
> Usage:     obsextractgroups [option] URL-to-published-repo
> [target-dir-includes-files]
>           [option]:
>           -s silent mode
>           -d debug mode, copy the group.xml in the
> target-dir-includes-files.
>           -v verbose mode.
>           URL-to-published-repo: must be a valid repository
>           target-dir-includes-files: is optional, by default the value
> is the current directory
>
> Example1:  Remote
>           ./obsextractgroups -v -d
> http://repo.meego.com/MeeGo/releases/1.2.0/repos/oss/ia32/ ./result/
> Example2:  Remote (note: here the port is 82)
>           ./obsextractgroups
> http://128.124.118.140:82/home/ronan/MeeGo/1.2/
> Example3:  Local
>           ./obsextractgroups -s ./repos/
> version 1.0   LicenseGLPv2
>
> Where to get it
> ============
> You will find our small tools in our GIT tree.
>
> https://meego.gitorious.org/meego-developer-tools/obs-light/trees/master/src/script
>
> A bit more documentation
> ====================
> Obviously on the MeeGo.com Wiki
> http://wiki.meego.com/Obstag
>
> Feedback (good as well as bad) is welcomed
>
> --
> Dominig ar Foll
> MeeGo TV
> Open Source Technology Centre
> Intel SSG
>
> _______________________________________________
> MeeGo-distribution-tools mailing list
> [email protected]
> http://lists.meego.com/listinfo/meego-distribution-tools
>
_______________________________________________
MeeGo-distribution-tools mailing list
[email protected]
http://lists.meego.com/listinfo/meego-distribution-tools

Reply via email to