[Meego-architecture] [meego-packaging] Label Core OS packages with proper Group tag
elena.reshetova at intel.com
Mon Jul 11 01:31:56 PDT 2011
A question related to this:
Who is maintaining the overall architecture model? I want to make sure our
changes in security domain are visible outside of the team, too.
From: meego-architecture-bounces at lists.meego.com
[mailto:meego-architecture-bounces at lists.meego.com] On Behalf Of Carsten
Sent: Friday, June 24, 2011 9:17 AM
To: meego-architecture at lists.meego.com
Subject: Re: [Meego-architecture] [meego-packaging] Label Core OS packages
with proper Group tag
While this is an ancient e-mail, I was browsing the MeeGo 1.3 dependancy
tree for a random tablet ia32 image the other day using Agile Browser and
realized that it's a horrible mess of groups these days, not at all
corresponding to our Domain views as defined in
So, my question is if there's interest in:
* To have the MeeGo stack grouping into these domains (excluding reference
* Have patches/SR's towards MeeGo 1.3 packages changing Group: tags for them
to match domain view, as it looks like the voluntary call didn't work
If so, two questions:
* Is it your opinion that a domain covers all packages a source package
generates, or is it per .rpm?
* Would you like a overview of intended package changes before I start
I think this should make the MeeGo architecture easier to work with and
browse, for many, including architects. If OK'ed, I plan to start the work
in 1 1/2 weeks.
 http://wiki.meego.com/AgileBrowser ,
https://gitorious.org/meego-architecture/meego-deps-gen - fantastic tool by
2010/12/21 <Mikko.K.Ylinen at nokia.com>:
> Some time ago it was discussed the RPM .spec file Group:
> tag is used to identify into which subsystem  the package belongs.
> This is an action request to all package maintainers to check your
> .spec file and label your Core OS packages.
> Attached (I hope a .csv file gets through) is a proposal about
> packages vs. subsystem mapping. Check your packages from that list.
> Guidelines how to label them are given in .
> in-view 
> Regards, Mikko
> MeeGo-packaging mailing list
> MeeGo-packaging at meego.com
MeeGo-architecture mailing list
MeeGo-architecture at lists.meego.com
-------------- next part --------------
A non-text attachment was scrubbed...
Size: 7220 bytes
Desc: not available
More information about the MeeGo-architecture