[meego-releases] Moving package group definition to OBS

[Alexander.Kanevskiy at nokia.com]

On 20/09/2010 22:53, "Anas Nashif" <anas.nashif at intel.com> wrote:

> 
> On 2010-09-20, at 8:25 PM, <Alexander.Kanevskiy at nokia.com> wrote:
> 
>> 
>> 
>> 
>> On 20/09/2010 20:12, "Anas Nashif" <anas.nashif at intel.com> wrote:
>> 
>>> Hi,
>>> package groups (AKA rpm groups, patterns) are now maintained in a git repo
>>> in
>>> a comps file. This comps file is applied on repos after OBS has published
>>> the
>>> repositories and is not maintained in any way in OBS.
>>> At the same time, OBS supports a different type of groups which is supported
>>> by our package manager and is fully maintained in OBS per project and gets
>>> automatically applied to repo when those are published.
>>> 
>>> Latest OBS release also generates comps files (consumable by yum) from the
>>> patterns, something we can use now.
>>> 
>>> Since we are going to do some changes to the groups and need to do some
>>> renaming to align with architecture and remove some legacy stuff, we should
>>> take this opportunity to move the definition into OBS completely. This means
>>> that packages will be added to projects directly (using osc meta pattern
>>> <project> <pattern>) and the whole process will streamlined without the need
>>> for access to the repo servers etc.
>> 
>> Does OBS maintain history of changes for those patterns ? Or we will get one
>> more untraceable thing like prjconf ?
> 
> both now maintain history.

In 2.0 ? How to see it ?


-- 
Best regards, Alexander Kanevskiy.