> Are there details on the wiki for setting up an OBS/build box to compile the
> source rpms ? Previously I attempted something similar for Moblin both with
> my own scripts and based on these instructions,
> http://moblin.org/documentation/building-moblin-packages-natively.
> Unfortunately due to packaging issues, quite a few of the source rpms failed
> to successfully rebuild.
So far, seemed not (I am not sure.)
But meego community obs [ see attached email] seemed to target for this. And
you can also find some similar project in opensuse public obs server.
-----Original Message-----
From: Glen Gray [mailto:[email protected]]
Sent: Friday, June 11, 2010 5:06 PM
To: Zhang, Austin
Cc: [email protected]
Subject: Re: [MeeGo-dev] Compiling MeeGo - Other Platforms
Hi Austin,
On 11 Jun 2010, at 09:51, Zhang, Austin wrote:
>
>> Or rather I'm asking, is it still the case that ssse3 is used throughout
>> entire suite of x86 rpms, as it was in Moblin.
> IMHO, yes.
Thanks, clarification that it is used.
>> Yes, it is what I'm referring to. If other x86 platforms want to base on
>> MeeGo Core, then does it make sense for the ssse3 optimization to be applied
>> to the underlying core os and not just the UX.
> It is a little unimaginable: if anyone else platform wants to base on MeeGo
> Core, but don't compile/optimize for itself, say at least -march, -mtune
> ......
Are there details on the wiki for setting up an OBS/build box to compile the
source rpms ? Previously I attempted something similar for Moblin both with my
own scripts and based on these instructions,
http://moblin.org/documentation/building-moblin-packages-natively.
Unfortunately due to packaging issues, quite a few of the source rpms failed to
successfully rebuild.
--
Glen Gray
<[email protected]>
--- Begin Message ---
Hi all,
We had a small meeting about the MeeGo community applications pipeline Thursday
29.4 evening UTC.
First off, sorry for having the meeting unadvertised. However to get the
community repository team moving, I saw it necessary to get a small bunch of
people in an IRC room and make sure we all have the same goal. The discussions
that have been going back and forth in this mailing list definitely seemed to
point to that, but I like to be sure. Now it is safe to say that the perception
was correct. The team has a common target of creating the system where a
community developer can share their open application with MeeGo device end
users through a community repository.
People present in no sensible order:
- David Greaves
- Niels Breet
- Carsten Munk
- Brian Harring
- Bob Spencer
- Ramez Hanna
- Anas Nashif
- Mike Shaver
- Tero Kojo
So to summarise the outcome of yesterday:
- There will be a Community Applications Team (name open to sensible
discussion, I just picked that from a mail by Bob previously here)
- I promised to take the lead on the Team
- The team will create the pipeline that enables the community to create and
provide open applications to MeeGo
- The pipeline will consist of: a community build system (OBS), a community
repository, application clients for MeeGo devices, the web backend for the
clients and the backend that manages the repo
- The target initially is to have the basic stream in place and then extend it
to cover the whole spectrum of use
Things that came out as action points (names in parenthesis mean main persons
for the task, if you want to help, talk to them):
- Could the MeeGo community OBS be connected to the Linux Foundation OBS in
some way? (Mike Shaver)
- Hardware for the community apps infra (Mike Shaver and Tero Kojo)
- Setting up the community OBS once the hardware arrives (Niels Breet and David
Greaves)
- Designing the community repo structure (David Greaves with help from Ramez
Hanna and Anas Nashif if necessary)
- Clients for accessing the apps (Bob Spencer and Daniel Wilms)
- Backend in the web server for the clients (Mike Shaver and Daniel Wilms)
- Inform the TSG that there will be a Community Applications Team (Tero Kojo)
Things that need an open discussion here:
- How the QA will be handled in the Community Apps? Initially it will be human
based, but can we get automation to help in some phase?
- How do we handle trust (both technical as in repository signings and such and
social as in trusting the developer) in the applications
- How to do the app client development (it's in gitorious, but finding a single
project in gitorious is not simple) more in the open and how to get the clients
even better than now
If I forgot something, please add.
Tero
MeeGo community infra guy
P.S. the log is here http://www.daimi.au.dk/~cvm/log.04-29-2010 in case someone
wants to see it.
_______________________________________________
MeeGo-dev mailing list
[email protected]
http://lists.meego.com/listinfo/meego-dev
--- End Message ---
_______________________________________________
MeeGo-dev mailing list
[email protected]
http://lists.meego.com/listinfo/meego-dev
