Hi Tom, We're going through this exercise and the first version of the core package list will be available by end of this month and posted at meego.com. It wont be final until 1.1 is released but drafts of the list will be available.
Thank you, Ibrahim * * On Tue, Aug 17, 2010 at 5:22 AM, Counihan, Tom <[email protected]>wrote: > Hi Folks, > > Firstly, sincere apologies in advance - I know there has been a lot of > mails on the topic of compliance to date, I've studied these in length, but > I'm still struggling with the following question: > > How do I generate a list of packages that explicitly define what is Meego > Core Compliant for a particular release? > > I read from here the compliance program is yet to be finalized: > http://meego.com/about/compliance-program > > A package list like this: > http://repo.moblin.org/MeeGo/releases/1.0/netbook/images/meego-netbook-chromium-ia32/meego-netbook-chromium-ia32-1.0-20100524.1.packagesis > very useful in that it contains Meego Core, but how to identify what is > Meego Core vs vertical specific I'm finding a challenge. > > I'm drawn to this link: > http://repo.meego.com/MeeGo/releases/1.0/core/repos/source/ > > Do these 942 packages define Meego Core 1.0? > > Following some further investigation I find; > > http://mirrors2.kernel.org/meego/releases/1.0/core/images/meego-n900-open-armv7l/meego-n900-open-armv7l-1.0.0.20100525.1.packageswhich > is interesting because it's the first I find of a core specific > release. > Therein I find 286 packages - substantially less that my 942 list. > Interestingly, the kickstart file here defines core to be located here: > repo --name=MeeGo-1.0-Core-official --baseurl= > http://repo.meego.com/MeeGo/releases/1.0/core/repos/armv7l/packages/ > where a quick count herein yields 1894 packages. > > Finally, looking from a different angle through the kickstart files: > > http://repo.meego.com/MeeGo/releases/1.0.1/ivi/images/meego-ivi-ia32-noemgd/meego-ivi-ia32-noemgd-1.0.1-20100729.1.ks > > "repo --name=core-1.0.1 --baseurl= > http://repo.meego.com/MeeGo/releases/1.0.1/core/repos/ia32/packages"; > therein gives me the impression I might be on the right track with the > aforementioned 942 package list. However, if I look at the "%packages" > package selection, @MeeGo Core component is explicitly stated - I get the > impression this is a subset of the mentioned 942 list - does it define Core > or is the name simply throwing me? I suspect perhaps not, as I'm guessing > Meego Base and MeeGo X Window System are at a minimum also considered Meego > Core. > > Where this leaves me is I'm unsure how one can create a list of packages > that define what Meego Core is for a specific release. > > Again, sincere apologies if what I convey is a dumb-ass question - Mea > Culpa > > Warm Regards > Tom. > > > -------------------------------------------------------------- > Intel Shannon Limited > Registered in Ireland > Registered Office: Collinstown Industrial Park, Leixlip, County Kildare > Registered Number: 308263 > Business address: Dromore House, East Park, Shannon, Co. Clare > > This e-mail and any attachments may contain confidential material for the > sole use of the intended recipient(s). Any review or distribution by others > is strictly prohibited. If you are not the intended recipient, please > contact the sender and delete all copies. > > > _______________________________________________ > MeeGo-dev mailing list > [email protected] > http://lists.meego.com/listinfo/meego-dev >
_______________________________________________ MeeGo-dev mailing list [email protected] http://lists.meego.com/listinfo/meego-dev
