Hi architects, 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[1] and realized that it's a horrible mess of groups these days, not at all corresponding to our Domain views as defined in https://meego.com/developers/meego-architecture/meego-architecture-domain-view.
So, my question is if there's interest in: * To have the MeeGo stack grouping into these domains (excluding reference UX) * 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 sending SR's? 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. BR Carsten Munk [1] http://wiki.meego.com/AgileBrowser , https://gitorious.org/meego-architecture/meego-deps-gen - fantastic tool by the way. 2010/12/21 <[email protected]>: > Hi, > > Some time ago it was discussed the RPM .spec file Group: > tag is used to identify into which subsystem [1] 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 [2]. > > [1] > http://meego.com/developers/meego-architecture/meego-architecture-domain-view > [2] > http://wiki.meego.com/Packaging/Guidelines#Domain.2FSubsystem_based_RPM_Groups > > -- > Regards, Mikko > > > _______________________________________________ > MeeGo-packaging mailing list > [email protected] > http://lists.meego.com/listinfo/meego-packaging > > _______________________________________________ MeeGo-architecture mailing list [email protected] http://lists.meego.com/listinfo/meego-architecture
