2010/4/29 David Greaves da...@dgreaves.com:
http://wiki.meego.com/Packaging/Deb_conversion_example
More to follow - we'd appreciate constructive feedback both from those
knowledgeable about rpms and those trying to gain that knowledge.
Yes, feedback and changes welcome. Like I noted on the
ext Glen Gray wrote:
On 27 Apr 2010, at 10:16, Quim Gil wrote:
The plan is to have in few weeks a first complete MeeGo release
followed by a roadmap to work on the next release. Once this is out
the MeeGo project shouldn't have any obstacle to have all the daily
work and routines in the
On 04/28/2010 09:10 PM, ext Greg KH wrote:
On Wed, Apr 28, 2010 at 09:03:15PM +0300, Ameya Palande wrote:
Naturally all the bugs related to this should be assigned to Nokia
instead of Intel. So I fail to understand your argument about Intel
doing all the work and all the kernel bugs being
I used rootfs of arm meego to boot standard kernel, but it runs like this ,
what happend ? The rootfs is made with rpm packets from
http://repo.meego.com/MeeGo/devel/trunk/repo/arm/os/armv5tel/.
/etc/rc.d/rc.sysinit: line 28: /sys/devices/virtual/graphics/fbcon/cursor_blink:
No such file
On 29 Apr 2010, at 13:46, wangjihong wrote:
hello all ,
i have a problem . who can give me some advise?
the problem is i can not install the MEEGO OS on my netbook.
how can i install the meego OS?
Currently, there's no way to install MeeGo on a netbook, using the default
images.
i
On Thu, 2010-04-29 at 14:20 +0200, ext yespmc wrote:
I used rootfs of arm meego to boot standard kernel, but it runs like
this , what happend ? The rootfs is made with rpm packets from
http://repo.meego.com/MeeGo/devel/trunk/repo/arm/os/armv5tel/.
Which rootfs and kernel did you use? From
-Original Message-
From: meego-dev-boun...@meego.com
[mailto:meego-dev-boun...@meego.com] On Behalf Of Dave Neary
Sent: Thursday, April 29, 2010 4:06 PM
To: Greg KH
Cc: meego-dev
Subject: Re: [MeeGo-dev] Kernel process comment
So your argument is that the people who are doing the
Move x86 ARCH stuff from config-generic to config-x86-generic and
config-arm-generic. config-generic cannot contain ARCH_xxx stuff.
Makefile.config is fixed to generate temp-ARCH-generic from
config-generic and config-ARCH-generic. Then other variants
can use this temp-ARCH-generic to arrive at
On Thu, Apr 29, 2010 at 3:13 PM, Wang, Yong Y yong.y.w...@intel.com wrote:
Hi Guys,
This is indeed a documentation bug and we will fix it. No Intel employees
will bypass the process. All changes, including those from Intel employees,
will be scrutinized by MeeGo kernel maintainer team which
On 04/28/10 17:59, ext Greg KH wrote:
As Intel is ultimately responsible for distributing and maintaining this
kernel tree, having someone within intel to own each patch in the same
manner makes lots of sense as well.
This is not true. Where did you get that one ?
Nokia and Intel are
Hi,
tero.k...@nokia.com wrote:
But we also need the process and mechanisms to ensure that the
community apps are of good quality. The apps are one of the calling
cards of the community. Also some process to ensure that the people
building on the community OBS do not hog the system or try to
On Thu, Apr 29, 2010 at 7:23 PM, Zahed Ali Taqi zahedonl...@gmail.comwrote:
Hi Guys,
I have N900 Device can it be of any help? I also have N810 was using the
Meamo for a couple of years, got very familiar with it. So please let me
know i can help in testing on my device,
Cheers,
Zahed
-Original Message-
From: surreal.w...@gmail.com [mailto:surreal.w...@gmail.com] On Behalf
Of Robin Burchell
Sent: Thursday, April 29, 2010 10:54 PM
To: Wang, Yong Y
Cc: Dave Neary; Greg KH; meego-dev
Subject: Re: [MeeGo-dev] Kernel process comment
On Thu, Apr 29, 2010 at 3:13 PM,
Hi kojo,
在 2010-04-29四的 11:22 +0200，tero.k...@nokia.com写道：
I don't think the MeeGo core OBS that is used to make the MeeGo
distribution releases will be opened to just anybody. Gaining access
to that will always be a merit based thing based on working on a core
project.
I do NOT like OBS,
Hi Tero,
Android java executables are platform-independent, however, AFAIK, Qt, or
MeeGo support an only source compatible interfaces, so that applications has
to be rebuild for different platforms.
Here comes the necessity to setup an official MeeGo OBS server which open to
everyone. Otherwise
On 2010-04-29, 16:06 +0800, Dave Neary wrote:
What people are taking issue with is that (a) being an employee of Intel
is not sufficient to make you a MeeGo kernel maintainer and (b) in
theory, at least, being an employee of Intel is not required to be a
MeeGo kernel maintainer either.
On Fri, Apr 30, 2010 at 10:16:07AM +0800, An Yang wrote:
Hi kojo,
??? 2010-04-29?? 11:22 +0200???tero.k...@nokia.com?
I don't think the MeeGo core OBS that is used to make the MeeGo
distribution releases will be opened to just anybody. Gaining access
to that will always be
On Fri, Apr 30, 2010 at 12:03:17PM +0800, Yin Kangkai wrote:
We have no problem to add others outside of Intel into the MeeGo
kernel maintainer team, actually we welcome that, as long as he can
take the responsibilities.
Great, how does one go about signing themselves up to do this?
thanks,
On 4/29/2010 21:16, Greg KH wrote:
On Fri, Apr 30, 2010 at 12:03:17PM +0800, Yin Kangkai wrote:
We have no problem to add others outside of Intel into the MeeGo
kernel maintainer team, actually we welcome that, as long as he can
take the responsibilities.
Great, how does one go about signing
19 matches
Mail list logo
