On 3 Feb 2011, at 18:55, Gabriel Beddingfield wrote:

> On Thu, Feb 3, 2011 at 9:50 AM, Arjan van de Ven <[email protected]> 
> wrote:
>>>> can you describe what you are trying to do so that maybe we can have
>>>> better suggestions?
>>> 
>>> On some other project derived from meego, create images without a
>>> package included in meego package groups. That functionality is provided
>>> by alternative package, and you cannot replace original with Provides:
>>> for mic.
>>> 
>> so you're not meego compliant in this derived project...
>> ... why not fix your own package group definition ?
> 
> Last I checked, createrepo support package groups, but not patterns.
> zypper supports patterns but not package groups.  The only way to
> create both is through OBS.[1]

What createrep does is just add another section in the repomd.xml, it is just 
matter of convenience. 
We add the patterns using modifyrepo.

To convert from comps to patterns, you can use this xsl file:
http://meego.gitorious.org/meego-os-base/package-groups/blobs/master/bak/patterns.xsl

But I am not sure why you want to do that, a pattern is a simple list of 
packages, so no reason to start from comps to get patterns.


> 
> Know of any non-OBS solutions to this?  Until then, I can understand
> why people would opt for a meta-package that works with both
> kickstart/mic (yum) and zypper (meego).

mic uses patterns.

Anas

> 
> Thanks,
> Gabriel
> 
> [1] I found a util. for converting groups to patterns, but I got stuck
> in all the ruby dependencies.
> _______________________________________________
> MeeGo-packaging mailing list
> [email protected]
> http://lists.meego.com/listinfo/meego-packaging

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

Reply via email to